Contribute
Register

Multibeast failure/error at FakeSMC

Status
Not open for further replies.
Joined
Oct 20, 2018
Messages
81
Motherboard
ASUS Maximus IX Code
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
  1. macOS version
MacOS High Sierra version 10.13.6
  1. MultiBeast version
Multibeast version High Sierra Edition 10.4.0
  1. MultiBeast choices
MultiBeast
Quick Start > UEFI Boot Mode
Drivers > Network > Intel > IntelMausiEthernet v2.4.0
Customize >Graphics > Intel HD 6xx

Build - shows your selections, and adds 3 more.
  1. Destination files system type, HFS+ or APFS
Destination Samsung NVME APFS
  1. MultiBeast.log contents

  1. install.log contents for the choices that you are installing

Log contents are found in the Console application

~/Library/Logs/MultiBeast.log
11/14/18 22:40:50 - Starting MultiBeast 10.4.0-20180812
11/14/18 22:43:04 - Installing 'Bootloaders > Clover UEFI Boot Mode'
11/14/18 22:43:08 - Installing 'BootVolume'
11/14/18 22:43:08 - Mounting EFI at destination 'SamsungNVME'
11/14/18 22:43:08 - Installing 'Drivers > Misc > FakeSMC'
11/14/18 22:43:10 - Install of '/Applications/MultiBeast.app/Contents/Resources/FakeSMC-v6.26-344-g1cf53906.1787.pkg' failed.
'installer: Package name is FakeSMC-v6.26-344-g1cf53906.1787
installer: Installing at base path /
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
'. Exiting.
11/14/18 23:07:00 - Installing 'Bootloaders > Clover UEFI Boot Mode'
11/14/18 23:07:05 - Installing 'BootVolume'
11/14/18 23:07:05 - Mounting EFI at destination 'SamsungNVME'
11/14/18 23:07:05 - Installing 'Drivers > Misc > FakeSMC'
11/14/18 23:07:07 - Install of '/Applications/MultiBeast.app/Contents/Resources/FakeSMC-v6.26-344-g1cf53906.1787.pkg' failed.
'installer: Package name is FakeSMC-v6.26-344-g1cf53906.1787
installer: Installing at base path /
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
'. Exiting.
11/14/18 23:10:12 - Installing 'Bootloaders > Clover UEFI Boot Mode + Emulated NVRAM'
11/14/18 23:10:17 - Installing 'BootVolume'
11/14/18 23:10:17 - Mounting EFI at destination 'SamsungNVME'
11/14/18 23:10:17 - Installing 'Drivers > Misc > FakeSMC'
11/14/18 23:10:19 - Install of '/Applications/MultiBeast.app/Contents/Resources/FakeSMC-v6.26-344-g1cf53906.1787.pkg' failed.
'installer: Package name is FakeSMC-v6.26-344-g1cf53906.1787
installer: Installing at base path /
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
'. Exiting.
11/14/18 23:13:51 - Starting MultiBeast 9.2.1-20180221
11/14/18 23:14:24 - Installing 'Bootloaders > Clover v2.4k r4173 UEFI Boot Mode'
11/14/18 23:15:15 - Installing 'BootVolume'
11/14/18 23:15:15 - Mounting EFI
11/14/18 23:15:15 - Installing 'Drivers > Misc > FakeSMC v6.25-333-g05e0f4be.1759'
11/14/18 23:15:18 - Installing 'Drivers > Network > Intel > IntelMausiEthernet v2.3.0'
11/14/18 23:15:20 - Installing 'Drivers > Graphics > Intel HD 6xx'
11/14/18 23:15:22 - Install of '/private/var/folders/jz/rcjm8r1n2jq3b1kjc8z18h4r0000gn/T/AppTranslocation/A976CBEF-7A01-4CFF-8C86-F75387FE3BF5/d/MultiBeast.app/Contents/Resources/Clover-HD6xx-Graphics.pkg' failed.
'installer: Package name is Clover-HD6xx-Graphics
installer: Installing at base path /Volumes/Install macOS High Sierra
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
'. Exiting.
11/14/18 23:16:26 - Starting MultiBeast 9.2.1-20180221
11/14/18 23:16:46 - Starting MultiBeast 10.4.0-20180812
11/14/18 23:17:13 - Installing 'Bootloaders > Clover UEFI Boot Mode'
11/14/18 23:17:18 - Installing 'BootVolume'
11/14/18 23:17:18 - Mounting EFI at destination 'SamsungNVME'
11/14/18 23:17:18 - Installing 'Drivers > Misc > FakeSMC'
11/14/18 23:17:19 - Install of '/Applications/MultiBeast.app/Contents/Resources/FakeSMC-v6.26-344-g1cf53906.1787.pkg' failed.
'installer: Package name is FakeSMC-v6.26-344-g1cf53906.1787
installer: Installing at base path /
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
'. Exiting.


/var/log/install.log

UPLOADED FILE; Readme.txt
 

Attachments

  • readme.txt
    1.3 MB · Views: 283

MacMan

Administrator
Staff member
Joined
Feb 2, 2010
Messages
8,462
Motherboard
ASUS TUF Z390-PRO GAMING - 2606 - UEFI
CPU
i9-9900K
Graphics
Vega 64
Mac
  1. MacBook Pro
  2. Mac Pro
Classic Mac
  1. Power Mac
  2. PowerBook
Mobile Phone
  1. iOS
Joined
Jul 24, 2018
Messages
186
Motherboard
GigaByte-Z370N-WIFI
CPU
i5-8400
Graphics
HD 630 / GTX 1060
Mac
  1. iMac
  2. MacBook
  3. MacBook Pro
  4. Mac mini
Mobile Phone
  1. iOS
> Installed failed as it couldn't find the Clover EFI folder.

@Danoldo,
It sounds like MultiBeast can not copy the files it needs from the UniBeast USB drive.
Did you unplug the UniBeast USB drive before running MultiBeast?
 
Joined
Oct 20, 2018
Messages
81
Motherboard
ASUS Maximus IX Code
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
> Installed failed as it couldn't find the Clover EFI folder.

@Danoldo,
It sounds like MultiBeast can not copy the files it needs from the UniBeast USB drive.
Did you unplug the UniBeast USB drive before running MultiBeast?
no, been here since i started the process.
 

Attachments

  • IMG_0118.jpg
    IMG_0118.jpg
    745.3 KB · Views: 187
Joined
Oct 20, 2018
Messages
81
Motherboard
ASUS Maximus IX Code
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
My question is, once the Mac OS High Sierra desktop pops up...the only thing I did was get EFI mounter V3, mounted the EFI on the USB disk, then I went into the Install macOS High Sierra partition(USB) and dragged Multibeast over, unzipped it, and put Multibeast into the applications folder, and then I ran it.

From there, I ran multibeast with your options you say to select...then when I clicked install, I got a failure at FakeSMC.

I have now since rebooted the machine, I have mounted the EFI partition(USB drive) and then I have multibeast open(same one)....should I attempt to re-run the process? I am wanting to know if I need to create or drag any files from the USB EFI Folder to the BootDrive.
 
Joined
Jul 24, 2018
Messages
186
Motherboard
GigaByte-Z370N-WIFI
CPU
i5-8400
Graphics
HD 630 / GTX 1060
Mac
  1. iMac
  2. MacBook
  3. MacBook Pro
  4. Mac mini
Mobile Phone
  1. iOS
After the macOS install, my local EFI partition had /EFI/Apple,
but no /EFI/Clover or /EFI/Boot.
Those two folders did not exist until I ran MultiBeast.
-----------
On a separate note,
I could not reliably boot from the 6 rear USB ports until I got the USB fix installed.
Try booting from the front USB ports instead.
-----------
If you wanted to do the deed manually, you could try this:

mount the USB's EFI partition
mount the NVME's EFI partition

make a safe backup copy of the NVMe's EFI folder, in case we mess up.

copy USB/EFI/EFI/Clover to NVMe/EFI/EFI/Clover
copy USB/EFI/EFI/Boot to NVMe/EFI/EFI/Boot
 
Joined
Oct 20, 2018
Messages
81
Motherboard
ASUS Maximus IX Code
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
After the macOS install, my local EFI partition had /EFI/Apple,
but no /EFI/Clover or /EFI/Boot.
Those two folders did not exist until I ran MultiBeast.
-----------
On a separate note,
I could not reliably boot from the 6 rear USB ports until I got the USB fix installed.
Try booting from the front USB ports instead.
-----------
If you wanted to do the deed manually, you could try this:

mount the USB's EFI partition
mount the NVME's EFI partition

make a safe backup copy of the NVMe's EFI folder, in case we mess up.

copy USB/EFI/EFI/Clover to NVMe/EFI/EFI/Clover
copy USB/EFI/EFI/Boot to NVMe/EFI/EFI/Boot
I’m about to fall in love with you if this works. Which will be both strange and a paradox because I’m just not clovered that way. However, if this computer was for me and not someone else, I’d be getting less frustrated. I plan on doing this to my computer once this is complete because I do find this fun, but not when it’s a gift and the time is ticking.

Let me try this first.

1) I’m first going to swap the usb to front and then the change the boot option in bios to nvme drive.

2) I’ll try this after if it doesn’t work .
 
Joined
Apr 8, 2020
Messages
15
Motherboard
Asus TUF z390 Pro Gaming
CPU
i9-9900K
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
I just encountered this problem, and it was due to running EFI Mounter v3.1 to mount disk0s1 as /Volumes/EFI in order to execute /usr/libexec/PlistBuddy -c "Merge ASUS_ACPI :ACPI:DSDT:" /Volumes/EFI/EFI/CLOVER/config.plist

As mentioned above, rebooting probably would solve it because it would unmount that. To do it without the invasive-reboot, simply run EFI Mounter again, select (in my case) disk0s1, and unmount it.

After I did that, Multibeast installed/ran successfully.

Bonus data:
- When my Multibeast was failing, there was an EFI icon on my desktop; after unmounting, it disappeared (obviously)
- A person could probably open Finder and eject the EFI volume via that Eject button (I didn't test this but it might be faster than running EFI Mounter again)
 
Status
Not open for further replies.
Top