Although all of this is true, as it turns out, I know of only one disk management tool that will even attempt to repair a Time Machine volume, because the volume architecture is so baroque -- and that is Disk Utility. If you try to repair the volume with Disk Warrior, it will flat out tell you, "this is a Time Machine volume, and I don't do those." You have to use only Disk Utility, not fsck. If DU can't solve the problem, it can't be solved.
> On Jan 23, 2020, at 11:31 AM, Matt Penna <[email protected]> wrote: > > On Jan 23, 2020, at 1:25 PM, Michael <[email protected]> wrote: >> >>> On 2020-01-23, at 10:23 AM, Matt Penna <[email protected]> wrote: >>> >>> If you have DiskWarrior, I would give that a try. I believe it works on >>> disk images and sparsebundles. >>> >>> Matt >> >> I do not have disk warrior. > > Unfortunately, whenever a drive or image is not reparable like this, I’ve > always had to resort to a 3rd-party tool to fix the file system; the built-in > tools are not very robust. Perhaps someone else will have another suggestion. > > It’s always been baffling to me that 3rd parties write better fix-it tools > than the people who write the OSes. This has been a problem for over 30 years > and it’s still as unsolved as ever, even if the file systems are a lot less > fragile than they used to be. > > Matt > _______________________________________________ > MacOSX-talk mailing list > [email protected] > https://www.omnigroup.com/mailman/listinfo/macosx-talk _______________________________________________ MacOSX-talk mailing list [email protected] https://www.omnigroup.com/mailman/listinfo/macosx-talk
