Files
homelab/services/media/clonarr.nix
T
darmanandClaude Opus 5 0ec3c6413c jupiter: keep booting when the data array is missing
After the rack move one of the RAID0 disks failed to enumerate, and jupiter
boot-looped into an emergency shell nobody could use — root is locked, so
sulogin offers a prompt with no answer, and there is no ssh from there:

  Timed out waiting for device /dev/disk/by-uuid/dadbff6f-...
  Dependency failed for /mnt/data.
  Dependency failed for /var/lib/private/prowlarr.
  Dependency failed for Local File Systems.
  local-fs.target: Job local-fs.target/start failed with result 'dependency'
  Reached target Emergency Mode.

`nofail` on /mnt/data did not help, because the prowlarr and seerr bind
mounts layered on top of it had none: without it a mount is RequiredBy
local-fs.target, so those two failed the target on the array's behalf. Give
them `nofail` too and let them fail alone. `systemd.enableEmergencyMode =
false` then keeps a bad array from costing a reachable box at all — far more
useful on a headless host than a console prompt.

Booting further is only safe if nothing quietly relocates onto the 29G eMMC,
so pin the array-backed services to the mount. systemd derives
RequiresMountsFor from a unit's own paths, which for these is somewhere under
/var/lib (eMMC) — nothing pointed immich at mediaLocation or sabnzbd at its
configFile, so with the array gone they would have started and written to the
OS disk, into directories that go invisible the moment /mnt/data mounts over
them. jellyfin, sonarr, radarr and gitea already had a real dependency and
are untouched.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-06 03:32:42 +02:00

35 lines
1.2 KiB
Nix

{ ... }:
# Clonarr — visual TRaSH-Guides sync tool for Radarr/Sonarr (quality
# profiles, custom formats, scores). No nixpkgs package; runs the official
# container image (ghcr.io/prophetse7en/clonarr).
{
virtualisation.oci-containers.containers.clonarr = {
image = "ghcr.io/prophetse7en/clonarr:latest";
autoStart = true;
# Host networking: clonarr needs to reach Radarr/Sonarr/Prowlarr on
# jupiter's own localhost (native systemd services, not containers) —
# bridge-mode "localhost" would be the container's own netns, not the host's.
extraOptions = [ "--network=host" ];
volumes = [
"/mnt/data/AppData/clonarr:/config"
];
environment = {
TZ = "Europe/Berlin";
PUID = "1000";
PGID = "100"; # darman:users
PORT = "6060";
};
};
systemd.tmpfiles.rules = [
"d /mnt/data/AppData/clonarr 0755 darman users -"
];
# podman bind-mounts /mnt/data/AppData/clonarr into the container, but the
# generated unit only knows about /run/clonarr — with the array absent podman
# would create the source path on the eMMC and the container would run
# against an empty config.
systemd.services.podman-clonarr.unitConfig.RequiresMountsFor = [ "/mnt/data" ];
}