Trying the Ghostty terminal, I hit a problem over SSH to a Synology NAS: arrow-key history recall and clear don’t work, because Ghostty sets TERM to xterm-ghostty and Synology lacks the matching terminfo. The practical fix is overriding TERM to xterm-256color via an ssh config SetEnv entry, which can be wildcarded across multiple hosts. The terminfo installation method Ghostty officially recommends fails on Synology’s minimal DSM...
After abandoning an overly complicated LXD-based file transfer setup, I walk through using command-line rsync to sync files directly between two Synology NASes, including over Tailscale. I cover setting up passwordless SSH without ssh-copy-id, working around DSM 7’s restriction on Tailscale outbound connections and its lack of Magic DNS, enabling rsync in the Synology interface, excluding metadata and recycle bin directories, fixing permissions, throttling bandwidth, deleting remote files in one-way syncs, and running the job in the background with nohup...
My Proxmox backup of an unprivileged LXC container to an NFS share failed with tar permission errors, even though privileged container backups to the same share worked. Testing with throwaway containers, I traced the problem to vzdump’s temp directory living on the NFS mount, and setting tmpdir to /tmp in /etc/vzdump.conf fixed it. I walk through the error logs and include some skepticism about the common forum explanation...
Proxmox saves VM backups to local storage by default, which is no help if the host dies and makes restoring to a different node awkward. My walkthrough covers creating a shared folder with NFS permissions on a Synology NAS, then adding that share as storage at the datacenter level in Proxmox so backups and restores can happen from any node, making it easy to move VMs between hosts...
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...
Setting up a backup strategy on a Synology NAS, I SSH in to locate volume and share mount points and do a dry-run rsync of a movies directory from the NAS to a USB drive. The first run surfaces thousands of @eaDir entries, which turn out to be Synology metadata files likely produced by the indexing service, and I end the post by excluding them via the –exclude option...
Setting up SSH key-based login on a Synology NAS running DSM 7.1.1 takes a couple of extra steps compared to a standard Linux distro: enabling the SSH service and enabling user home directories, since DSM doesn’t create them by default and ssh-copy-id needs one. I walk through both settings in the DSM web interface, and note that most Synology tasks are usually easier and safer done through its web UI or Package Center...
A guide to mounting a remote Synology NAS share onto a second Synology NAS using FileStation’s Mount Remote Folder feature, allowing large direct NAS-to-NAS transfers without an intermediary laptop. I walk through creating a mount point, connecting via CIFS, and copying 4TB of data, with observed transfer speeds of 30-70 MB/s...
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...
