Contribute
Register

Install fails ( abnormal code: 1 )

Status
Not open for further replies.
Joined
Oct 13, 2011
Messages
42
Motherboard
Asus Z87-A
CPU
i7-4770
Graphics
GTX 650 Ti
Mac
  1. iMac
Hey guys,
I've triggered the installation normally from Sierra and after reboot, it always gets stuck at the attached screen. Any idea about what could I do to make it work? Thanks!
2017-09-27-10.30.36.jpg
 
I'm having the same problem.. could be because of not adding nullcpumanagement kext? I didn't add it and it might be stalling on trying to load the cpu management. I don't know.
 
Typically when I hit these kinds of problems I remove stuff and try again. Sound fixes, USB fixes, Power management fixes, all that stuff, especially if you're coming from a Sierra system to a High Sierra System or using a clover EFI folder from a working Sierra, is a possible culprit. config.plist patches either may not work if they worked for Sierra or worse, brick your system.

Try reviewing the clover EFI folder you're booting, and temporarily removing from both /kexts/other (or /S/L/E or /L/E if you put any non-vanilla kexts there) and config.plist any USB, sound, or power management fixes. The goal being to get to a broken but booting system possibly without all USB working, no sound, and no power management and crappy VESA graphics until you can fix each of those issues.

You might try booting with apfs.efi in /drivers64UEFI (or wherever appropriate for your system) (/drivers64UEFI/EmuVariableUefi-64.efi causes install issues for some systems so remove that temporarily if you have it), kexts/other just with FakeSMC.kext and your ethernet kext, using USB2 port on upper back of machine. Remove or disable all USB and sound patches in config.plist for now. As you make config.plist changes keep the earlier "working" one around because at clover boot you can manually override using config.plist and use instead, e.g., config-1.plist.
 
Thanks for the suggestion.. I would try it but I have a major problem now. I am using two SSD's, my main SSD is a 960 EVO Nvme and the other a regular 850 EVO as my backup. The problem now is that when trying to restore my system using Carbon Copy Cloner I cannot locate my main 960 EVO ssd to restore to. I don't know how to go about restoring so I can try the upgrade again.

Anyone have any ideas about this?
 
Is one or the other now an apfs drive? What is the output from `diskutil list` in terminal.app? You're saying from Sierra on the 850 EVO you run CCC and it can't see the 960 EVO? Did you install High Sierra to the 960 EVO and it was converted to apfs? I don't know if CCC supports apfs.
 
I think that is what happened. High Sierra failed to install but must have changed the file system. I cannot see the 960 EVO when booting into my backup. Neither in CCC or in Disk Utility..
 
I have no patches and no extra kexts installed as for my configuration Sierra works flawless "out of the box". Just in case, hoping it helps, I've posted here my config.plist. My kexts/Other is empty and in /drivers64UEFI I have:

AppleImageCodec-64.efi
AppleKeyAggregator-64.efi
AppleUITheme-64.efi
DataHubDxe-64.efi
FirmwareVolume-64.efi
FSInject-64.efi
OsxAptioFix2Drv-64.efi
OsxFatBinaryDrv-64.efi
SMCHelper-64.efi
VBoxHfs-64.efi
 

Attachments

  • config.plist
    1.8 KB · Views: 224
Hmm while I was playing around with the High Sierra betas I could always load my Sierra and see the apfs-formatted SSD drive. I run Sierra on an nvme with @RehabMan and PikeRAlpha's NVME fixes and High Sierra on an SSD. So Sierra can read apfs disks ok far as I can tell.

So you have Sierra on an SSD and you installed High Sierra to an NVME. Now Sierra can't see the NVME. It could before, so you had the NVME fixes applied in Sierra? HackrNVMEFamily.kext etc? You're booting clover from the Sierra SSD with the NVME fixes in it?
 
I have no patches and no extra kexts installed as for my configuration Sierra works flawless "out of the box". Just in case, hoping it helps, I've posted here my config.plist. My kexts/Other is empty and in /drivers64UEFI I have:

AppleImageCodec-64.efi
AppleKeyAggregator-64.efi
AppleUITheme-64.efi
DataHubDxe-64.efi
FirmwareVolume-64.efi
FSInject-64.efi
OsxAptioFix2Drv-64.efi
OsxFatBinaryDrv-64.efi
SMCHelper-64.efi
VBoxHfs-64.efi

Where is FakeSMC.kext? Did you put it in /S/L/E or /L/E? You need it in /kexts/Other or installed to /S/L/E or /L/E to boot.

You should put the latest apfs.efi in drivers64UEFI, as far as I know it won't hurt if it's not needed.

What other non-vanilla kexts have you installed?

Boy that config.plist is the barest config I've ever seen, doesn't set SMBIOS or nothing. Not saying it's not valid, not a config.plist expert, but boy is it bare. You sure you're booting Sierra using that config? Is it possible you have clover installed twice, like, installed to EFI partition and to root partition? Where did you copy that config.plist from?
 
More or less the same issue here too.
 
Status
Not open for further replies.
Back
Top