On Wed, Mar 26, 2014 at 2:21 PM, Arno Hautala <[email protected]> wrote:
> It's possible that the Time Capsule disk is fine and Disk Utility is just > being finicky about the repair. > > http://blog.jthon.com/?p=31 > http://pondini.org/TM/A5b.html > > http://warmsouthernbreeze.wordpress.com/2013/06/07/how-i-finally-fixed-the-sparsebundle-errors-on-apples-time-capsuletime-machine/ > > Thank you - these are very helpful and look like they should (have) worked....but alas they did not. When, in Terminal, I was able to find the sparsebundle but was unable to do anything at all with it (even hdiutil said it was not found, even though ls found it just fine), I now have to assume that there is something very wrong with the disk itself, and per Karl's suggestion that the error is probably exactly where that sparsebundle is stored. I'll be getting a new disk now.... Thank you all for your time, thoughts, help and generosity!! > > On Tue, Mar 25, 2014 at 6:58 PM, Jeff Weinberger > <[email protected]>wrote: > >> On Tue, Mar 25, 2014 at 3:50 PM, Karl Kuehn <[email protected]> wrote: >> >>> On Mar 25, 2014, at 3:38 PM, Jeff Weinberger <[email protected]> >>> wrote: >>> >>> My acute sense of the obvious failed me on that one. Thank you for >>> reminding me. >>> >>> However, Disk Utility can't (or won't) mount it or even acknowledge it. >>> I can't copy it to any of the Macs in the house, and I can't open it (now I >>> get "no readable file system"). >>> >>> If I could delete it, I could start over - it would not be a big deal in >>> this case. >>> >>> But I also suspect something with the Time Capsule disk - any >>> suggestions for how to repair this? >>> >>> >>> If you can't copy the sparcebundle, then chances are very good that the >>> physical disk is failing. And based on what you have described, there is a >>> very good chance that one of the physical sectors underlying at least one >>> of the sparcebundle stripes was involved in this failure. If you can't get >>> it mounted, then there is a very good chance that it is so corrupted that >>> you are not going to get much from it (disk images are not as robust as >>> physical disks this way). >>> >>> As a last resort, sometimes damaged disk images will open with: >>> >>> hdiutil attach -noverify -ignorebadcheckums -noautofsck >>> >>> Even if it opens I would expect data corruption. But if you are >>> getting "no readable file system" then there is a good chance that the >>> volume headers are gone, and that makes recovery even more difficult >>> (certainly beyond me). >>> >>> >> I"m guessing the Time Capsule disk is failing. Again. They do this far >> too often and far too quickly. >> >> I was hoping to avoid replacing it, but it looks liek I have no choice... >> Thanks for your help! >> >> >> >> >>> -- >>> Karl Kuehn >>> [email protected] >>> >> >> >> _______________________________________________ >> MacOSX-talk mailing list >> [email protected] >> http://www.omnigroup.com/mailman/listinfo/macosx-talk >> >> > > > -- > arno s hautala /-| [email protected] > > pgp b2c9d448 >
_______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
