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 revisionPrevious revision
Next revision
Previous revision
docs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors [20.04.2020 10:48 CEST] peterdocs:tips_n_tricks:max_os_x:fix_time_machine_sparsebundle_errors [25.06.2020 01:01 CEST] (current) peter
Line 18: Line 18:
   - Start a shell (Terminal Window) with root permissions and recursively clear the //user immutable flag//:<code>   - 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> ~ # chflags -v -R nouchg /Volumes/Backup_Volume/MyHostname_YYYY-MM-DD-HHMMSS.sparsebundle</code>
-  - attach the sparsebundle as volume without mounting<code>+  - attach the sparsebundle as volume without mounting((it's been ''Apple_HFS'' instead of ''Apple_HFSX'' in my case))<code>
 ~ # hdiutil attach -nomount /Volumes/Backup_Volume/MyHostname_YYYY-MM-DD-HHMMSS.sparsebundle ~ # hdiutil attach -nomount /Volumes/Backup_Volume/MyHostname_YYYY-MM-DD-HHMMSS.sparsebundle
 /dev/disk1              Apple_partition_scheme /dev/disk1              Apple_partition_scheme
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
Line 99: Line 99:
 </WRAP> </WRAP>
  
-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. 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}} {{tag>OSX backup}}
 {{entry>OSX}} {{entry>OSX}}
 {{entry>backup}} {{entry>backup}}
docs/tips_n_tricks/max_os_x/fix_time_machine_sparsebundle_errors.1587372531.txt.gz · Last modified: 20.04.2020 10:48 CEST by peter

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki