Verify Disk Fails on 11" Mid-2011 MBA

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.

Well, now you've added new information not mentioned previously. However, if a drive becomes corrupted then that's a drive issue. It is possible the corruption may have been caused by something else, but there's no way of knowing. Drive corruption is not necessarily a Lion or FileVault issue.

All that Disk Utility is telling you is that the disks directory structure is OK. It doesn't test for bad sectors, damaged data, etc.

I have the same problem and my drive is encrypted with Filevault 2. Here is a copy of my Disk Utility results-

Verifying partition map for “TOSHIBA MK7559GSXF 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

Checking all HFS data partition loader spaces

Checking Core Storage Physical Volume partitions

Checking storage system

Checking volume.

disk0s2: Scan for Volume Headers

disk0s2: Scan for Disk Labels

Logical Volume Group D6C6B140-FF84-4215-A23B-2F338FDB07DE spans 1 device

Logical Volume Group has a 16 MB Metadata Volume with double redundancy

Start scanning metadata for a valid checkpoint

Load and verify Segment Headers

Load and verify Checkpoint Payload

Load and verify Transaction Segment

Load and verify Transaction Segment

Incorporate 1 newer non-checkpoint transactions

Load and verify Virtual Address Table

Load and verify Segment Usage Table

Load and verify Metadata Superblock

Load and verify Logical Volumes B-Trees

Logical Volume Group contains 1 Logical Volumes

Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E

Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Segment Cleaning

Unable to bootstrap transaction group 5720: invalid field value

Continue scanning metadata for an older checkpoint

Load and verify Segment Headers

Load and verify Checkpoint Payload

Load and verify Transaction Segment

Incorporate 0 newer non-checkpoint transactions

Load and verify Virtual Address Table

Load and verify Segment Usage Table

Load and verify Metadata Superblock

Load and verify Logical Volumes B-Trees

Logical Volume Group contains 1 Logical Volumes

Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E

Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Segment Cleaning

Unable to bootstrap transaction group 5719: invalid field value

Continue scanning metadata for an older checkpoint

Load and verify Segment Headers

Load and verify Checkpoint Payload

Load and verify Transaction Segment

Incorporate 0 newer non-checkpoint transactions

Load and verify Virtual Address Table

Load and verify Segment Usage Table

Load and verify Metadata Superblock

Load and verify Logical Volumes B-Trees

Logical Volume Group contains 1 Logical Volumes

Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E

Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Segment Cleaning

Unable to bootstrap transaction group 5718: invalid field value

Continue scanning metadata for an older checkpoint

Load and verify Segment Headers

Load and verify Checkpoint Payload

Load and verify Transaction Segment

Incorporate 0 newer non-checkpoint transactions

Load and verify Virtual Address Table

Load and verify Segment Usage Table

Load and verify Metadata Superblock

Load and verify Logical Volumes B-Trees

Logical Volume Group contains 1 Logical Volumes

Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E

Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Segment Cleaning

Unable to bootstrap transaction group 5717: invalid field value

No valid commit checkpoint found

The volume D6C6B140-FF84-4215-A23B-2F338FDB07DE 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.

This is a brand spanking new Macbook Pro 8,2 with a clean install of lion with my user account migrated from a time machine backup. The weird thing is that if I boot to the recovery partition and verify the disk, it comes back clean with no errors. When I log in again and run disk utility immediately after logging in, disk utility shows no errors. I only get these errors after the machine has been on for a while.

I have tried just doing a repair disk in the recovery partition to see if it would help but I still get the same errors after a few hours of use. I think there is a bug with Filevault.

I am using 10.7.1

FileVault only encrypts your Home folder. It does not impact on whether the drive's directory is corrupted. If you boot from the Recovery HD and then use Disk Utility you can repair the drive instead ov verifying it. Verifying a drive will not repair anything.

I am using filevault 2 on Lion. It encrypts the entire drive. Please re read my statment under the log results.

Thanks though.

I suggest you post your own topic.

I am having the same issue as the OP. Why would I create a new post for the same issue? I am uploading a video right now that should be up in about 2 hours (slow internet connection). Maybe seeing the issue on video will give you a better understanding of what is happening for myself and the OP.

Thanks

Unfortunately I don't have an Apple Store to visit as I am in Thailand. Can you take a look at my video and let me know if we were having the same issue. Also, have you ran a disk check that came back with no errors after 5 or 6 hours of use?

Thanks

http://www.youtube.com/watch?v=TS9Tr900hts

This isn't specific to MacBooks - it seems to be related to FileVault 2. I've got the same on an 2011 iMac after turning on FileVault 2 these errors appear in DiskUtility

I have the same issue here. Two mac books pro with File Vault on Lion and sometimes Disk Utilty show

"Unable to bootstrap transaction group 2413: invalid field value" . When I boot using DVD and use Disk Utility this message does not show up.

.

Same issue with 2 MacBooks running Lion and FileVault 2. After a forced poweroff a check with disk utility shows the "Unable to bootstrap transaction group xxxx: invalid field value" error.

1. I've tried booting in single user (command-S) and running fsck. Shows no error.

2. Booted in safe mode (shift), but disk utility stills shows the error after boot.

3. Checked the disk with recovery mode (command-R) but this shows no error.

Sometimes the problem has gone away eventually by itself. A sure fire way to fix seems to be to decrypt and then re-encrypt the entire drive but naturally this takes a long time to do.

I do wonder if this is anyway related to spotlight, as on every boot after I get this error spotlight is indexing for around 20 minutes.

after the restart everithing seems fine, but after 5 minutes the problem persist

Mba with lion and filevault (i bought it 5 days ago.....)

I decrypted my ssd disk....no problem during the verify....now i'm trying with time machine problem....