MultiBeast High Sierra not writing to EFI Partition

[world-of-pies]

ok - went throught the buid process again, with a kingston ssd.
its not the ssd - must be something wrong with the way multibeast was written

 

[P1LGRIM]

must be something wrong with the way multibeast was written

MultiBeast Failure Reporting v10 and later

NOTE: MultiBeast cannot mount the EFI partition when booted in Safe Mode. Any MultiBeast option that needs access to /EFI or Clover config.plist will fail. When reporting a failed install with MultiBeast 10 or later you need to create a new topic in...

www.tonymacx86.com

 

[world-of-pies]

ah thanks P1LGRIM, glad you're well
i'll put something together - i've never had so much grief with a basic build.

 

[P1LGRIM]

i've never had so much grief with a basic build

You seem to have experienced similar difficulty back in 2019 :

Mobo doesn't recognise Clover UEFI (High Sierra)

Hi, I have an Intel DQ77MK Mobo which is working well with OSX 10.8.5 (for legacy apps), OSX10.10 Yosemite and a slightly buggy OSX10.12 Sierra. Now I've just built a couple of High Sierra Installs - one on an SSD in HFS+ format, and a 2nd SSD in APFS format. These SSDs were blessed using...

www.tonymacx86.com

 

[world-of-pies]

yeah - its the same job re-visited. sierra builds well.
but HS and Mojave seem to hit a wall.
last week, i somehow managed to get a UEFI to work, but when i tried to repeat the process from scratch i get nothing
you'd think cloning the EFI part across would work, but nope.
not gonna tear my hair out because i've got none left

 

[world-of-pies]

ok so today, i went through the build onto
another kingston ssd - wouldn't boot via UEFI or legacy
a seagate hard drive - which installed as a HFS+ so Multibeast failed.
and finally a build onto a samsung evo 750, which again runs fine, just multibeast fails to install a working bootlaoder (either UEFI or Legacy).

is there a thread that explains exactly what multibeast is trying to do ?
there's hardly any detail in the logs...

Installing BootSectors/BootLoader

Stage 0 - Don't write any of boot0af, boot0md, boot0ss to /
Stage 1 - Don't write any of boot1h2, boot1f32alt, boot1xalt to /


Multibeast log is pretty sparse too.. (i live in 2018 to avoid the virus)

05/29/18 10:50:09 - Starting MultiBeast 10.4.0-20180812
05/29/18 10:50:20 - Installing 'Bootloaders > Clover UEFI Boot Mode'
05/29/18 10:50:25 - Installing 'BootVolume'
05/29/18 10:50:26 - Mounting EFI at destination 'Untitled'
05/29/18 10:50:26 - Installing 'Drivers > Audio > Realtek ALCxxx > ALC892'
05/29/18 10:50:58 - Installing 'Drivers > Disk > Intel Generic AHCI SATA'
05/29/18 10:51:30 - Installing 'Drivers > Misc > FakeSMC'
05/29/18 10:52:03 - Installing 'Drivers > Network > Intel > AppleIntelE1000e v3.3.6'
05/29/18 10:52:35 - Installing 'Drivers > USB > 7/8/9 Series USB Support'
05/29/18 10:53:08 - Installing 'Customize > System Definitions > iMac > iMac 14,2'
05/29/18 10:53:08 - Releasing XPC connection.
05/29/18 10:53:08 - Finished Installing.

 

[P1LGRIM]

is there a thread that explains exactly what multibeast is trying to do ?

If you follow the instructions in the Failure Reporting notes the developer will respond to you.
If you don't then the chances are that nobody will.

 

[world-of-pies]

yes, i'm just collecting the logs.
however, my question is still: "is there a thread that describes what multibeast is trying to do" as i couldn't find one.
thanks

 

[UtterDisbelief]

yes, i'm just collecting the logs.
however, my question is still: "is there a thread that describes what multibeast is trying to do" as i couldn't find one.
thanks

No there isn't.

When you ask MultiBeast to make a drive bootable it actually runs a Clover installer. The one inside the High Sierra MultiBeast is Clover v2.4k-r4630. What's more you can select one of three versions - Legacy, UEFI or UEFI+Emulated NVRAM.

That you have a "failure" could be down to your own disk format/partition or some other Clover conflict. With a problem like yours, do as @P1LGRIM says and report it to get feedback.

You can also run a Clover installer "externally" to MultiBeast and check if that works instead.

 

[jonarnp]

I think I was having a similar issue - couldn't boot without the USB stick. Using an older version of Multibeast seems to have fixed the problem for me. I used MultiBeast 10.3.0 - High Sierra

[edit] I remember getting it up and running without much hassle a few years ago, but struggled quite a lot this time.