While rearranging disks toward a 3-2-1 backup setup, I realise a wiped Synology drive still held the only other copy of my audiobook collection. Reinstalling the one surviving RAID drive and using the Recover option brings the pool back in a degraded state, allowing the files to be copied out. The episode doubles as a useful test of a dead-drive scenario, with the NAS’s beeping alert proving reassuring for a self-hosted setup...
While planning to move my applications from the cloud to self-hosting, I evaluate Synology NAS options for a roughly 12TB storage target, weighing RAID levels, second-hand versus new drives, cost per terabyte, and power consumption. I ultimately choose a new DS420j with four used 6TB drives in RAID 6 for production, plus a single-drive NAS for local backup and my existing unit with 14TB drives for remote backup...
I move Jellyfin from a Proxmox LXC container to a VM because Tailscale wouldn’t run in the container, but the fstab entry mounting a NAS media share over CIFS no longer mounts at boot, even though mount -a works. The cause is the network not being up when the mount is attempted, and the fix is adding noauto, x-systemd.automount, and _netdev to the mount options so systemd waits for the network and mounts on demand...
I set up a secondhand Synology DS216j NAS as homelab storage with RAID 1 and a Samba share, intended for VM backups and eventually a media library. I then mount the share on a privileged Debian LXC container in Proxmox via a cifs entry in /etc/fstab, with a breakdown of the mount options and a note that the setup persists across reboots...
