Jump to content

Partition Map Error in Yosemite


WeiSer
 Share

21 posts in this topic

Recommended Posts

Hi.

 

I have a problem in yosemite..

 

PC SPEC

 

CPU : i5 4460

 

Mainboard : ASUS H97 Pro (smbios : imac 5k)

 

VGA : HD 7770

 

 

 

After successful installation (via clover uefi), I checked partition map of HDD in disk utility... and Disk Utility shows me that partition map error.

 

So.. I repaired (disk utility shows partition map fixed). and after reboot I checked again, and same error happens again...

 

I doubted about hdd or sata cable malfunction so tested with other hdd and cable but same result.. (beside, usb hdd and usb stick shows me same error)

 

I tested with different smbios, chameleon boot loader but same all.. even I installed yosemite into another pc (i3 3220, ASUS P8Z77-V, GT 630) and same result..

 

(No problem with Mavericks)

 

How can I fix this problem? Please Help~

 

 

* In short..

 

Disk Utility show me 'The Partition Map Needs to be repaired because there is a problem with the EFI system partition's file system' message.

 

After successful repair, and reboot, it happens again.

post-337344-0-58141500-1416498671_thumb.png

Link to comment
Share on other sites

Run kextstat in ternimal to see if AppleLPC.kext load or not.

Cause it is differnet, my system is not face it.

 

Loaded. At first boot, it wasn't loaded. so I made dsdt of my board and inserted '8c4b' (hm87). Now it's loaded..

 

Would you upload dsdt and config.plist of your h97 hackin, kvonlinee? (Please~)

post-337344-0-70101000-1416589052_thumb.jpg

Link to comment
Share on other sites

Which main board do you have?

 

Gigabyte Z97X-UD3H.

 

Here is my kextstat output (no AppleLPC):

$ kextstat | grep LPC
   46    0 0xffffff7f81956000 0x17000    0x17000    org.hwsensors.driver.LPCSensors (1328) <19 12 11 7 5 4 3>

And btw, I'm using Clover.

Link to comment
Share on other sites

On the dsdt I don't edit anything about LPC, i put in it to get HDMI audio.

Lpc thing I add more more string from dpci manager. And it load, work out to the old dell-xps-410 it show 2 more drive on the ata mode yosemite.

I will up load those thing for you, when i got home. About 10 hr more or something like that.

Link to comment
Share on other sites

What if you manually reformat the EFI partition of one of the drives? Just an idea. What does diskutil list tell you?

 

Maybe rolling back some kexts (not ideal) or taking a look at some of the source code could help.

Also, maybe converting it to a hybrid MBR like bootcamp does would stop the error.

 

Did you try repartitioning and formatting the drives on a different computer, maybe the hardware configuration is doing something weird when it's formatting them or something.

 

Those are all very dirty hacks, I know. But one of them could be a step in the right direction. 

 

Very strange issue.

Link to comment
Share on other sites

What if you manually reformat the EFI partition of one of the drives? Just an idea. What does diskutil list tell you?

 

Maybe rolling back some kexts (not ideal) or taking a look at some of the source code could help.

Also, maybe converting it to a hybrid MBR like bootcamp does would stop the error.

 

Did you try repartitioning and formatting the drives on a different computer, maybe the hardware configuration is doing something weird when it's formatting them or something.

 

Those are all very dirty hacks, I know. But one of them could be a step in the right direction. 

 

Very strange issue.

 

Thank you for your advice. BUT nothing changed by reformatting EFI partition. I think rolling back kexts or making hybrid MBR partition is not so good solution..

 

I want pure OS X!!!  :P lol..

 

 

This is what Disk Utility shows me.

 

 

Verifying partition map for “ST3160215SCE Media”

Checking prerequisites

Checking the partition list

Checking for an EFI system partition

Checking the EFI system partition’s size

Checking the EFI system partition’s file system

Problems were found with the partition map which might prevent booting

Error: The partition map needs to be repaired because there’s a problem with the EFI system partition’s file system.

 

Verifying and repairing partition map for “ST3160215SCE Media”

Checking prerequisites

Checking the partition list

Adjusting partition map to fit whole disk as required

Checking for an EFI system partition

Checking the EFI system partition’s size

Checking the EFI system partition’s file system

Repairing the EFI system partition’s file system

Repairing file system.

** /dev/rdisk0s1

** Phase 1 - Preparing FAT

** Phase 2 - Checking Directories

** Phase 3 - Checking for Orphan Clusters

Free space in FSInfo block (375138) not correct (375140)

Fix? yes

418 files, 187570 KiB free (375140 clusters)

File system check exit code is 0.

Updating boot support partitions for the volume as required.

Checking all HFS data partition loader spaces

Checking booter partitions

Checking booter partition disk0s3

Repairing file system.

Checking Journaled HFS Plus volume.

Checking extents overflow file.

Checking catalog file.

Checking multi-linked files.

Checking catalog hierarchy.

Checking extended attributes file.

Checking volume bitmap.

Checking volume information.

The volume Recovery HD appears to be OK.

File system check exit code is 0.

Updating boot support partitions for the volume as required.

Reviewing boot support loaders

Checking Core Storage Physical Volume partitions

Updating Windows boot.ini files as required

The partition map has been repaired

 

After repair, reboot, same error.. It says 'Free Space in FSInfo block not correct' (Always it shows 2 bytes difference) Do you know what does it mean? Maybe this can be the point.

 

 

Oh, and another symptom is.. No APPLE folder in EFI folder of EFI partition. You can see /EFI/APPLE/FIRMWARE folder in EFI partition.

 

Even if you manually format the EFI partition, you can see /EFI/APPLE/FIRMWARE folder after reboot several times. But I can't see it.

 

 

Attached my config.plist (serial removed) and dsdt. And I used fakesmc, appleintel1000e. I think this is a quite formal installation..  :(

 

Can't figure out what cause this problem;

Archive.zip

Link to comment
Share on other sites

Thank you for your advice. BUT nothing changed by reformatting EFI partition. I think rolling back kexts or making hybrid MBR partition is not so good solution..

 

I want pure OS X!!! :P lol..

 

 

This is what Disk Utility shows me.

 

 

After repair, reboot, same error.. It says 'Free Space in FSInfo block not correct' (Always it shows 2 bytes difference) Do you know what does it mean? Maybe this can be the point.

 

 

Oh, and another symptom is.. No APPLE folder in EFI folder of EFI partition. You can see /EFI/APPLE/FIRMWARE folder in EFI partition.

 

Even if you manually format the EFI partition, you can see /EFI/APPLE/FIRMWARE folder after reboot several times. But I can't see it.

 

 

Attached my config.plist (serial removed) and dsdt. And I used fakesmc, appleintel1000e. I think this is a quite formal installation.. :(

 

Can't figure out what cause this problem;

You don't need the apple/firmware folder, it serves no purpose on a hack. It's basically a temp folder for firmware updates on a real Mac.

 

I realize what I proposed is not a solution, those type of things are usually used as a last resort. But it could be a temporary workaround and maybe give some insight as to what the problem is.

 

I just had another thought. I could be remembering this wrong, I think disk utility has a debug mode you can enable with (iirc) something like Onyx or tinkertool. Maybe that could be useful.

 

I still think you should try creating the partition map from scratch on another computer. Just try it with a USB drive first. Maybe it just doesn't like being formatted on your PC for some odd reason.

 

I'll take a look at your config.plist soon.

 

Some other things such as boot.log, ioreg, and console log might be useful as well.

Have you used kext utility recently? Older versions used to patch msdosfs.kext which could potentially cause problems (I know it's now disabled for 10.10 and up).

Link to comment
Share on other sites

I think it's bug in Disk Utility. If you mount EFI partition before check disk everything is okay - EFI unmounted = error.

 

Oh I didn't noticed that!

I've just tested, and I can confirm this behavior.

It's certainly a bug from Disk Utility introduced in Yosemite, as I don't remember having this issue in Mavericks.

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...