- #MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL HOW TO#
- #MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL INSTALL#
- #MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL FULL#
- #MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL MAC#
This article will show you how you can deal with it.
![mac os could not create a preboot volume for apfs install mac os could not create a preboot volume for apfs install](https://i.stack.imgur.com/lEdZV.png)
#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL HOW TO#
It’s best to be prepared by knowing how to deal with the error that could hamper your macOS reinstall in the future. Unfortunately, it’s hard to say that it won’t happen to you.
#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL MAC#
Not a lot of Mac users are familiar with it yet.
#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL INSTALL#
There should not be an error with this method.A message pops up saying that it could not create a preboot volume for APFS install when you’re trying to reinstall the OS. Go to reinstall macOS and choose the internal hard drive for installation. Once the drive is created plug into the tanked computer- hold down option and choose to boot from the installerģ. Sudo /Applications/Install\ macOS\ High\ Sierra\ Beta.app/Contents/Resources/createinstallmedia -volume /Volumes/HighSierra -applicationpath /Applications/Install\ macOS\ High\ Sierra\ Beta.app -nointeraction &say Boot drive createdĢ. Create a bootable thumbdrive on another computerĮxcept I needed to change the command to this: Solution for error when you see "Could not create a preboot volume for APFS":ġ. If you get that preboot error I would suggest creating a bootable thumbdrive from another computer and using that to enter recovery mode and doing the install this way. But either way the lesson here is don't erase the internal hard drive from diskutility. In hindsight I know I shouldn't have erased that drive, and I likely could have reformatted disk 1 from terminal and seen if it would repopulated in diskutility then. It then populated when I did the reinstall from the install thumbdrive. I was able to then format it again as APFS.
![mac os could not create a preboot volume for apfs install mac os could not create a preboot volume for apfs install](https://i.ytimg.com/vi/mYDeMPmpV9M/hqdefault.jpg)
what eventually worked was somehow the drive appeared when I booted into recovery mode with the install thumbdrive and having another thumbdrive in the internal drive finally appeared. I created a bootable thumbdrive with high sierra from another computer and used that to boot up, and still the internal drive wasn't an option on diskutility. This didn't work either since it couldn't find the internal hard drive. I ended up trying to create a backup from another computer and installing the backup to that. The internal disk0 drive did not come back. I eventually made a really stupid move from diskutility and from the disk0 drive itself I right clicked and chose to Erase, somehow thinking what harm could be done at this point, thinking it would erase and reappear. This made things interesting so I tried reformatting the drive with the unencrypted APFS and still same error. Went into the reinstall macOS and as it worked through the 8 minutes it would stop at the end with a pop up message saying "Could not create a preboot volume for APFS". Went to reinstall high sierra (was currently running beta 8), went into recovery mode (Command +R at boot), erased the hard drive in diskutility and reformatted it in APFS encrypted.
![mac os could not create a preboot volume for apfs install mac os could not create a preboot volume for apfs install](https://media.fonepaw.com/mac-update/could-not-create-a-preboot-volume-for-apfs-install.jpg)
I had this same problem happen to me recently. select internal HD as boot drive and then reboot dirty install of High Sierra Beta 7 over top the exisitng OS (Beta 7)Ģ. The fix was to do as Kode54 described in the response above:ġ. Using Terminal and diskutil cmdline, forced it, but then it wouldn't bless. I converted my TimeMachine volume to APFS, but boot volume wasn't having it. If it does show Convert to APFS under the Edit menu, give it shot.
![mac os could not create a preboot volume for apfs install mac os could not create a preboot volume for apfs install](https://i.stack.imgur.com/Rm7ey.png)
It's really not worth the effort of getting it up and running again even if it's just a sacrificial test machine or VM.
#MAC OS COULD NOT CREATE A PREBOOT VOLUME FOR APFS INSTALL FULL#
If the full GUI Disk Utility doesn't "offer" to convert your boot volume, don't force it. *Nota Bene: Manually converting a boot volume via commandline in terminal is hazardous/unfriendly. I just had to be very, very patient, and keep my hands off the mouse and keyboard out of fear of interrupting whatever process it was going through to tie the boot files to the APFS converted disk partition. Then I looked up the isse on Google and it brought me to this thread.įollowed that same advice, I did a dirty re-install of High Sierra Beta 7, that fixed enough of the partition entries and blessing to force it to boot the Disk02s. Spent a lot of time trying to manually bless the drive with subsequent errors. Then I got this error: Could not create preboot volume for APFS install I did that conversion to disk0s2 (my HFS+ data volume). I suspected I could conver to APFS using Terminal+diskutils. I know from times past the cmdline DiskUtils has way more options than the GUI. I decided that the Boot Volume should also be converted but did not see the Convert to APFS volume under the Edit menu. I converted the TimeMachine volume of to APFS as it showed up under the Edit Menu in Disk Utility. I have an external drive connected as a Time Machine volume. I have a single SATA drive internal, on a Mac Mini (boot volume).