Jump to content

Please help, after updating to Yosemite can't mount EFI


10 posts in this topic

Recommended Posts

Shortly after updating to Yosemite I realized I can't mount any EFI partitions. I even tried reformatting a USB with GPT to experiment and I can't get that EFI partition to mount either. In diskutility it says that the mounting has failed and to use First Aid, but that doesn't help. Nor does repairing permissions. It's only the EFI partitions on the drives, I am able to mount other partitions.

 

The console reports two entries: mount "blocked by dissenter PID=0 (unknown) status=0x0000c047 log=unknown message=(null)" and "diskarbitrationd[39]: unable to mount /dev/diskXsX (status code 0x00000047)."

 

I'm using the most recent clover bootloader on a GA-Q77M-D2H motherboard. I've not had any problems like this before. Mavericks worked great. I can't get in to the EFI partition to see what's going on with clover. Any help would be really appreciated. I'm pretty stumped here and a tad nervous because if anything does wrong I can't fix anything because I'm totally locked out of any EFI partition.

 
Link to comment
Share on other sites

Thanks, but that didn't work. It's very strange. I can't even use a newly formatted usb and access that efi.

 

 

use this tool to mount your EFI partitions.

 

http://www.hackintoshosx.com/files/file/49-clover-configurator/

 

it has a button on the bottom right to allow easy mounting and works flawlessly in Yosemite.

 

HBP

Link to comment
Share on other sites

open terminal 

defaults write com.apple.DiskUtility DUDebugMenuEnabled 1

then launch disk utility and make all partition display in the new debug menu

then you probably see your EFI partition became some “disk0s1“

repair it you and will see EFI again but no more clover directory 

so try to reinstall it ? but it's necessary to do a backup

Link to comment
Share on other sites

Thanks everybody, I couldn't figure it out so I ended up just doing a full reinstall (first with chimera, then back to clover). Mounting the EFI partition worked fine for a little while. But argh, it did it again. I did run kext utility, maybe that's the issue. How do I restore the original version of msdosfs.kext?

 

Do you run “Kext Utility” to rebuild the kext cache? It also modifies msdosfs.kext, the responsible for mounting FAT32 partitions making it fail the new integrity check. The solution would be to restore the original kext.

Link to comment
Share on other sites

 Share

×
×
  • Create New...