Contribute
Register

"APFSStart:1456" during fresh install of High Sierra

Status
Not open for further replies.
Joined
Feb 4, 2020
Messages
9
Motherboard
MSI Z170A Gaming Pro Carbon
CPU
i7-6700K
Graphics
GTX 1070
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
Everytime I try and fresh install High Sierra, after selecting the USB I'm using as the boot device, I keep getting this code after about 2 minutes of black screen:

APFSStart:1456: Mounting with apfs_efi_osx-748.77.8 efi_container_create:1079: -efi_container_create, Status = 8000000000000007

It then goes away after about 45 seconds, followed by a black screen. During one attempt, out of frustration I pulled the USB out of my rig and to my surprise I was greeted with a grey Clover Boot Manager Screen. However I only had the options to "Boot Windows from Storage" and no options to "Install High Sierra" or anything High Sierra related at all for that matter. So I assumed I could just plug back in the USB, to which I was greeted with the same code mentioned above, and an indefinintely frozen machine.

I've followed all the steps in the Installation Guide (including downloading High Sierra, running Unibeast to create a bootable USB, and finally copying Multibeast to the same USB) and have changed all the appropriate settings on my motherboard (disable VT-d, disable CFG-Lock, enable XHCI Handoff).

I'm kind of at a loss as to what to do next, as I feel like I've tried everything. Is there anyone out there that can help me or who has experienced a similar occurence?
 
Everytime I try and fresh install High Sierra, after selecting the USB I'm using as the boot device, I keep getting this code after about 2 minutes of black screen:

APFSStart:1456: Mounting with apfs_efi_osx-748.77.8 efi_container_create:1079: -efi_container_create, Status = 8000000000000007

It then goes away after about 45 seconds, followed by a black screen. During one attempt, out of frustration I pulled the USB out of my rig and to my surprise I was greeted with a grey Clover Boot Manager Screen. However I only had the options to "Boot Windows from Storage" and no options to "Install High Sierra" or anything High Sierra related at all for that matter. So I assumed I could just plug back in the USB, to which I was greeted with the same code mentioned above, and an indefinintely frozen machine.

I've followed all the steps in the Installation Guide (including downloading High Sierra, running Unibeast to create a bootable USB, and finally copying Multibeast to the same USB) and have changed all the appropriate settings on my motherboard (disable VT-d, disable CFG-Lock, enable XHCI Handoff).

I'm kind of at a loss as to what to do next, as I feel like I've tried everything. Is there anyone out there that can help me or who has experienced a similar occurence?

Hi there.

Are you trying to install High Sierra to a fresh, separate SSD/HDD or are you trying to install on the same one Windows is already on?

:)
 
Hi there.

Are you trying to install High Sierra to a fresh, separate SSD/HDD or are you trying to install on the same one Windows is already on?

:)

I'm trying to install to a new Samsung 860 PRO SATA SSD.
 
I'm trying to install to a new Samsung 860 PRO SATA SSD.

Okay, so why did you get the message about 'Boot Windows from storage', do you think?
 
Okay, so why did you get the message about 'Boot Windows from storage', do you think?

I was assuming that I was only given those options because I had removed the bootable USB, but obviously I'm missing something. Is it not possible to create a fresh install to a brand new blank drive?
 
I was assuming that I was only given those options because I had removed the bootable USB, but obviously I'm missing something. Is it not possible to create a fresh install to a brand new blank drive?

Yes, of course. That's one of the two install options in the guides - fresh install or upgrade.

No need to have anything Windows anywhere near. Create UniBeast stick on a Mac then use that to format new disk and install :thumbup:
 
Yes, of course. That's one of the two install options in the guides - fresh install or upgrade. No need to have anything Windows anywhere near. Create UniBeast stick on a Mac then use that to format new disk and install :thumbup:
Yes, of course. That's one of the two install options in the guides - fresh install or upgrade. No need to have anything Windows anywhere near. Create UniBeast stick on a Mac then use that to format new disk and install :thumbup:
Yes, of course. That's one of the two install options in the guides - fresh install or upgrade. No need to have anything Windows anywhere near. Create UniBeast stick on a Mac then use that to format new disk and install :thumbup:

I probably should have mentioned that all the Unibeast side of things was performed on my Mid 2012 Macbook Pro, and the only reason I'm encountering anything Windows related is because I am attempting to install High Sierra onto a blank SSD which is attached to my Windows 10 gaming rig. My apologies, I am new to this! :)
 
I probably should have mentioned that all the Unibeast side of things was performed on my Mid 2012 Macbook Pro, and the only reason I'm encountering anything Windows related is because I am attempting to install High Sierra onto a blank SSD which is attached to my Windows 10 gaming rig. My apologies, I am new to this! :)

No problem :thumbup:

If you can you need to disconnect the Windows drive. If it is an M.2 style device that's not so easy. Maybe temporarily disable it in BIOS? While there, check your settings are Mac-compatible. I don't want you to do anything to mess up the other installation, so take care.

Basically what I am saying is that any previous Windows installation can confuse the macOS installer and may lead to one or other of the disks getting code not designed for it. Our main installation guide for High Sierra will work and show you most of what you need. Your hardware is nothing to worry about.

The error you posted relates to the APFS file system and is not necessarily a problem, just the last point at which visible logging occurred.

For the black screen, that is probably caused by the GTX1070 as at the point no Nvidia drivers have yet been installed. So ensure you have the "nv_disable=1" boot command selected (press SpaceBar at the Clover boot menu).

:)
 
No problem :thumbup:

If you can you need to disconnect the Windows drive. If it is an M.2 style device that's not so easy. Maybe temporarily disable it in BIOS? While there, check your settings are Mac-compatible. I don't want you to do anything to mess up the other installation, so take care.

Basically what I am saying is that any previous Windows installation can confuse the macOS installer and may lead to one or other of the disks getting code not designed for it. Our main installation guide for High Sierra will work and show you most of what you need. Your hardware is nothing to worry about.

The error you posted relates to the APFS file system and is not necessarily a problem, just the last point at which visible logging occurred.

For the black screen, that is probably caused by the GTX1070 as at the point no Nvidia drivers have yet been installed. So ensure you have the "nv_disable=1" boot command selected (press SpaceBar at the Clover boot menu).

:)

Thanks so much for all your help thus far. I feel like I'm very close to getting it all sorted!

I seem to have progressed slightly further than before. I've just completed a new bootable USB on a different drive and have now made it to the Clover boot menu, and have selected the "Boot OS X Install from Install macOS High Sierra" option (which leads me to believe the USB drive I was using was just insufficient for this job).

Followed all the prompts and attempted to install High Sierra on the SSD, which got about 7/8 of the way and system rebooted (installed progress saying "about 2 minutes remaining"). After reboot I selected the new High Sierra installation from the SSD, but now I'm getting a white stop sign symbol immediately after selecting the new installation which hasn't gone away after about 10 minutes. Upon rebooting again, the "Boot High Sierra from SSD" option is no longer available in the Clover boot menu and I am left only with the "Boot OS X Install from Install macOS High Sierra" option. I also have "nv_disable=1" boot command enabled which hasn't made any difference as yet.
 
Last edited:
Thanks so much for all your help thus far. I feel like I'm very close to getting it all sorted!

I seem to have progressed slightly further than before. I've just completed a new bootable USB on a different drive and have now made it to the Clover boot menu, and have selected the "Boot OS X Install from Install macOS High Sierra" option (which leads me to believe the USB drive I was using was just insufficient for this job).

Followed all the prompts and installed High Sierra on the SSD (I just named it SSD to avoid confusion). System rebooted and I selected the new High Sierra installation from the SSD, but now I'm getting a white stop sign symbol immediately after selecting the new installation which hasn't gone away after about 10 minutes. Upon rebooting the "Boot High Sierra from SSD" option is no longer available in the Clover boot menu and I am left only with the "Boot OS X Install from Install macOS High Sierra" option. I also have "nv_disable=1" boot command enabled which hasn't made any difference as yet.

Okay, to break this down into understandable chunks...

Normally, as long as there is a "Boot from OS X Install ..." option on the left of the menu, you select this after each reboot until it disappears and the job will be complete.

The "Stop Sign" is telling you the boot cannot progress (obviously). Usually this is a failure to read the boot device. Now in your case, because the "Boot High Sierra..." option has gone, this indicates that particular drive has become unreadable, for some reason. A reboot may restore it, but if not, then boot into the installer drive again (External in the Clover menu) and let the installer start - but don't proceed. When you get the menu panel select Disk Utility and run First Aid on your destination drive to see if there are any problems.

:)
 
Status
Not open for further replies.
Back
Top