Written 4 Sep 2026. This is a how-to, not a product card.
When the house backup won't run
rsync failed, the USB is missing, or the second copy never landed. Check the stick, the mount, the source path, then match the error (no space, permission, connection). You don't need a NAS.
Haven't made a second copy yet? Start with a backup of the house folder. Copying to another old PC instead of a stick? See copy the house folder to another old computer. This note is only for when the copy fails, or used to work and now doesn't.
Skip until you have a real error
Copy the exact line from the terminal. "No such file or directory," "No space left on device," "Permission denied," and "Connection refused" are different fixes. Don't buy a NAS for a stick that never mounted.
What this is
A house backup is usually rsync from the house folder (often /srv/share) onto a USB disk or another old PC. It needs the source folder to exist, the destination to be mounted and writable, and room on that destination. One of those usually drifted. Stick unplugged, wrong /dev/sdX, empty mount point, full USB, or SSH broken to the second box. The walk below is order of cheap checks.
Step 1: is the computer awake?
Power light. Fan. Screen if it has one. If it looks asleep or dead, start with is the computer still on?. Soft-off on purpose? Wake it from the house network: wake the computer from the house network. You need SSH from the couch before any of the commands below: SSH from the couch. If that connect fails first, fix it with when SSH won't connect.
Step 2: USB path โ see the stick, then mount it
If your second copy is a USB disk, plug it in. Confirm the computer sees it:
lsblk
You should see a new disk (often sdb with a partition like sdb1). Use the name lsblk printed, not a guess from last week. Fuller walk: see if the USB backup disk showed up.
Mount it the same way the first-backup note taught:
sudo mkdir -p /mnt/backup && sudo mount /dev/sdb1 /mnt/backup
Swap /dev/sdb1 if yours differs. Check it stuck:
findmnt /mnt/backup
If that prints nothing, the mount failed. Don't run rsync into an empty /mnt/backup on the system disk by accident.
Step 3: confirm the source folder
The house folder has to exist before you copy it:
ls /srv/share
If that path is wrong on your box, use the folder you actually share. Haven't made one yet? That is a file share, not a backup bug.
Step 4: match the symptom to a fix
| What you see | What to do |
|---|---|
| No such file or directory (source) | Wrong source path. Fix Step 3. Trailing slashes matter on rsync: rsync -a /srv/share/ /mnt/backup/share/ copies the contents into that backup folder. |
| No such file or directory (destination) / empty mount | USB never mounted, or you typed the wrong mount folder. Redo Step 2. Confirm with findmnt /mnt/backup before rsync. |
| No space left on device | The destination is full (USB or second box), or you wrote onto the system disk by mistake. Check room: df -h /mnt/backup and see if the computer still has room. Use a bigger stick, delete junk on the USB, or park the live share on a bigger disk: put the house folder on a USB disk. |
| Permission denied | Destination folder not writable, or you need sudo for the mount only. After a normal mount, your user should own the copy target: sudo mkdir -p /mnt/backup/share && sudo chown "$USER:$USER" /mnt/backup/share. Then rerun rsync without stuffing every file through root. |
| Connection refused / timed out / Permission denied (second PC) | The other-computer path needs working SSH to that box first. Fix connect: when SSH won't connect. Full second-box walk: copy the house folder to another old computer. |
| rsync exits 0 but the USB looks empty | You may have copied into an unmounted path on the system disk, or looked at the wrong folder. Confirm the mount, then check the copy landed: check that the backup actually copied. |
Check
Run the copy again (USB example):
rsync -a /srv/share/ /mnt/backup/share/
Then look:
ls /mnt/backup/share
You should see the same folders as /srv/share. Unmount before you yank the cable:
sudo umount /mnt/backup
Pull one file back sometime so you know restore works: restore one file from the USB backup. Need the whole folder after a wipe? put the house folder back from the backup.
What this is not
This is not a reason to buy a NAS tonight. It is not RAID. It is not restic, Borg, or a cloud plan until a plain second copy exists on a stick or another old PC. It is not leaving the USB plugged in forever so one bad day can wipe both copies.
What next
First successful copy still lives on a backup of the house folder. Stick not showing up: see if the USB backup disk showed up. After a green terminal, confirm files landed: check that the backup actually copied. Second old PC instead of USB: copy the house folder to another old computer. When the copy is boring, let the computer do it weekly: back up the folder every week without remembering.
Skip
- Skip buying a NAS for a first-timer rsync failure.
- Skip RAID. RAID is not a backup.
- Skip restic and Borg until a plain second copy works.
- Skip a cloud plan until the USB (or second-box) copy exists.
- Skip leaving the USB plugged in forever.
- Skip guessing last week's
/dev/sdb1instead of runninglsblkagain.
Sources
Debian: rsync man page. Ubuntu: rsync man page. Debian: lsblk. Debian: df. Official pages only. For the copy this fixes, see a backup of the house folder. For the stick check, see see if the USB backup disk showed up. For a landed-copy look, see check that the backup actually copied. For the second-box path, see copy the house folder to another old computer.