So, I had a kernel panic recently, and on restart, it would get to the "Unlock Disk" screen (first password prompt on a FileVaulted system), progress about 1/16th of the way, get stuck there for a while, and watchdog reboot.

Tried that a few times with no progress, so into Recovery.

Trying to repair with Disk Utility in Recovery got to the "unlocking disk" point, put up an indeterminate progress bar and a spinner, and looked like it was doing nothing.

This is already one step further than a "normal" user would go. On a plain kernel panic. Bad.

Worried that the encryption was corrupt, I force powered down (nothing was repaired), back into Recovery, then Terminal, then used diskutil to unlock without mount...no problem. Phew.

Next - tried to repair, but you can't, beacause *part* of the volume (system) is mounted. Have to force unmount the drive (disk3), then repair that.

Which is happening, and in progress. But how are "normals" supposed to deal with this?

Truly terrible UX.

And, given this, off to DFU.
@dnanian 😳