Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Verify Disk Fails on 11" Mid-2011 MBA

Hi,

When using Disk Utility to Verify Disk, I get the following error:

Unable to bootstrap transaction group 1877: invalid field value

No valid commit checkpoint found

The volume 5E475AC6-27BF-4533-89F3-A1E555405EDA was found corrupt and needs to be repaired.

Problems were found with the partition map which might prevent booting

Error: Storage system verify or repair failed.

I tried searching, but didn't seem to be able to find anything related. Anybody have any ideas?

Thanks!

Mac OS X (10.7)

Posted on Aug 7, 2011 11:07 PM

Best reply

Kappy

Level 10

361,741 points

Posted on Aug 7, 2011 11:11 PM

Have you tried repairing the drive rather than verifying it? Verification will not fix anything. Only repairing will.

Repair the Hard Drive and Permissions - Lion

Boot from your Lion Recovery HD. When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.

To boot from the Recovery HD restart the computer. After the chime hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.

View in context

27 replies

dimfen

Level 1

0 points

Sep 29, 2011 7:50 AM in response to TheGerman2004

I have the same problem

iMac 2011 21.5' 2.5ghz (1 month old) - Lion with encrypted HD Filevault 2

I thing there is a problem with Filevault 2 or with Diskultility that check HD

Sep 29, 2011 8:27 AM in response to dimfen

Try to decrypt and then re-encrypt

dimfen

Level 1

0 points

Sep 29, 2011 9:39 AM in response to TheGerman2004

I don't need because problem disappears after closing all apps (safari in homepage!!) and restart then for the time when it stays on every test is ok but sometimes when the system closed or hibernate when disk make errors.

Maybe some apps like safari it re-open last visited sites or the disk mount that Filevault 2 use create this problem.

Sep 29, 2011 9:54 AM in response to dimfen

It sounds like a bug as you said. However, when the disk is decrypet, disk utility doesn't find problems

dimfen

Level 1

0 points

Sep 29, 2011 10:05 AM in response to TheGerman2004

The problem started when I encrypted disk, so for now is better make the disk decrypt

Oct 12, 2011 3:16 PM in response to TheGerman2004

10.7.2 resolve my problem:

The volume HD appears to be OK.

🙂

paulvee

Level 1

4 points

May 9, 2012 4:22 PM in response to wavemotion

10.7.4 came out today. Updated five startup drives on my Mac Pros and one on my MacBook Pro - I have two drives in that machine - but when I updated the second drive, the startup drive, and THE ONLY ONE RUNNING FILEVAULT, I got an error when I tried to verify the drive with disk utility. It said that "Problems were found with the partition map which might prevent booting" and then the red error message "Error: Storage system verify or repair failed."

Now, I did NOT upgrade from legacy Filevault with Lion. I de-encrypted first and then updated and then re-encrypted with FileVault 2, but my gut tells me FV is the problem. Why? Cause that's the only real difference here.

I called Apple and got maybe the worst tech support guy ever. He didn't know about the 10.7.4 update at all. Then, when I explained my problem and paused and said "wait, what did you say about file vault again?" It was like he was smoking weed. I was disgusted, so I called back and got somebody who was at least semi-present.

I'm de-encrypting now and plan to run Disk Repair again when that's done. Maybe that'll fix it. Then, my next step will be to try to repair it from the Recovery Partition. What a drag.

Anybody else out there with this issue?

May 10, 2012 11:20 AM in response to paulvee

I'm doing that now. Simply because my MBP with Lion will not boot when restarting. It also fails to shut down and boot with the latest 10.7.4 update. Using repair disk from the startup DVD I created, it shows errors on the log, but when done shows that it appears to be ok. If I use the disk utility while booted in lion to verify the disk, I get the "may prevent booting" message.

Hopefully turning off FileVault and decrypting will allow disk utility to fix the errors and booting freezes. It will take approx 4 hours to finish.

May 11, 2012 10:14 AM in response to SuperSizeIt

After decrypting which took about six hours. Disk Utility no longer shows "may prevent booting". I'm not sure if I want to turn Filevault back again until the issue is fixed by Apple.

May 20, 2012 2:51 PM in response to paulvee

I add my voice to yours: Only after running the 10.7.4 on my FileVault2 protected 15" MacBook Pro (2010) did I get the "Problems were found with the partition map which might prevent booting" error -- and can confirm that it corresponds with FileVault2

Here's a sequence of events that may help Apple (if they are listening) to diagnose this

1) The drive (and partition) passed Disk First Aid (DFA) testing prior to running the 10.7.4 update

2) I did my customary backup (clone using Carbon Copy Cloner, CCC) and updated (Combo) to OS X 10.7.4

3) A week later I ran Disk First Aid again (prior to doing another CCC clone and got the error listed above (and then performed my backup)

4) Booting from my clone, wiped and recreated the partiion on my MBP's internal drive, and installed Lion. DFA gave it a clean bill of health

5) After installing Lion, I cloned from my backup to my MBP's internal drive. Rebooted from the internal drive, and DFA again said all was well.

6) Activated FileVault2 again, permitted two of the three accounts to be unlockers. I let it complete, and rebooted.

7) It rebooted normally, and the ran DFA again -- and the error (which had not been present prior to initating File

Vault2 whole disk encryption) was back.

I have never had a problem with FileVault2, and conclude that one of the things that they fixed to permit peaceful coexistence with the original FileVault has caused this apparent problem.

Apple, please take note.

Tim Fall

Level 1

65 points

Jun 6, 2012 4:59 PM in response to Steve Davidson

I just wanted to add that I get this error as well. Booting into recovery mode and repairing the disk was successful, but when logged back in, verifying the disk gave the same error.

Aug 9, 2012 6:27 PM in response to Tim Fall

Good news, all. After turning off FileVault2, upgrading to Mountain Lion, and turning it back on again fixed the problem. It would seem that Apple introduced a bug, and then fixed it. For me, at least, case closed.

Verify Disk Fails on 11" Mid-2011 MBA