Differences

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

--- docs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors [17.04.2020 20:40 CEST] – peter
+++ docs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors [02.05.2020 22:15 CEST] – peter
@@ Line 62: / 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.
 <note important>Therefore I recommend cabled network during the recovery process.</note>
-  - If this does not finish successfully or did a "QUICKCHECK ONLY", run disk repair again:<code>
+  - If this does not finish successfully or did a "QUICKCHECK ONLY", run disk repair again((The Disk Utility does not use ''-r'' which means to rebuild the catalog tree. Try again without it if you run into an “Disk Full” error during rebuilding the catalog B-tree)):<code>
 ~ # fsck_hfs -drfy /dev/rdisk1s2
 ** /dev/rdisk1s2
@@ Line 99: / Line 99: @@
 </WRAP>
-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.
+Now you can eject the network share((Use ''hdiutil eject /Volumes/Backup_Volume'' if you prefer the command line)) and have Time Machine give it another go.
+<note tip>Don't forget to enable backups again ((Might be done via ''tmutil enable'' at the command line)).</note>
+After the (long) verification step, backups should proceed once again.
 {{tag>OSX backup}}
 {{entry>OSX}}
 {{entry>backup}}