MultiBeast Failure

hello guys, I need your support please

macOS version
13.1.05
2nd try with
13.2.07

File system type for destination
APFS

the contents of ~/Library/Logs/MultiBeast.log
11/19/17 20:40:26 -


and the contents of /var/log/install.log
see attached file: install.txt

MultiBeast.log shows the program started but did nothing with a date almost 2 months in the past.

Install.log your only shows macOS installation and nothing else.

the installation works fine, in Finder i can see the new drive
but if i want install drivers from multibeast no such disk is shown, also when i start to install clover


i try new installation with version 13.2.07 , no change

this is what Disk Utility shows:

Why are you installing with the Clover installer when MultiBeast includes Clover?

Post a screen capture of the MultiBeast Build screen to show what options you are trying to install.

at first, thank you that you take care of the matter!

i think i don´t explain it right, that you can´t imagine, what my problem is

when i boot my hackintosh, i don´t see the new drive with the high sierra installation,
the booting from my old drive with sierra installation works fine

when i then start to install multibeast i get this message, equal wich settings, for example only the bootloader:


also i try to start a (test-) installation of clover it only shows the other drives

it seems, that my system has not access to the high sierra drive
(the drive "Install m..gh Sierra" is the Installation-Disk, not the recommended "High Sierra"-Drive
look at my screenshot above from the Disk Utility and you can see my 3 Drives

Need install.log from the screen shots as it will show why the Clover install failed.

Hi All,
My observation :
-When I tried installing drivers using Multibeast it failed.
-I restarted PC and tried again and failed.
-Now, 3rd time selected and used UEFI boot Mode with drivers and it succeeded. Installation complete.
Then I tried this for few other things at least 3-4 times, Installing with and without UEFI mode. Just to verify.

It failed most of the times without UEFI Boot mode
BUT
Succeeded every time I installed with UEFI boot mode.

NOTE: I was doing it after a clean install 10.13.1. To start my audio and graphics.

Don't know why, but it worked that way. (May be techies can check WHY ?)
Hope this works for you.