Windows 8.1 update blew Clover EFI entry

[Hameer Abbasi]

Okay, so I ran a Windows 8.1 Pro update, and after that got a "Reboot and select proper boot device" error. I swapped the cables on my two HDDs, and that got me into Windows, but the Clover EFI entry has disappeared. I used a boot USB I made to get me into OS X, but installing Clover just fails, and mounting the EFI partition with Clover Configurator fails as well. Booting into my Ubuntu installation shows that the Clover partition is still FAT32, not NTFS.

 

Here is the installation log: http://pastebin.com/6dmYrFr9

Here is the output of diskutil list: http://pastebin.com/FKTu4yHE

 

I'm clueless about where to go from here. Suggestions?

[arsradu]

Okay, so I ran a Windows 8.1 Pro update, and after that got a "Reboot and select proper boot device" error. I swapped the cables on my two HDDs, and that got me into Windows, but the Clover EFI entry has disappeared. I used a boot USB I made to get me into OS X, but installing Clover just fails, and mounting the EFI partition with Clover Configurator fails as well. Booting into my Ubuntu installation shows that the Clover partition is still FAT32, not NTFS.

 

Here is the installation log: http://pastebin.com/6dmYrFr9

Here is the output of diskutil list: http://pastebin.com/FKTu4yHE

 

I'm clueless about where to go from here. Suggestions?

 

So you've got OS X (Yosemite, I assume) and Windows 8.1 on one HDD, and a simple NTFS partition on the other one, which is not bootable, for as far as I can see. It's just for storage.

 

Now, I would suggest putting back your cables the way they were. Not sure why you switched them in the first place, but anyway.

 

And what do you mean by Clover entry disappeared? How are you booting up? You can't boot into Clover anymore? Cause that usually means that the bootloader has been replaced/it can't be used anymore. And knowing Windows, it tends to do that sometimes. For example when you're installing Windows AFTER Ubuntu, you won't be able to boot into Ubuntu anymore. Cause the Windows bootloader won't let you. Easiest way to fix this is reinstalling GRUB, in Ubuntu's case, and Clover in this case. Windows doesn't play nicely with dual-booting. At all. It wants to be the one and only operating system on your computer. The best one you'll ever want. Which is stupid. But..yeah, Microsoft.

 

Try this:

1. put back your cables the way they were (if that worked for you previous to that update).

2. disconnect your storage HDD (dev/disk1 in your diskutil output).

3. boot into OS X and try to re-install Clover (from a USB installer, if you can't boot from the HDD anymore).

4. avoid using Windows, if you can.

 

I'm not sure what you meant by Clover partition is not NTFS. But I don't think it's supposed to be NTFS in the first place. Might be wrong though. If you meant the EFI partition, I'm pretty sure that's not supposed to be NTFS.

[Hameer Abbasi]

So you've got OS X (Yosemite, I assume) and Windows 8.1 on one HDD, and a simple NTFS partition on the other one, which is not bootable, for as far as I can see. It's just for storage.

 

Now, I would suggest putting back your cables the way they were. Not sure why you switched them in the first place, but anyway.

 

And what do you mean by Clover entry disappeared? How are you booting up? You can't boot into Clover anymore? Cause that usually means that the bootloader has been replaced/it can't be used anymore. And knowing Windows, it tends to do that sometimes. For example when you're installing Windows AFTER Ubuntu, you won't be able to boot into Ubuntu anymore. Cause the Windows bootloader won't let you. Easiest way to fix this is reinstalling GRUB, in Ubuntu's case, and Clover in this case. Windows doesn't play nicely with dual-booting. At all. It wants to be the one and only operating system on your computer. The best one you'll ever want. Which is stupid. But..yeah, Microsoft.

 

Try this:

1. put back your cables the way they were (if that worked for you previous to that update).

2. disconnect your storage HDD (dev/disk1 in your diskutil output).

3. boot into OS X and try to re-install Clover (from a USB installer, if you can't boot from the HDD anymore).

4. avoid using Windows, if you can.

 

I'm not sure what you meant by Clover partition is not NTFS. But I don't think it's supposed to be NTFS in the first place. Might be wrong though. If you meant the EFI partition, I'm pretty sure that's not supposed to be NTFS.

I did all the steps. reversed the cables, then disconnected the extra HDD, then tried to reinstall Clover, still fails.    Thanks for attempting to help, though.

[arsradu]

I did all the steps. reversed the cables, then disconnected the extra HDD, then tried to reinstall Clover, still fails.    Thanks for attempting to help, though.

 

I'm pretty sure the installer fails cause it can't mount the EFI partition. So question is why.

 

What does it happen when you try to mount the EFI partition manually? I had this kind of issues (not being able to mount the EFI partition) when booting in Safe Mode. And that's intended. But I suppose you're not booting in safe mode, are you?

 

Can you try to run the following commands, in terminal, and post here the output?

 

Since your EFI partition is located on disk0s1 (still,  you should run another diskutil list to make sure that's still the case), this is what we're gonna use. So open up a terminal window and do this:

mkdir /Volumes/efi

sudo mount -t msdos /dev/disk0s1 /Volumes/efi

Normally this would mount your EFI partition. But since Clover Configurator doesn't do it, I'm expecting to see some sort of error here. So please, post that error here. Might help.

[Hameer Abbasi]

I'm pretty sure the installer fails cause it can't mount the EFI partition. So question is why.

 

What does it happen when you try to mount the EFI partition manually? I had this kind of issues (not being able to mount the EFI partition) when booting in Safe Mode. And that's intended. But I suppose you're not booting in safe mode, are you?

 

Can you try to run the following commands, in terminal, and post here the output?

 

Since your EFI partition is located on disk0s1 (still,  you should run another diskutil list to make sure that's still the case), this is what we're gonna use. So open up a terminal window and do this:

mkdir /Volumes/efi

sudo mount -t msdos /dev/disk0s1 /Volumes/efi

Normally this would mount your EFI partition. But since Clover Configurator doesn't do it, I'm expecting to see some sort of error here. So please, post that error here. Might help.

Ermmm. My installer USB only boots the OS X in safe mode. I've been using safe mode all along.

 

So, question is, how do I get into OS X to boot without safe mode, so I can install Clover?

 

Without safe mode, it stops at stops at Missing Bluetooth Controller Transport. Tried nv_disable=1. Anything else I can try? (Relevant specs are in my signature).

[arsradu]

Ermmm. My installer USB only boots the OS X in safe mode. I've been using safe mode all along.

 

So, question is, how do I get into OS X to boot without safe mode, so I can install Clover?

 

Without safe mode, it stops at stops at Missing Bluetooth Controller Transport. Tried nv_disable=1. Anything else I can try? (Relevant specs are in my signature).

 

Do you have all the relevant kexts in EFI/Clover/kexts/10.10 (on the USB installer)? Especially FakeSMC.kext. And also, just to confirm, you're trying to boot Yosemite, right?

 

Also, your config (or you can specify on every boot) need to use the following boot flag, for Yosemite: kext-dev-mode=1. So either you're adding it into your config.plist, or you specify it when you boot up. This will allow your unsigned kexts (again, especially FakeSMC.kext) to load and thus, you will be able to boot into the OS (assuming everything else is in place).

 

Looks like a problem with either the config.plist (you can upload it here if you want) or the kexts you're using (or the place they're in, if it's not the correct one).

[Hameer Abbasi]

Do you have all the relevant kexts in EFI/Clover/kexts/10.10 (on the USB installer)? Especially FakeSMC.kext. And also, just to confirm, you're trying to boot Yosemite, right?

 

Looks like a problem with either the config.plist (you can upload it here if you want) or the kexts you're using (or the place they're in, if it's not the correct one).

My boot USB is Chameleon-based, not Clover-based. I won't use the name here, since many people hate it, but you know the one I mean.

[arsradu]

My boot USB is Chameleon-based, not Clover-based. I won't use the name here, since many people hate it, but you know the one I mean.

Then I'm sorry... I don't use Chameleon. I don't know why YOU use it. ) But unfortunately my experience with Chameleon over the years has been painfully frustrating. So I can't recommend it to anyone. Also I don't know what could be the problem for your unbootable system in this case (I'm asuming the same as for Clover), but I don't know how to fix it.

I do however know how to help you create a Clover bootable USB and never switch to Chameleon again, if you want.

And...there is a reason why people hate it. )

Also, I think nv_disable=1 needs to be used with Clover, not Chameleon. I might be wrong though.

[Hameer Abbasi]

Then I'm sorry... I don't use Chameleon. I don't know why YOU use it. ) But unfortunately my experience with Chameleon over the years has been painfully frustrating. So I can't recommend it to anyone. Also I don't know what could be the problem for your unbootable system in this case (I'm asuming the same as for Clover), but I don't know how to fix it.

I do however know how to help you create a Clover bootable USB and never switch to Chameleon again, if you want.

And...there is a reason why people hate it. )

Also, I think nv_disable=1 needs to be used with Clover, not Chameleon. I might be wrong though.

Of couse I'd be willing. I've wanted to switch my USB to Clover for ages. Please keep in mind that I can only use OS X in safe mode, but I can access my EFI partition in Ubuntu.

[Hameer Abbasi]

UPDATE: I fixed it. I booted into OS X with dart=0. Then installed Clover. But my motherboard still didn't want to cooperate.

 

So I booted into Windows and used EasyUEFI to add a boot entry for Clover. Problem solved.

[arsradu]

UPDATE: I fixed it. I booted into OS X with dart=0. Then installed Clover. But my motherboard still didn't want to cooperate.

 

So I booted into Windows and used EasyUEFI to add a boot entry for Clover. Problem solved.

Not sure what does that dart=0 do... But I'm glad you did it!

 

Well, if you still want to make a USB installer with Clover, since you're already using it on your PC (that confused me into thinking you also have a USB booted by Clover), just let me know.