User Tools

Site Tools


docs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
docs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors [20.04.2020 10:51 CEST]
peter
docs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors [02.05.2020 22:15 CEST] (current)
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. </​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>​ <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 ~ # fsck_hfs -drfy /​dev/​rdisk1s2
 ** /​dev/​rdisk1s2 ** /​dev/​rdisk1s2
docs/tips_n_tricks/max_os_x/fix_time_machine_sparsebundle_errors.txt · Last modified: 02.05.2020 22:15 CEST by peter