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: GuyPicks
GuyPicks Author
User level: Level 1
34 points

exit code 8

File system check exit code is 8. What is this ?

I can't verify my boot SSD drive. Is my SSD drive going bad?


Any help is appreciated, thanks


GuyPicks

Mac Pro, macOS 10.14

Posted on Nov 22, 2019 5:18 AM

Reply

Similar questions

8 replies
User profile for user: John Galt
John Galt
User level: Level 10
146,348 points

Nov 22, 2019 7:38 AM in response to GuyPicks

Repair a storage device in Disk Utility on Mac - Apple Support:


Note: If you’re checking your startup disk or startup volume, restart your computer in macOS Recovery, ...


Apple doesn't publicly document those error codes. Does DU's "Details" reveal anything of interest?


For example (using "live mode" though)


Verifying file system.
Volume could not be unmounted.
Using live mode.
Performing fsck_apfs -n -l -x /dev/rdisk1s1
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.
Checking the snapshot metadata tree.
Checking the extent ref tree.
Checking the snapshots.
Checking snapshot 1 of 11.
Checking snapshot 2 of 11.
Checking snapshot 3 of 11.
Checking snapshot 4 of 11.
Checking snapshot 5 of 11.
Checking snapshot 6 of 11.
Checking snapshot 7 of 11.
Checking snapshot 8 of 11.
Checking snapshot 9 of 11.
Checking snapshot 10 of 11.
Checking snapshot 11 of 11.
Verifying allocated space.
The volume /dev/rdisk1s1 appears to be OK.
File system check exit code is 0.
Restoring the original state found as mounted.
Operation successful.

If you're concerned though, you should always contact Apple before AppleCare runs out.

Reply
User profile for user: John Galt
John Galt
User level: Level 10
146,348 points

Nov 22, 2019 7:55 AM in response to GuyPicks

That's an aftermarket SSD, so follow its manufacturer's instructions regarding warranty support.


In any event you must comply with this Note from Repair a storage device in Disk Utility on Mac - Apple Support:


Note: If you’re checking your startup disk or startup volume, restart your computer in macOS Recovery, ...


It can't be modified while your system is running from that disk.

Reply
User profile for user: GuyPicks
GuyPicks Author
User level: Level 1
34 points

Nov 22, 2019 7:46 AM in response to John Galt

I don't have apple care. Here's my specs and first aid report:

Running First Aid on “Container disk6”

NOTE: First Aid will temporarily lock the startup volume.

Verifying storage system

Using live mode.

Performing fsck_apfs -n -x -l /dev/disk5s2

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 hfs_convert (748.1.47) and last modified by apfs_kext (945.275.8).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking snapshot 1 of 16.

error: directory valence check: directory (oid 0x3): nchildren (355) does not match drec count (356) 

warning: snapshot fsroot tree corruptions are not repaired; they'll go away once the snapshot is deleted

Checking snapshot 2 of 16.

error: directory valence check: directory (oid 0x3): nchildren (853) does not match drec count (854) 

Checking snapshot 3 of 16.

error: directory valence check: directory (oid 0x3): nchildren (891) does not match drec count (892) 

Checking snapshot 4 of 16.

error: directory valence check: directory (oid 0x3): nchildren (927) does not match drec count (928) 

Checking snapshot 5 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1008) does not match drec count (1009) 

Checking snapshot 6 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1044) does not match drec count (1045) 

Checking snapshot 7 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1080) does not match drec count (1081) 

Checking snapshot 8 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1120) does not match drec count (1121) 

Checking snapshot 9 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1156) does not match drec count (1157) 

Checking snapshot 10 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1192) does not match drec count (1193) 

Checking snapshot 11 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1232) does not match drec count (1233) 

Checking snapshot 12 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1268) does not match drec count (1269) 

Checking snapshot 13 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1304) does not match drec count (1305) 

Checking snapshot 14 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1384) does not match drec count (1385) 

Checking snapshot 15 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1443) does not match drec count (1444) 

Checking snapshot 16 of 16.

error: directory valence check: directory (oid 0x3): nchildren (1515) does not match drec count (1516) 

Checking the extent ref tree.

Checking the fsroot tree.

error: directory valence check: directory (oid 0x3): nchildren (1516) does not match drec count (1517) 

warning: apfs_num_other_fsobjects (78) is not valid (80)

Checking volume.

Checking the APFS volume superblock.

The volume Preboot was formatted by newfs_apfs (748.1.47) and last modified by apfs_kext (945.275.8).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking the extent ref tree.

Checking the fsroot tree.

Checking volume.

Checking the APFS volume superblock.

The volume Recovery was formatted by newfs_apfs (748.1.47) and last modified by apfs_kext (945.275.8).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking the extent ref tree.

Checking the fsroot tree.

Checking volume.

Checking the APFS volume superblock.

The volume VM was formatted by newfs_apfs (748.1.47) and last modified by apfs_kext (945.275.8).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking the extent ref tree.

Checking the fsroot tree.

Verifying allocated space.

Performing deferred repairs.

error: nchildren of inode object (id 3) does not match expected value

Deferred repairs failed.

The volume /dev/disk5s2 could not be verified completely.

Storage system check exit code is 8.

Operation successful.

Reply
User profile for user: GuyPicks
GuyPicks Author
User level: Level 1
34 points

Nov 22, 2019 6:14 AM in response to John Galt

Thanks for responding John,

I'm using Disk Utility first aid to check the file system and it found errors but can't fix them and I get the (File system check exit code is 8) error.

My system isn't locking up but do have some quirkiness in OSX and some apps. Dropbox, Avid Pro Tools, iLok cloud...ect.


That's why I did first aid in the first place. The SSD is not yet a year old. It's raising concerns.

I did backup the SSD drive. :)


Thanks John

Reply

exit code 8

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