You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: lvpj65
lvpj65 Author
User level: Level 1
6 points

Disk Utility fsroot tree warnings (NOT invalid)

Hello to the community.

I’m running macOS 10.14.6 on a MBP mid2012.

Disk Utility is unable to repair the following errors, even when it’s running in recovery mode.

Verification code is 0.

I got the same results with fsck -fy command in single user mode.


I’ve seen comments that an invalid fsroot tree can’t be repaired but i don’t get that "invalid tree" line.

I did some searches but could not get any results for those errors.

Here are the details:


Checking the fsroot tree.

warning: drec_key: invalid hdr.obj_id (0x7)

warning: drec_val object (oid 0x7): invalid flags (0x205)

warning: drec_val object (oid 0x7): invalid type (5)

warning: directory valence check: directory (oid 0x7): orphan directory record

warning: inode_val: object (oid 0x302491319): invalid internal_flags (0x2008000)

warning: invalid xf.xf_type (0xf)

The exact same list of errors appear during the check of the snapshot (1 of 1), even after deleting and recreating it.


Conclusion of the test is "appears to be OK".

System and applications seem to run just fine.

I have no idea of the nature of these warnings.


Is there any step to take before erasing that SSD in recovery mode, reinstall a new system and import whatever Timemachine is able to rebuild ?


If anybody knows what this is all about, thanks to share knowledge.



MacBook Pro 13″, macOS 10.13

Posted on Sep 13, 2022 3:32 PM

Reply
Question marked as Top-ranking reply
User profile for user: HWTech
HWTech
User level: Level 9
60,362 points

Posted on Sep 15, 2022 11:25 AM

Odd that those are warnings instead of errors. Sure seem a lot more like errors. Are you booting to the same or newer version of macOS when you run First Aid in Recovery Mode? If not, then maybe that can explain it. Make sure you are booting into macOS 10.14+ when running First Aid.


Unfortunately if First Aid is unable to repair something on an APFS volume and you are running First Aid from 10.14+, then the only option is to erase and reinstall since Apple has not released the necessary APFS documentation. Most "warnings" I have seen could usually be ignored, but these don't look like the usual "warnings" I've ever seen as these look more like actual errors. I wouldn't feel save ignoring them either.

View in context

Similar questions

4 replies
Question marked as Top-ranking reply
User profile for user: HWTech
HWTech
User level: Level 9
60,362 points

Sep 15, 2022 11:25 AM in response to lvpj65

Odd that those are warnings instead of errors. Sure seem a lot more like errors. Are you booting to the same or newer version of macOS when you run First Aid in Recovery Mode? If not, then maybe that can explain it. Make sure you are booting into macOS 10.14+ when running First Aid.


Unfortunately if First Aid is unable to repair something on an APFS volume and you are running First Aid from 10.14+, then the only option is to erase and reinstall since Apple has not released the necessary APFS documentation. Most "warnings" I have seen could usually be ignored, but these don't look like the usual "warnings" I've ever seen as these look more like actual errors. I wouldn't feel save ignoring them either.

Reply
User profile for user: lvpj65
lvpj65 Author
User level: Level 1
6 points

Sep 15, 2022 2:13 PM in response to lvpj65

Thanks BDAqua and HWTech.


The recovery system is the one booting with command-R. That should be the same version than the one installed.


I also cloned that SSD to an HFS+ HD w/ CCC , which is able to create an external recovery volume.

I got the same result after booting from there.


I re-installed the system just in case that would clear the warning list.

I have another external boot disk with Monterrey, cloned from my Macmini, but that MBP is limited to 10.15, a system i don’t trust. I may be wrong... I doubt that updating the system could repair the APFS structure, anyway.

I’m going to build a 10.15 system on another disk and try to repair the SSD from Catalina Disk Utility to see if the warning are still listed.


I’ll report success or (more probably) failure of the attempt...


Reply
User profile for user: HWTech
HWTech
User level: Level 9
60,362 points

Sep 16, 2022 5:30 AM in response to lvpj65

lvpj65 wrote:

Thanks BDAqua and HWTech.

The recovery system is the one booting with command-R. That should be the same version than the one installed.

Bad assumption. In theory yes, but in practice not necessarily. You can tell what installer booted by looking at what OS is listed for "Reinstall macOS xxxxxxx" where "xxxxxxx" is the version of macOS. Many times it may boot to the installer for the OS which originally shipped with the OS from the factory.


I re-installed the system just in case that would clear the warning list.

Unless you erased the whole physical drive (Intel Macs only, erasing hidden Container is also an option especially for Apple Silicon Mac)), then you will still have the file system issue. A new file system must be created to correct the problem.


FYI, since you use bootable clones, be aware that bootable clones are a thing of the past with Apple Silicon Macs, and a "hope it works" for Intel Macs running macOS 12.x Monterey. Plus even to attempt to make a bootable clone of macOS 11.x+ requires doing some extra work. See this article from the CCC for more details about the situation:

https://bombich.com/kb/ccc6/cloning-macos-system-volumes-apple-software-restore

Reply

Disk Utility fsroot tree warnings (NOT invalid)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up