- Joined
- Dec 25, 2011
- Messages
- 13
- Motherboard
- Asus Z170 Pro Gaming
- CPU
- i7 6700K
- Graphics
- GTX 1070, HD 6870, HD530
- Mac
- Mobile Phone
Hi, I encountered a bug as stated in the title. Thought I'd report it.
Situation was like this: I took my ssd from my hackintosh out and connected it to macbook via external enclosure, to make a backup, together with backup hdd. I used osx Disk Utility to restore my partition name OSX to a backup hdd, it created partition OSX there. To check if it was ok I tried to install clover using multibeast on the backup hdd, since efi partition wasn't copied. I disconnected original ssd, ran multibeast and then figured a problem in naming. I name my osx drives just "OSX" so now I had two of them (mbp and backup hdd) and multibeast showed only one as option. So I renamed backup one as OSX_BACKUP, I renamed right one since it had orange icon as external drive. I relaunched Multibeast and now I could see OSX_BACKUP in the list of destinations. I installed clover there, but after failed boot attempt discovered that clover was installed on my macbooks hdd instead.
From my understanding of EFI partitions I assumed it's safe to just remove whats in it and copy content of /EFI_BACKUP that multibeast made in the root of mbp drive.
I havent restarted my mbp yet, but i've made installer usb for sierra just in case.
To mention I did use multibeast once more to create bootable usb stick with clover, I formatted usb stick using Disk Utility (guid, hfs+) and it installed fine there.
Maybe same name for drives was a confusing factor and renaming it through Info window in osx was not enough for Multibeast code to make a difference. But it did show it to me as a separate option for installation.
Situation was like this: I took my ssd from my hackintosh out and connected it to macbook via external enclosure, to make a backup, together with backup hdd. I used osx Disk Utility to restore my partition name OSX to a backup hdd, it created partition OSX there. To check if it was ok I tried to install clover using multibeast on the backup hdd, since efi partition wasn't copied. I disconnected original ssd, ran multibeast and then figured a problem in naming. I name my osx drives just "OSX" so now I had two of them (mbp and backup hdd) and multibeast showed only one as option. So I renamed backup one as OSX_BACKUP, I renamed right one since it had orange icon as external drive. I relaunched Multibeast and now I could see OSX_BACKUP in the list of destinations. I installed clover there, but after failed boot attempt discovered that clover was installed on my macbooks hdd instead.
From my understanding of EFI partitions I assumed it's safe to just remove whats in it and copy content of /EFI_BACKUP that multibeast made in the root of mbp drive.
I havent restarted my mbp yet, but i've made installer usb for sierra just in case.
To mention I did use multibeast once more to create bootable usb stick with clover, I formatted usb stick using Disk Utility (guid, hfs+) and it installed fine there.
Maybe same name for drives was a confusing factor and renaming it through Info window in osx was not enough for Multibeast code to make a difference. But it did show it to me as a separate option for installation.