What Would Cause This? Exit Code is 8

[BigMcGuire]

Device: 2017 MBP 13' TB (512GB SSD). (Less than 1.2 months old).

Background: Wife started noticing Arq Backup reporting files missing with Chrome Browser when attempting to do backups. Then Chrome started losing profile information, then iMessages lost all messages, stuff wouldn't load.

So I decided to do a first aid and it said I had to boot into recovery to do so. So I did and got this:

So, wife backed up her data, and I erased the partition, formatted it with APFS Encrypted, and reinstalled Mac OS. First Aid shows 100% fine now. Wife is setting up laptop again.

Anything we should be worried about? Everything seems fine now.

Bing'ing the problem "System Check Exit Code is 8" seems to just recommend formatting partition. So we did.

 

[campyguy]

Reads to me the drive encountered file system corruption. It happens and a reformat has been my course of action. FWIW I'm not sold on APFS yet, holding pat on HFS+ for all of the Macs in my company except for the new iMPs that were APFS out of the box...

 

[ApfelKuchen]

An Exit code of 8 doesn't tell us much - that's the typical "repair failed" code, regardless of cause. Read a bit higher up the list and you'll get a better idea of why the repair failed (Object map is invalid). There may be other errors that weren't captured by that screen shot - you'd have had to scroll up to see them.

The fact that it also says, "Restoring the original state found as mounted" is an argument in favor of APFS. That gave you a chance to backup that you likely wouldn't have had under HFS+.

Will the issue return? If it does, then it's time to start looking for a hardware-related problem. Most likely though, you encountered one-time damage to the file system. Now that it's fixed, it may be a long time before you run into something like it.

Regardless, this is a reminder that no matter how new the computer may be, a regular backup is highly advised.

 

[BigMcGuire]

An Exit code of 8 doesn't tell us much - that's the typical "repair failed" code, regardless of cause. Read a bit higher up the list and you'll get a better idea of why the repair failed (Object map is invalid). There may be other errors that weren't captured by that screen shot - you'd have had to scroll up to see them.

The fact that it also says, "Restoring the original state found as mounted" is an argument in favor of APFS. That gave you a chance to backup that you likely wouldn't have had under HFS+.

Will the issue return? If it does, then it's time to start looking for a hardware-related problem. Most likely though, you encountered one-time damage to the file system. Now that it's fixed, it may be a long time before you run into something like it.

Regardless, this is a reminder that no matter how new the computer may be, a regular backup is highly advised.

Yeah we were able to boot and save all the data (even stuff my wife hadn't put into iCloud). She was up and running in less than 15 mins thanks to the speed of the MBP. Will do if we get this again - so far it's working fine.

Yeah we do TimeMachine backups and I use Arq Backup to take all her files and back them up to B2 - and she uses Dropbox, iCloud, and Google Drive. (For work). But we figured we'd just do a fresh Mac OS Install (she wanted to).

Thanks for the help all.