Can't Mount the EFI Partition Anymore

So I've been trying to figure out why my Hackintosh wouldn't load into the Chimera bootloader without the USB plugigng in. Since my mobo is the Asus Z97-A, I believed that the 9 series motherboards might also be affected by the Asus bug, where you need to install the bootloader and /Extra to the EFI partition. So I followed this guide http://www.tonymacx86.com/401-install-bootloader-extra-efi-partition.html , and although this didn't solve my problem, it still worked and I could mount the EFI partition using terminal if i ever needed to edit anything. So my next thought was the boot0:error (Guide here: http://www.tonymacx86.com/25-boot0-error-official-guide.html), as my hard drive is 1TB, however it didn't seem to have the hanging thing, as my computer would just boot straight into Windows. I gave it a go anyways, and it actually fixed the boot issue! But now I can't mount the EFI partition using Terminal (it just says mount_hfs: argument invalid) or the EFI Mounter tool. So my question is if there is another way to mount the EFI partition or if there is a way to reverse installing the bootloader and /Extra to EFI, or if I missed something in either of those guides. Thank you for your help!

Ok so the EFI Mounter tool opens up a file called EFI but there's nothing in it and it's a file, not a partition. Does anyone have a suggestion on this? It would be greatly appreciated.

Could you post a screenshot or two? What does DiskUtil show? What is the disk id (disk1s2 etc?)
How is your HD partitioned? stuff like that.

Also, what was the command that you typed when you got the "argument invalid" error?

First, thanks for your response! The first screenshot shows diskutil list, where you can see the first drive is my Windows SSD, and the second drive is my Mavericks hard drive, where 120GB is for the OS, and the other 880GB is for storage for Windows, as I mainly use and game with Windows. So the efi partition is identified as disk1s1, which you can see I correctly adjusted for in the second screenshot, where I attempted to mount the EFI parition using the instructions from the guide I mentioned before. If you need anything else just ask.

based on your first screenshot you mount your EFI partition with the command

diskutil mount disk1s1

the mkdir command is for making directories, not mounting them.

Hello,

I've exactly the same problem. At first the coding in terminal worked all of a sudden stop working with an error; "Invalid argument".

Now when I try to do it with EFI mounter it shows up as an empty folder.

Have you found any solution to this?

Yeah, I know it's been awhile, but I still haven't figure out the solution to this problem. If I try to mount simply by using "diskutil mount disk1s1", and it says "Volume on disk1s1 failed to mount". I'm really at a loss here, has anyone else had this problem before? And I don't know if this affected anything, but I believe I repaired permissions and rebooted, and then this problem arose.

As always, thanks for any help!

YoureInMySpot said:

Yeah, I know it's been awhile, but I still haven't figure out the solution to this problem. If I try to mount simply by using "diskutil mount disk1s1", and it says "Volume on disk1s1 failed to mount". I'm really at a loss here, has anyone else had this problem before? And I don't know if this affected anything, but I believe I repaired permissions and rebooted, and then this problem arose.

As always, thanks for any help!

Click to expand...

You ever figure this out? Im running an asus z97 gryphon matx, 4790k, build. I was following this thread here:http://www.tonymacx86.com/general-h...ithout-uni-multibeast-usb-heres-solution.html

Anyways I ran into same problem ..EFI was mounting system crashed on reboot never could get it to mount again just saying invalid argument...Fortunately my main objective was to be able to boot into Yosemite w/o the unibeast usb. I just was wanting to put Fakesmc into the extensions folder on the EFI so it would be easier to do reinstalls in the future on this board. My instincts tell me it has something to do with a bios setting since there both asus boards...i did not see where to disable cfg was an option to support the guid tables on boot hence i had to mess with EFI...aghhh.