Contribute
Register

Stork's MyHero Build: ASUS ROG Z170 MAXIMUS VIII HERO - i7-6700K - GTX 980

Status
Not open for further replies.
View attachment 204675
That is the error I am getting. I have tried the osxaptiofix also

Even booting from the unibeast install drive with it in the pc all by itself.

So you can't even boot to the UniBeast stick then?

That's surprising, if created as per the guide.

Judging by the errors, it's probably disk access. Unable to page RAM memory to disk or similar.

Still think there's a disk format problem somewhere .... That's what the circle with slash is saying - unable to boot this disk.
 
So you can't even boot to the UniBeast stick then?

That's surprising, if created as per the guide.

Judging by the errors, it's probably disk access. Unable to page RAM memory to disk or similar.

Still think there's a disk format problem somewhere .... That's what the circle with slash is saying - unable to boot this disk.

Actually what fixed me was OsxAptioFix2Drv-free2000.efi. Im up and running like a beast. FCPX screams on this machine.
 
Actually what fixed me was OsxAptioFix2Drv-free2000.efi. Im up and running like a beast. FCPX screams on this machine.
How did you discover that you needed that efi? ...and what does it do? I'll have to check MyHero's EFI/EFI/CLOVER/ folders to see if I'm using it.
 
How did you discover that you needed that efi? ...and what does it do? I'll have to check MyHero's EFI/EFI/CLOVER/ folders to see if I'm using it.
Lots of reading and just trying different things. Found this http://www.tonymacx86.com/threads/b...ed-sign-couldnt-allocate-runtime-area.194452/ and actually worked. I now only get the error maybe once in every 10-15 boots. I can live with that. I also think it might be something with the extreme board that maybe yours or others don't have. IDK I haven't dug into it deep enough to find out. I am just glad it is working.
 
I meant to also ask you Stork does yours always boot with any hiccups? I mean does yours every give you a bad boot and if so is this common. I only ask to know to worry or not.
 
Last edited:
So is this error saying OS X isn't able to access the emulated EFI ? So still a disk-related problem ;) (I know, I should give up!)

That is what I understand the *.efi files enable. I've seen posts elsewhere pointing to the third version you use and others say they get periodic boot fails too @boogieman77 . Trouble is that worries me. Something more serious going on.

If created the standard way then Clover's inbuilt should work. For my penny-worth I'd recheck *everything* because you seem a pro-user and don't want to lose data!
 
So is this error saying OS X isn't able to access the emulated EFI ? So still a disk-related problem ;) (I know, I should give up!)

That is what I understand the *.efi files enable. I've seen posts elsewhere pointing to the third version you use and others say they get periodic boot fails too @boogieman77 . Trouble is that worries me. Something more serious going on.

If created the standard way then Clover's inbuilt should work. For my penny-worth I'd recheck *everything* because you seem a pro-user and don't want to lose data!
I have checked and checked. I still get the startup error maybe once in 10-15 boots as I said. I tried the unibeast install several times with a diff drive than my Samsung 850 Evo. I honestly dont know what else to do I had thought that had fixed my issue until I saw your reply about data.
 
I have checked and checked. I still get the startup error maybe once in 10-15 boots as I said. I tried the unibeast install several times with a diff drive than my Samsung 850 Evo. I honestly dont know what else to do I had thought that had fixed my issue until I saw your reply about data.

If you have problems yet, left unibeast method and try different one.
 
Status
Not open for further replies.
Back
Top