Ventura’s disk utility has discovered unrepairable APFS errors (invalid checksums, bit flips, fsroot tree is invalid) whereas operating First Support on my Mojave quantity. With out figuring out extra particularly what recordsdata or knowledge constructions are literally affected by the reported issues I discover it troublesome to gague the extent of present injury and threat of future injury. Extra particularly, what I am unable to decide from the First Support output is:
- Which recordsdata are affected?
- Is your complete current tree untrustworthy?
- Is the injury native to preexisting objects, or of a nature that might probably have an effect on newly created recordsdata and constructions?
- …and whether or not I ought to put much less belief in backups made after the issue arose.
Why do I wish to know this stuff? With out figuring out…
- …#1 I do not know learn how to exchange broken recordsdata even after I reformat, do a clear set up, and restore from a backup (if that backup occurs to have been made after the corruption).
- …#2 I do not know whether or not I can “repair” (work round) the issue by changing particular person recordsdata, or whether or not I have to reformat the entire quantity. Although I am leaning towards a reformat since I simply found some “non-empty” empty directories which are unattainable to take away, which doesn’t bode nicely. That mentioned, to this point I can nonetheless run and use Mojave usually from that quantity, so injury is likely to be localized (?)
- …#3 I do not know if I ought to keep away from writes to the file system within the meantime, whereas engaged on an answer.
- …#1 or #2 I am unable to decide #4; whether or not my backups have been affected and whether or not I ought to compensate for that.
man fsck_apfs doesn’t clarify the output. Within the output beneath I am guessing that oid, btn and xid are object id, b-tree node and extent id respectively, however even when so that does not assist me a lot.
The query in a single sentence: Is it doable to determine the broken objects in a manner that is extra relatable to me as a person? In essence, can I take advantage of the next data to conclude something apart from “reformat and restore every part”?
First Support output (Ventura 13.4.1)
Operating First Support on “Mojave” (disk1s1)
Verifying the startup quantity will trigger this laptop to cease responding.
Verifying file system.
Quantity couldn't be unmounted.
Utilizing reside mode.
Performing fsck_apfs -n -l -x /dev/rdisk1s1
Checking the container superblock.
Checking the checkpoint with transaction ID 5195073.
Checking the EFI jumpstart file.
Checking the area supervisor.
Checking the area supervisor free queue timber.
Checking the thing map.
Checking the encryption key constructions.
Checking quantity /dev/rdisk1s1.
Checking the APFS quantity superblock.
The quantity Mojave was formatted by diskmanagementd (945.250.134) and final modified by apfs_kext (945.275.10).
Checking the thing map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of seven (com.apple.TimeMachine.2023-08-21-224452)
warning: (oid 0x77c55) apfs_root: btn: invalid o_cksum (0x97a332a0c0f82f0f)
Checking snapshot 2 of seven (com.apple.TimeMachine.2023-08-21-234501)
warning: (oid 0x77c55) apfs_root: btn: invalid o_cksum (0x97a332a0c0f82f0f)
Checking snapshot 3 of seven (com.apple.TimeMachine.2023-08-22-010420)
warning: (oid 0x77c55) apfs_root: btn: invalid o_cksum (0x97a332a0c0f82f0f)
Checking snapshot 4 of seven (com.apple.TimeMachine.2023-08-22-020426)
warning: (oid 0x77c55) apfs_root: btn: invalid o_cksum (0x97a332a0c0f82f0f)
Checking snapshot 5 of seven (com.apple.TimeMachine.2023-08-22-030433)
warning: (oid 0x77c55) apfs_root: btn: invalid o_cksum (0x97a332a0c0f82f0f)
Checking snapshot 6 of seven (com.apple.TimeMachine.2023-08-22-150009)
warning: (oid 0x77c55) apfs_root: btn: invalid o_cksum (0x97a332a0c0f82f0f)
Checking snapshot 7 of seven (com.apple.TimeMachine.2023-08-22-160051)
warning: (oid 0x77c55) apfs_root: btn: invalid o_cksum (0x97a332a0c0f82f0f)
Checking the doc ID tree.
Checking the fsroot tree.
warning: (oid 0x77c55) apfs_root: btn: invalid o_cksum (0x97a332a0c0f82f0f)
warning: aborting jobj validations for present fsck cross - making an attempt to restore fsroot tree with invalid nodes
warning: (oid 0xc19a3) apfs_root: btn: invalid o_cksum (0x4b9ff977efadac3f)
error: (oid 0xc19a3) apfs_root: btn: discovered a bit flip at index 0x2e0c
warning: (oid 0xc1bd4) apfs_root: btn: invalid o_cksum (0x3543b8b7c0db6d66)
error: (oid 0xc1bd4) apfs_root: btn: discovered a bit flip at index 0x5d6f
warning: (oid 0xca9b8) apfs_root: btn: invalid o_cksum (0xc42a5017cd0fefbc)
error: (oid 0xca9b8) apfs_root: btn: discovered a bit flip at index 0x12c
warning: (oid 0xe5dab) apfs_root: btn: invalid o_cksum (0xf95d016805396644)
error: (oid 0xe5dab) apfs_root: btn: discovered a bit flip at index 0x2604
warning: (oid 0xe9e98) apfs_root: btn: invalid o_cksum (0xbe64f3bb3dae3b25)
warning: (oid 0x1d4352) apfs_root: btn: invalid o_cksum (0xd4eabeb7839d1400)
error: (oid 0x1d4352) apfs_root: btn: discovered a bit flip at index 0x420c
warning: (oid 0x1d7884) apfs_root: btn: invalid o_cksum (0xbe2eef72f85b5d84)
warning: (oid 0x2f6cf4) apfs_root: btn: invalid o_cksum (0x3732b1710e70951d)
warning: (oid 0x384ae7) apfs_root: btn: invalid o_cksum (0xe946e4cbedd29ee9)
error: btn: oid (285044), xid (5195072), sort (0x2), subtype (0xe), flags (0x1) degree (3)
error: btn: invalid btn_btree.bt_key_count (anticipated 7724707, precise 7725062)
fsroot tree is invalid.
The quantity /dev/rdisk1s1 was discovered to be corrupt and can't be repaired.
Verifying allotted area.
The quantity /dev/rdisk1s1 couldn't be verified utterly.
File system verify exit code is 8.
Restoring the unique state discovered as mounted.
File system confirm or restore failed. : (-69845)
Operation profitable.
Relaxation assured that the inconsistencies in all probability arose as a result of a nasty bodily SATA connection — not a failing drive — which has since been corrected (in addition to the scenario permits). That is decided by utilizing an hourly log of S.M.A.R.T knowledge and evaluating CRC error counts, and has occurred earlier than. I’ve no purpose at current to suspect defective bodily media.
