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.04.2020 17:44 CEST] – 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''... :!:
   - Connect your Backup Volume((Might be done via the Finder or by\\ ''mkdir /Volumes/Backup_Volume''\\ ''mount_afp -i afp:/''''/<user>@<host>/Backup_Volume /Volumes/Backup_Volume''))
-  - I recommend to disable your backups as successive tries seem to interfere with the recovery process. Furthermore, it might be a good idea to keep the backup volume open by displaying it in the finder and to make sure that your network connection is stable (provided your backup volume is connectec via your network one way or the other)
+  - I recommend to disable your backups((Either in the Time Machine system preferences dialog or by ''tmutil disable'')) as successive tries seem to interfere with the recovery process. Furthermore, it might be a good idea to keep the backup volume open by displaying it in the finder and to make sure that your network connection is stable (provided your backup volume is connected via your network one way or the other)
   - Start a shell (Terminal Window) with root permissions and recursively clear the //user immutable flag//:<code>
 ~ # chflags -v -R nouchg /Volumes/Backup_Volume/MyHostname_YYYY-MM-DD-HHMMSS.sparsebundle</code>
@@ 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.