Differences

This shows you the differences between two versions of the page.

--- docs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors [21.01.2017 01:51 CET] – peter
+++ docs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors [05.10.2017 03:04 CEST] – peter
@@ Line 4: / Line 4: @@
 :!: 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/ :!:\\
+:!: 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/((Basically he suggests to create a sparsebundle on your own first, give it a custom band size:
+  # creates a sparsebundle disk image with a 128MB band size
+  MACHINE_NAME=your-machine-name
+  echo $MACHINE_NAME
+  hdiutil create -size 900g -type SPARSEBUNDLE -nospotlight -volname "Backup of $MACHINE_NAME" -fs "Case-sensitive Journaled HFS+" -imagekey sparse-band-size=262144 -verbose ./$MACHINE_NAME.sparsebundle
+)) :!:\\
 :!: Just realized that the source recommends to use raw disk devices, which means to use ''/dev/rdisk''... instead of ''/dev/disk''... :!:
@@ Line 56: / Line 61: @@
 </code>(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.
   - If this does not finish successfully or did a "QUICKCHECK ONLY", run disk repair again:<code>
-~ # fsck_hfs -drfy /dev/disk1s2
+~ # fsck_hfs -drfy /dev/rdisk1s2
 ** /dev/rdisk1s2
         Using cacheBlockSize=32K cacheTotalBlock=8192 cacheSize=262144K.