Mac os could not create a preboot volume for apfs install

#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL HOW TO#
#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL SOFTWARE#
#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL PASSWORD#
#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL MAC#
#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL WINDOWS#

The drive was successfully decrypted in about 7 daysвЂ™ time, and the challenge was to trace down and recover the data by wading through the SSDвЂ™s unknown (and unaccounted) history of erasure.ДЄfter successfully decrypting the clone HDD and regaining unrestrained access to the erased volume, the next step was to perform data recovery. This was achieve by connecting the MacBook SSD clone (HDD) to the original MacBook and using command line to fully decrypt it on The R&D team did certain changes on sector level to begin decrypting the APFS boot drive via command line.

#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL MAC#

The Device Block Size of the original MacBook SSD was 4096 bytes (as compared to 512 bytes on ordinary SSDs), which could be decrypted only on the original Mac device.

The APFS file system on the drive was found to be corrupt, due to which the decryption process was getting hindered.

However, the decryption process couldnвЂ™t complete due to the following reasons: The encryption key unlocked after successful account login was entered to decrypt the Startup volume.

#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL PASSWORD#

The team requisitioned the password for the FileVault-enabled account from the client and entered it to unlock the encryption key that protects the startup volume.

#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL WINDOWS#

Stellar В® R&D team implemented a proprietary technique to reconstruct the necessary information which enabled them to boot the drive from powered-off state and prompt the password screen via a Windows machine.Startup volume so, there was no screen or mechanism to input the decryption key. As the clone was essentially a formatted boot volume with disk-level encryption, macOS couldnвЂ™t boot into the main system on the This step focused on recreating the login screen for entering the password for FileVault enabled account.Mounting SSD clone and recreating the login screen:.Stellar В® R&D engineers broke down this formidable problem into smaller pieces, as follows: Devising a mechanism to enter the password for FileVault-enabled account so as to unlock the encryption key.Mounting the clone on a secondary host machine that could emulate the original MacBook hardware to test out the possibilities of decryption.

#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL HOW TO#

The challenge began right with- how to access the clone of a native MacBook SSD having disk-levelД®ncryption on a secondary host (non-OEM machine)? This would essentially require meeting two necessary conditions. Disk cloning was completed in a dayвЂ™s time.Дecrypting the Mac SSD clone was the most challenging aspect of this data recovery case. The clones were created on two separate HDDs to serve as backup in case of any contingency which was anticipated considering the complexity of this case.

The process copied entire data of the SSD including the information to boot to the operating system on the original drive.

#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL SOFTWARE#

Stellar data care experts used proprietary cloning software to create clones of the MacBook SSD via its HDD disk image. This problem was overcome by using a USB-C to USB 2.0 adapter for connecting and imaging the MacBook SSD, which was completed in 4 days. The disk imaging step however faced an impediment- the MacBook had only one USB-C port which couldnвЂ™t be directly connected to the USB 2.0 Standard-A connector on the external HDD. SSDвЂ™s system and data while it remained inside the MacBook.

Without disk imaging, it wouldnвЂ™t be possible to operate on the native Imaging the Mac SSD was a critical step to obtain a вЂlogicalвЂ™ replica of the drive that could be cloned and further operated to gain access for decryption and data recovery. Techniques followed through the stages of disk cloning, decryption, and data recovery, as follows:ДЎ. Stellar data care experts managed to retrieve the entire data successfully by using a mix of standard and proprietary data recovery toolsВ and OS installation which would overwrite the erased data. Unfortunately, there was no backup of this data, and further, the SSD had been secured with FileVault full-disk XTS-AES 128 encryption for the only user account configured on the MacBook.Д«y the time the MacBook В® was brought to a Stellar В® data recovery service center, it was in an unbootable state. The user then rebooted the MacBook В® in Recovery Mode and used Disk Utility to erase the startup (and only) volume, resulting in loss of 400 GB data stored on the 512 GB SSD. вЂњCould not create a Preboot Volume for APFS to install.вЂќ However, while attempting to erase the volume, the user received an error message. This case outlines recovery of 400 GB data lost from a MacBook В® while it was being prepared for macOS High Sierra installation.ДЄs the standard procedure, the MacBook В® SSD startup volume needed to be erasedВ and reformatted in APFS so as to prepare it for fresh installation

Mac os could not create a preboot volume for apfs install