Benches MacBooks

5

SSD 1TB | warning: inode_val: object (oid…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

After installing to MacOS 10.14.2, I ran a First-aid (including on Recovery Mode and Recovery Mode using a MacOS Mojave 10.14.2 USB Installer) on my 1 TB SSD and received this following error:

Running First Aid on “Macintosh HD” (disk1s1)
Performing fsck_apfs -n -l -x /dev/rdisk1s1
Checking the container superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking volume.
Checking the APFS volume superblock.
The volume Macintosh HD was formatted by diskmanagementd (945.230.6) and last modified by apfs_kext (945.230.6).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the extent ref tree.
Checking the fsroot tree.

warning: inode_val: object (oid 0x2a6975): invalid bsd_flags (0x10)


Verifying allocated space.
Performing deferred repairs.
The volume /dev/rdisk1s1 appears to be OK.
Operation successful.

It seems first-aid cannot repair it at all. So formatted the hard disk using USB Installer on Recovery Mode and reinstalled MacOS again. After that, I ran first-aid again and it did not show the warning. Then after one day, I ran again and here it is showing the same error. System freezes sometimes, which should not happen to this as it is a high specs machine and normal browsing should not freeze it.

I bought the MacBook Pro 15 inch one month ago. Any suggestion to resolve the issue?

System Specification:

MacBook Pro 15 Inch Late 2018

Processor: Intel 8th Generation I9 2.9 GHz

RAM: 32 GB

GPU: Radeon Pro Vega 20 4GB

Hard Drive: 1 TB SSD

🔧 Closest iFixit match: MacBook Air 13" Retina Touch ID 2018-2020
Take-apart guides & videos on iFixit →
Double-check this is your exact model before ordering parts.

5 replies

Sign in or join Beachball Help to reply.

  1. 0

    Tesserax

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    At this point, I would suggest that you make a Genius Bar appointment at your local Apple Store or Apple Authorized Service Provider to have them take a look. You shouldn't of had a need to have to re-install macOS on a new device.

  2. 0

    Tesserax

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    At this point, I would suggest that you make a Genius Bar appointment at your local Apple Store or Apple Authorized Service Provider to have them take a look. You shouldn't of had a need to have to re-install macOS on a new device.

  3. 0

    Ashiq.CS

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I converted 0x2a6975 into decimal and ran "ls -I Filename" command on my home directory. It seems the file name returned is OneDrive which has the inode number 2779509 (0x2a6975). Because "OneDrive" is badly named due to not having spaces between two words, hence it is showing that error. Good to know it is nothing to do with HDD rather than error in naming a folder.

    Still I will book an appointment with Genius Bar to follow up with my findings. Thank you.

  4. 0

    terapun

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    This seems to be a consistent issue with users using OneDrive and Mojave:

    https://answers.microsoft.com/en-us/msoffice/forum/all/disk-utility-warnings-in-os-x-mojave-and-onedrive/8452b5fe-4f1a-44a7-a56b-c35ceec41129

    https://discussions.apple.com/thread/8630489

    I had this issue and conducted multiple recovery installs. Ended up not re-installing OneDrive, using web OneDrive and going back to Dropbox until this is fixed.

  5. 0

    Ashiq.CS

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I converted 0x2a6975 into decimal and ran "ls -I Filename" command on my home directory (~Users). The file name returned was OneDrive which had the inode number 2779509 (0x2a6975). I guess "OneDrive" is badly named due to not having a space between two words, hence it is showing that error on APFS file system, but I could be dead wrong on that.

    Glad to know it is nothing to do with HDD rather than error in naming a folder.