mkdir /Volumes/Backup_Volume
mount_afp -i afp:/
/<user>@<host>/Backup_Volume /Volumes/Backup_Volume
This is an old revision of the document!
[This is an extract from Fix Time Machine Sparsebundle NAS Based Backup Errors by Garth Gillespie]
This is work in progress! Not all steps are verified yet!
Maybe one reference in the comments to the article denoted above is worth reading: http://sansumbrella.com/writing/2012/the-reluctant-sysadmin-nas-time-machine/
~ # chflags -v -R nouchg /Volumes/Backup_Volume/MyHostname_YYYY-MM-DD-HHMMSS.sparsebundle
~ # hdiutil attach -nomount /Volumes/Backup_Volume/MyHostname_YYYY-MM-DD-HHMMSS.sparsebundle /dev/disk1 Apple_partition_scheme /dev/disk1s1 Apple_partition_map /dev/disk1s2 Apple_HFSX ~ #
Use the partiion listed as Apple_HFSX
in the following steps (i.e. replace /dev/disk1s2
by your partition). This will implicitly start a file system check. As checked with ps
, the actual command run seems to be
/System/Library/Filesystems/hfs.fs/Contents/Resources/../../../../../../sbin/fsck_hfs -y /dev/disk1s2
~ # tail -f /var/log/fsck_hfs.log /dev/rdisk1s2: ** /dev/rdisk1s2 /dev/rdisk1s2: Executing fsck_hfs (version diskdev_cmds-491.6~3). ** Checking Journaled HFS Plus volume. ** Detected a case-sensitive volume. ** Checking extents overflow file. ** Checking catalog file. ** Checking multi-linked files. ** Checking catalog hierarchy. ** Checking extended attributes file. ** Checking multi-linked directories. ** Checking volume bitmap. Volume bitmap needs minor repair for orphaned blocks ** Checking volume information. Invalid volume file count (It should be 3180308 instead of 3355480) Invalid volume directory count (It should be 356386 instead of 356055) Invalid volume free block count (It should be 15844066 instead of 16637291) Volume header needs minor repair (2, 0) /dev/rdisk1s2: ** Repairing volume. ** Rechecking volume. ** Checking Journaled HFS Plus volume. ** Detected a case-sensitive volume. ** Checking extents overflow file. ** Checking catalog file. ** Checking multi-linked files. ** Checking catalog hierarchy. ** Checking extended attributes file. ** Checking multi-linked directories. ** Checking volume bitmap. ** Checking volume information. ** The volume Time Machine-Backups was repaired successfully.
(If something goes wrong and you have to start over, you need to clear the user immutable flag again.)
Most failures at this point were due to accidental unmount of the underlying /Volumes/Backup_Volume
. I believe the unmounts were caused by network errors while using WIFI.
Therefore I recommend cabled network during the recovery process.
~ # fsck_hfs -drfy /dev/disk1s2 ** /dev/rdisk1s2 Using cacheBlockSize=32K cacheTotalBlock=8192 cacheSize=262144K. Executing fsck_hfs (version diskdev_cmds-491.6~3). Journal replayed successfully or journal was empty ** Checking Journaled HFS Plus volume. ** Detected a case-sensitive volume. ** Checking extents overflow file. ** Checking catalog file. ** Rebuilding catalog B-tree. hfs_UNswap_BTNode: invalid node height (1) ** Rechecking volume. ** Checking Journaled HFS Plus volume. ** Detected a case-sensitive volume. ** Checking extents overflow file. ** Checking catalog file. ** Checking multi-linked files. ** Checking catalog hierarchy. ** Checking extended attributes file. ** Checking multi-linked directories. privdir_valence=24850, calc_dirlinks=101703, calc_dirinode=24850 ** Checking volume bitmap. ** Checking volume information. ** The volume Time Machine-Backups was repaired successfully. ~ #
~ # hdiutil detach /dev/disk1s2
com.apple.TimeMachine.MachineID.plist
with the Plist Editor. Remove the EntryRecoveryBackupDeclinedDate | Date | DD.MM.YYYY HH:MM:SS |
VerificationState | Number | 2 |
to
VerificationState | Number | 0 |
Now you can eject the network share and have Time Machine give it another go. After the (long) verification step, backups should proceed once again.