fsck_apfs check error

Just after upgrading to High Sierra for few days and running with APFS auto-conversion

I had 2 kernel-panics (almost forgotten that those exists...) and now I got this:

-bash-3.2# fsck_apfs /dev/rdisk2s2

** Checking volume.
** Checking the container superblock.

** Checking the EFI jumpstart record.

** Checking the space manager.

** Checking the object map.

** Checking the APFS volume superblock.

** Checking the object map.

** Checking the fsroot tree.

error: drec_val object (oid 0x76ed006): invalid type (0)

fsroot tree is invalid.

** The volume /dev/rdisk2s2 could not be verified completely.


I don't have a clue what "error: drec_val object XXX invalid type (0)" means.

So what Do I do now? Pray to the gods of internet since APFS sources aren't released,

there is no documentation and now what? I can go and reformat my drive because

that the base fs can't be repaired? Really?

I'm seriously amazed at the quality and implementation of such major change as APFS.

iMac, macOS High Sierra (10.13), null

Posted on Oct 19, 2017 6:15 AM

Reply
19 replies

Oct 19, 2017 7:53 AM in response to anonyme4321

I don't have disk errors, and I am absolutely sure about it. The SSD drive is fault free. I made sure about that with by booting a linux, runing hdparm, smart tests and re-checking logs for any kind of hardware faults.


It's not a hardware issue- and macOS kernel would spill something in dmesg if there is any kind of hardware issues.

I work with BSD/Unix'es for more then 20 years so I know a bit about it, and macOS is BSDish os with a fancy GUI 😉

Nov 4, 2017 8:02 PM in response to Synaps1s

drec_val probaby means "disk record"


The upgrade notes i saw said APFS is currently suggested only for optimal SDD (not even sata attached sdd necessarily: apple built-in ssd slot ssd). I read that shortly after an initial release High Sierra stopped making APFS default for non-ssd drives due to various reported difficulties. And that High Sierra either no longer formats SATA to apfs or that apfs had been fixed (whichever comes first, but the default choice for upgrade should work).


Your free to use UFS if you like: the high sierra upgrade notes say you can still choose UFS over APFS (any FS apple supports for that matter, which is two or just a few). And APFS - I'm unsure where you saw any apple legal statement that they were not releasing source code to developers. can you cite where you found any such statement?


You maybe had a disk failure or perhaps a power outage caused the loss. or, maybe you tried running "fix disk" on a mounted disk which caused corruption. At any rate you have a broken record and who knows if that belies some further problem underneath.


Anyway the advice you were given early on, "reformat your disk", is likely the most direct and sure to work cure.


I'm not conviced Apple didn't provide a "chkdsk" that works nor that apple's fsck didn't already fix the fixable errors. As I said earlier: "fsck" and "chkdsk" never did fix "any or all problems". Moreso forced fixes by fschk NORMALLY do cause corruption (in my experience, having applied such a few times on disks with real issues: such as the EZ-DRIVE bug that Maxtor hard drives shipped with).


as far as dual booting: what is normal is that the internet is not a nice place: linux has been known to corrupt WIndows10 and Apple things, WIndows 10 has been known to corrupt linux and apple, and Apple ... well i'm not sure it's often just "never released". all of the previous never admit this until one is looking for articles about "why it happened / how to fix" - and it's not nice to say these things after one is aready up the creek w/o a paddle.


SUMMARY: Apple is not corrupting your system. It's the least corrupted system with the greatest uptime I've ever had (all things considered - this includes that it's running allot of upgrades and apple softwares, whereas compared to my linux box - linux is stable but not upgrading and not running multimedia heavy apps). Note I only use app store though - and do not install apps that "alter the OS". Also Apple is not preventing you from developing.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

fsck_apfs check error

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