Mac mini (192.168.0.15) — data migration and current state

2009 Mac mini, Mac OS X 10.11.6 (El Capitan), 297 GiB internal disk. Being kept only until its data is safe, then repurposed. Reached as root@192.168.0.15 over the OpenSSH 10.5p1 daemon built from source (biz.critchley.openssh) — the vendor sshd is disabled, so that daemon is the only remote way in.

Everything that existed only on this Mac is now also on the WD My Cloud NAS under /mac-mini-archive/ on the Public share. Verified by comparing file counts and total bytes on both sides, not by trusting rsync's exit status — which mattered, because several runs reported success while transferring nothing. Note the Mac is NOT being wiped (John, 2026-09-17): the goal was to get the data off an ancient machine and secured, not to empty it. The originals stay where they are.

Everything that existed only on this Mac is now also on the WD My Cloud NAS under /mac-mini-archive/ on the Public share. Verified by comparing file counts and total bytes on both sides, not by trusting rsync's exit status — which mattered, because several runs reported success while transferring nothing.

SourceFilesBytesWhere it landed
/Users/Isaac (Photos Library)8044,140,512,339NAS /mac-mini-archive/Isaac/
/Users/Joshua (most)8,27038,286,307,563NAS /mac-mini-archive/Joshua/
/Users/Joshua (whitespace dirs)115,712,642,196NAS .../Joshua/Movies/GameCaptureHD-whitespace-dirs.tar
Joshua TOTAL8,28143,998,949,759matches source exactly

Why 11 files are in a tar rather than as normal files

Elgato's Game Capture HD Library contains directories whose names consist only of spaces — one called " " and one called " " — with files inside them also named with leading spaces (" .json", " .png"). SMB cannot represent such names. The NAS silently mangled them into 8.3-style short names (_2X68Q~7, _IDZPL~P); rsync then created content under the mangled name but kept looking for the original, and failed with failed to stat ... Not a directory (20). Rather than rename them and lose fidelity, those two directories were archived with tar, where the names are just bytes and SMB never sees them. Verified: the archive holds 15 entries / 5,712,642,918 bytes — the 11 real files plus four AppleDouble ._ metadata files (722 bytes), which exactly accounts for the difference.

To restore, extract on a filesystem that permits such names (HFS+/APFS/ZFS/ext4 all do; SMB and NTFS do not):

cd "/somewhere/Game Capture HD Library"
tar xf GameCaptureHD-whitespace-dirs.tar

Transfer path and performance

The Mac is on the house LAN (192.168.0.0/26, WiFi) and the NAS is on 192.168.99.0/24 behind pomelo, so everything routes through pomelo. Measured at 8.6–8.9 MB/s, and the two possible paths are indistinguishable: rsync-over-SSH pulled by pomelo gave 8.6 MB/s, a direct SMB copy over the new static route gave 8.9 MB/s. The WiFi leg is the bottleneck — 71 Mbit/s effective against a 270 Mbit/s nominal link. SSH encryption is not the constraint despite the 2009 CPU having no AES-NI (cp used 7.8 s of system time for 3.9 GB). If a large transfer is ever needed again, put the Mac on ethernet — nothing else will make a material difference.

Changes made to this Mac 2026-09-17

tags hosts, mac, migration, nas, archive