- Joined
- Dec 6, 2015
- Messages
- 10
- Motherboard
- asrock h97m pro4
- CPU
- i5-4690
- Graphics
- evga gt 740 sc ss
- Mac
- Mobile Phone
So I purchased a new disk and wanted to migrate to it. First thing, I cloned the existing disk onto the new one, it created a recovery HD, etc. Reboot, and Clover (off the existing disk) recognized the new install, great, it boots fine and no problems on that front.
The problem is that I can't get a working Clover install on the new disk to boot. I copied the EFI partition contents to the new EFI partition, the UEFI BIOS tries to boot it but fails (blinking underline). I tried Multibeast to install a new version of Clover onto the new disk, it was successful according to the logs (the only thing updated in the Clover.plist was the serial number which I replaced after). Still the same result. Basically nothing after the BIOS screen. If I go into the F11 boot menu, selecting Clover goes back to the boot menu as if it failed (a la any of the other invalid entries). Booting the disk directly in the boot menu has never worked.
Any thoughts? Am I missing something silly here? Thanks!
The problem is that I can't get a working Clover install on the new disk to boot. I copied the EFI partition contents to the new EFI partition, the UEFI BIOS tries to boot it but fails (blinking underline). I tried Multibeast to install a new version of Clover onto the new disk, it was successful according to the logs (the only thing updated in the Clover.plist was the serial number which I replaced after). Still the same result. Basically nothing after the BIOS screen. If I go into the F11 boot menu, selecting Clover goes back to the boot menu as if it failed (a la any of the other invalid entries). Booting the disk directly in the boot menu has never worked.
Any thoughts? Am I missing something silly here? Thanks!