The disk is clearly dead (up to some point). At mount-time, the disk spins and makes the usual noises when tools try to read to it, no noise happens. Data Rescue says it can't find any file (even in the extensive search).
It won't mount and disk utility can't repair it. But they are difficult problems, so I’m not surprised it is taking a long time to develop a useful and reliable rebuild tool.I'm trying to repair a hard disk for a friend. And I’m sure they have ideas (if not yet fully tested code) for how to deal with them. I’m sure Alsoft is aware of all of these issues. Because of this, is it possible to rebuild one volume without rebuilding every volume in a container? All volumes in an APFS container share the same pool of free blocks. Is it possible at all to rebuild that directory without breaking the seal and rendering the volume non-bootable? Big Sur doesn’t boot from the System volume, but from a cryptographically signed (“sealed”) snapshot of that volume.
Another key concept that ties multiple volumes (especially System and Data) together on Catalina+ systems. Necessary for a Catalina or later system to boot properly. Special kinds of links used to tie locations on the System volume to corresponding locations on the Data volume.
Every volume has multiple (maybe hundreds or even thousands) of directory systems, each one partially sharing disk blocks with the others. Reference-counted disk blocks, including copy-on-write semantics.The problem is that APFS introduces many new concepts that must be thoroughly understood in order to rebuild everything correctly. It should always technically be possible, but it could be (probably is) far more difficult than rebuilding HFS+ volumes. What it does is construct a new directory, that doesn’t have the damage. Also, think of the point of DiskWarrior: it doesn’t repair damage.
0 kommentar(er)
