Move vlda-01 Gitea backup destination to the WSD2L840 unassigned disk

Was landing in /mnt/user/appdata/ (array storage); moved to a dedicated
external disk per request. That disk isn't guaranteed to already be
mounted when the pull script runs, so it now resolves the device by
filesystem label (not a hardcoded /dev/sdX - unassigned device paths
aren't stable across reboots) and mounts it itself via the Unassigned
Devices plugin's own tool, refusing to proceed unless a real mountpoint
actually comes up - avoids the failure mode of silently writing backups
onto the array if the disk is unplugged or fails to mount. Migrated the
two already-pulled archives to the new location and verified the
updated script end-to-end through the real scheduled-invocation path.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
2026-07-26 16:50:24 +02:00
co-authored by Claude Sonnet 5
parent f9e0f5221f
commit 77eb6487e8
+13 -3
View File
@@ -415,9 +415,19 @@ The SSH keypair needed no special handling: Unraid already auto-mirrors
already present locally — a run after several days offline catches up
on all of them, not just the newest, without re-downloading anything
already pulled.
- Lands in `/mnt/user/appdata/gitea-backups-from-alpha/` (real array
storage, not the RAM-backed root), keeps the last 30 locallydeeper
history than alpha's own 14, given the Unraid array's ample headroom.
- Lands in `/mnt/disks/WSD2L840/git/` — an **Unassigned Device** (external
disk, not part of the protected array), not the RAM-backed rootkeeps
the last 30 locally, deeper history than alpha's own 14, given the
disk's ample headroom.
- **The device isn't guaranteed to already be mounted** when the script
runs, so it resolves the disk by filesystem label (`findfs
LABEL=WSD2L840`, not a hardcoded `/dev/sdX` — USB/Unassigned-Device
paths aren't stable across reboots) and mounts it itself via the
Unassigned Devices plugin's own `rc.unassigned mount` (confirmed
idempotent — safe to call even when already mounted). Explicitly
verifies the result is a real mountpoint (`mountpoint -q`) before writing
anything — refuses to run rather than risk silently dumping backups onto
the array if the disk is unplugged or fails to mount.
**Restore path, if ever needed**: manual and deliberate — stop the target
Gitea container, unpack the chosen dump's DB/repos/etc. into `/data` per