Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.5: Time machine, corrupt sparse images, and panics' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Time machine, corrupt sparse images, and panics
Authored by: higgy on Jun 25, '08 10:32:02AM

Awesome fix - thank you for all who figured this out!

I've not had the KPs, (Time Machine would fail after about 1 month - disk would become "read only") but have had to previously reformat and wipe out my time machine backups (Lacie USB connected to Airport Extreme; OS 10.5.2 Powerbook G4). Nothing else worked - and I've been scouring the Apple discussion boards.

Final fix that worked: the "hdiutil xxx..." terminal command to "attach" the sparsebundle; followed by DiskWarrior 4.1 to repair the corrupt image.

Thank you again to all that contributed to this fix - I'm back up and running time machine backups and didn't have to wipeout a month's worth of backups - which, I believe, is what Time Machine on Leopard is supposed to do.

- higgy



[ Reply to This | # ]
10.5: Time machine, corrupt sparse images, and panics
Authored by: cneth on Apr 02, '09 06:23:39AM

Note that if you get "operation not supported on socket" what that really means is that you don't have the right permissions. You'll need admin privs to mount the disk in that case (sudo hdiutil ....)



[ Reply to This | # ]