I've spent about a week reading about everyones issues with filevault and crashing or locking the hard drive. Nothing seems to work to unlock it and the password that is in icloud doesn't work, but instead crashed the drive everytime. What can we do now? I've tried to reinstall High Sierra because my startup disk is now APFS and it won't install because it's locked. When I do the internet recovery it tries to install Sierra, is there a way to force High Sierra over the internet recovery? Will an update fix my locked drive because if I can't access it how will an update fix it? Please help! Where is Apple in any of this?
High Sierra 10.13 beta 3 FileVault crash locked startup HD
I have the same problem. Locked up at 91% and cant enter any password anywhere. 0KB disk space left. tried to diskutil apfs decrypt/encrypt, nothing working.. Does it help to keep laptop on before sign in, or does filefault only encrype while logged on? Disk Utility Programm also not working - First Aid always fails with error 8. Tried target mode with another beta laptop; didnt work. although thtat laptop was still on beta 2. filevault was only activated in beta 3 if Im right, and yes sadly backup was disabled during beta 1&2. Holding out for a solution..
Thinking about cloning my HD to another bigger HD to get more space. dont know if that works.
I don't think that will work and I've tried everything you mentioned as well. Nothing works so far and Apple doesn't have any solutions yet. I hope there is a fix, because a lot of people have the same problem. It's completely unmountable or unlockable. The only thing I can think of is waiting for Internet Recovery to push the High Sierra 10.13 out and it going around encryption that way without erasing our data we can reinstall. I've tried many times to find a way to boot Internet Recovery and then force the High Sierra re-install via USB/bootable USB but it never let's me switch. The Internet Recovery now always tries to reinstall Sierra, which doesn't work.
any news?
Nohting and tried almost everything. I even loaded High Sierra 10.13 beta 4 on a USB to try and unlock the drive. It cannot mount the High Sierra 10.13 beta 3 drive that's got all my files on my MacBook Pro. I'm extremely upset that they put out a beta this horrible. I've never had an issue with beta's in the past this bad. The beta 3 is more like an Alpha, not beta for users to test. I have been through many apple support calls and visited 2 apple shops with no solutions. I thought they would have a solution for such a major problem, but they aren't even working on it from what I understand. Anyone else have any luck?
I think we have no other option other than wait for the next beta, since beta 4 still doesn’t support apfs decryption...
Is there still no APFS decryption?
Nope, hopefully next beta, and hopefully it will work :-)
Same here with beta 3. Everything was ok, until I rebooted my machine in the morning and just saw the no disk icon.
In verbose mode, I saw:
CoreStorageFamily: unlockVEKs(...) VEK unwrap failed.
Unlocking/mount in the recovery Disk Util worked.
So I decided to restore 10.12 from TS and wait for a more stable beta.
What really ***** is Apples policy in the Feedback assistant. It is completely useless in the dev betas (not even stating HS builds there). Feedback on a radar was "The Feedback Assistant is only for public beta users". Why do they offer then an old version of it in the dev betas?
Did it work with beta 5?
I was having the same issue with Public Beta 5. Tried all the stuff that's been suggested.
I think this is what finally did it...patience. 😉
1. Boot in safe mode.
2. Turn off screen saver
3. Set screen to never sleep.
4. Turn brightness all the way down (so as not to damage your screen and let it run overnight)
FileVault was was stuck at 11% late last night, and was complete upon coming back to my computer at 7pm today.
Hope that helps! Downloading Public Beta 7 now and looking forward to a successful update. 🙂
Hi,
I can't even boot in safe mode (holding shift), nor in single user mode, because when I get into the FileVault login screen, my Mac does not recognize my FileVault password. The resetpassword command does not work. Is it possible to let my Mac continue the disk encryption from the FileVault login screen?
Now I have an APFS container with two partitions: one (the locked one) with the first or second beta of 10.13 and the other one with Beta 8 on it.
I had the same issue today. I thought at first my disk was dead. Tried everything, the only way I fixed it was to format the disk and start from scratch
I take it there is still no fix on the horizon?
Has there been any murmur from ACME? Does anyone over there even give a s*** anymore?
The official release of 10.13 causes the same crash. It is clearly a known/documented issue. I find it staggering that they released it without fixing this.
My upgrade completed successfully. After poking around for a couple hours I thought "Let's reboot and make sure we can get back in".
...big mistake.
Has anyone successfully recovered any data from an affected machine?