Differences

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

--- docs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors [10.02.2017 11:32 CET] – Added code to create sparse bundle in case it will be deleted on gist. peter
+++ docs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors [17.03.2018 18:16 CET] – peter
@@ Line 9: / Line 9: @@
   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
-)) :!:\\
+)) :!: \\
+Inspired by his basic Idea, that the problem might be related to //ext2/3/4// file systems limitations, I changed to XFS for the underlying file system and got a stable backup.\\
 :!: Just realized that the source recommends to use raw disk devices, which means to use ''/dev/rdisk''... instead of ''/dev/disk''... :!:
@@ Line 61: / Line 62: @@
 </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.