Can't Boot after Beta 4 Update

Question

Created Oct ’17

Replies 3

Boosts 0

Views 1.6k

Participants 3

Hi all,

I've been moving along pretty smoothly with the BETAs. After today's update, I seem to have run into a pretty major issue.

After the update began, it did what I assume was a normal mid-update-restart. When the machine booted, I was greeted with the prohibitory sign which sticks around for about 30 seconds and then machine turns off.

I booted into disk utility and tried to do a repair. I mounted my macOS partition and had to enter my password since the volume is encrypted. Once it was mounted, I attempted to run a first aid and received the following:

Checking the fsroot tree.
error: invalid dstream.default_crypto_id (0x4), given apfs_fs_flags (0x1)
error: xattr_val: object (oid 0x1002fb2fa): invalid dstream
fsroot tree is invalid
The volume /dev/rdisk2s1 could not be verified completely
File system check exit code is 0

I can still boot into my Windows 10 partition just fine. I'd like to get around having to completely erase and reinstall if possible, but understand it might be a possibility due to living in Apple's weird new borked BETA land.

Thanks!

Boost

Answer 1

trentsartain OP

Oct ’17

So apparently my disk was half way through decrypting. I didn't turn off FileVault, but something apparently did. Because the disk wasn't done decrypting and the update came through restarting the machine, everything got into a weird state. I did end up having to erase and start over.

0

Answer 2

Fuzzygoat OP

Oct ’17

I have a similar problem, I have a late 2014 Fusion Mac, it worked perfectly all through the High Sierra Beta (when it was apparently running APFS) it also worked perfectly after reverting the drive back to the old file system when Apple decided to change things for release. Since release it has worked fine right upto and including the initial beta release of 10.13.1 b1, my problems all started after installing beta2 (or maybe beta3, not sure now)

The machine got pretty much to the end of the beta2 installation and stated that there had been a problem installing the beta and informing me that I needed to reboot. I did as suggested and on restart was presented with the Prohibitory sign you mentioned. Since then I have tried.

Re-installing High Sierra again = Prohibitory sign on reboot.
Re-installing from my Time Capsual backup = Prohibitory sign on reboot.
Rebulding the drive following Apples instructions to reformat the CoreFusion disk and reinstalling HS = Prohibitory sign on reboot.
Manually unmount & erase disk0, disk1, create coreStorage group, create coreStorage vol, reinstalling HS Release = Prohibitory sign on reboot.
Manually unmount & erase disk0, disk1, create coreStorage group, create coreStorage vol, reinstalling HS 10.13.1 Beta = Prohibitory sign on reboot.
Installing Yosemite ... Installs, Machine Works fine.
upgrade to Sierra ... Installs, Machine Works fine.
upgrade to High Sierra = Prohibitory sign on reboot.

The machine is covered by Apple Care, so I have passed it to them here in the UK, Case Number: 100327492058 they have been at it for a week and various engineers still can't work out whats going on. If anyone from Apple reading this knows a solution please add it onto the case number above, as it will probably save myself and Apple a fair amount of wasted effort, money and engineering time. At this stage it looks like they might have to take the machine into the shop and swap (i.e. replace both drives) absolutly ridiculous as both drives are physically undamaged.

Gary

0

Answer 3

liquidmetalin OP

Oct ’17

I have been struggling with the problem of white screen. Even cmd+R does NOT bring up recovery disk/mode into play. After several attempts at single user mode, cmd+s, it finally seems to have sorted and able to login. The only thing I did different in cmd+s than earlier, was I didn't run fsck. Instead just /sbin/mount -uw /, and then reboot/exit. Weird that it worked twice; but if I used fsck first, then on reboot, would again come to white screen.

0