UpdatePreboot: Treating this APFS Crypto User as a Personal Recovery Key User UpdatePreboot: This is the Personal Recovery Key for this Volume UpdatePreboot: Considering APFS Crypto User EBC6C064-0000-11AA-AA11-00306543ECAC UpdatePreboot: Preboot Volume Target Directory = /Volumes/Preboot/6AAC9D56-EC44-38B3-9C50-1D6DA3020377 UpdatePreboot: Preboot Volume = disk2s2 Preboot UpdatePreboot: Mounting and ensuring as mounted the related Preboot Volume UpdatePreboot: Successfully opened Open Directory database setting AuthODNodeOrNil accordingly UpdatePreboot: Open Directory Database Search Path = (nil=MacOSSearchPathNotMounted) = /var/db/dslocal/nodes/Default UpdatePreboot: MacOS Search Path = (nil=NotMounted) = / UpdatePreboot: Using MacOSSearchPath's child dslocal path as OpenDirectorySearchPath UpdatePreboot: Using GivenVolumeMountPointOrNilIfNotMounted as MacOSSearchPath UpdatePreboot: No custom Open Directory path given UpdatePreboot: The Target Volume's OpenDirectory (non-special kind) user count is 1 and the Recovery (any of 3 kinds) user count is 2 UpdatePreboot: Commencing operation to update the Preboot Volume for Target Volume disk2s1 Macintosh HD Finally, run diskutil apfs updatePreboot on your now unlocked boot volume $ diskutil apfs updatePreboot disk2s1 Authenticate with your usual password $ diskutil apfs unlockvolume disk2s1ģ. Now run diskutil apfs unlockvolume on your boot volume. | APFS Volume Disk (Role): disk2s3 (Recovery) | APFS Volume Disk (Role): disk2s2 (Preboot) | APFS Volume Disk (Role): disk2s1 (No specific role) Run diskutil apfs list and find your boot volume $ diskutil apfs list Boot into the OS installer/recovery drive.Ģ. I ended up creating a bootable USB drive so I could get to an OS 10.13 terminal window.Īfter some research and a lot of trial and error I came up with a solution that worked for me:ġ. To make matters worse it wouldn't even boot into the recovery partion (although it would boot into the password recovery utility). I had the same problem on my 15" MacBook Pro early 2011 with a FV2 encrypted homemade fusion drive after it slept during install. Migration type 3 (decrypting) state 1 (paused) pause state 0 (unknown) bash-3.2# diskutil apfs listCryptoUsers /dev/disk2s1īackground decryption migration (data on disk becoming plaintext) in progress Is there have some way to have to continue decrypting in Recovery Mode? In previous coreStorage can be done this things by manual activating corestoraged in terminal to continue encrypting/decrypting, but in this APFS does have any way to migration successful or revert the state? If you used Disk Utility from macOS Recovery, you can now restart your Mac: choose Apple menu > Restart.Same as my situation, but once I've use diskutil apfs decryptVolume to decrypt volume, but after I enter this command, quickly it crashed my macOS 10.13, then I can't boot my mac and also can't read any files anymore, after I boot into Recovery Mode to unlock the volume with my passphrase, all the encrypted files on the volume can be list and not modified, but they can't decrypt by FileVault2 and let me read raw encrypted data, and I use diskutil to check crypto users, that said I'm in decrypting action but paused state of my volume? The order of repair in this example was Macintosh HD - Data, then Macintosh HD, then Container disk4, then APPLE SSD. Keep moving up the list, running First Aid for each volume on the disk, then each container on the disk, then finally the disk itself.
0 Comments
Leave a Reply. |