Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

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

User profile for user: Alexander Grove
Alexander Grove Author
User level: Level 1
19 points

Disk Utility error when verifying DIY fusion drive

Hi,


It has been a while since I had to post a problem, but I need others advice on this if you can help. When 10.8.3 came out I installed an M4 512gb ssd in my main drive bay of 2008 unibody aluminium macbook and put a 1tb spinner in the optibay. Created a fusion drive, migrated data and all has been great. Decided to run disk utility today to check for any errors as I had a sleep issue with the 10.8.4 update which I ended up solving by changing the sleep settings in terminal - the issue had caused a few forced shutdowns. I have Disk Utitliy Version 13 (450). The Fusion drive is shown as the logical volume group followed by the volume disk. When I run a verify disk on the volume itself it is all ok:


Verifying volume “Cybernet”

Checking storage systemChecking volume.

disk0s2: Scan for Volume Headers

disk1s2: Scan for Volume Headers

disk0s2: Scan for Disk Labels

disk1s2: Scan for Disk Labels

Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices

disk0s2+disk1s2: Scan for Metadata Volume

Logical Volume Group has a 2170 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

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Incorporate 6 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 Volume

Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3

Load and verify 5388E543-6974-4251-BDBD-FA850C121897

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Live Virtual Addresses

Newest transaction commit checkpoint is valid

Load and verify Segment Cleaning

The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.

Checking file systemPerforming live verification.

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 Cybernet appears to be OK.




When I run it on the LVG it comes up as:


Verifying partition map for “M4-CT512M4SSD2 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

disk1s2: Scan for Volume Headers

disk0s2: Scan for Disk Labels

disk1s2: Scan for Disk Labels

Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices

disk0s2+disk1s2: Scan for Metadata Volume

Logical Volume Group has a 2170 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

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Incorporate 40 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 Volume

Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3

Load and verify 5388E543-6974-4251-BDBD-FA850C121897

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Live Virtual Addresses

Newest transaction commit checkpoint is valid

Load and verify Segment Cleaning

The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.

Incorrect size for volume “Cybernet”

Problems were found with the partition map which might prevent booting

Error: Incorrect size for logical volume.

Verifying partition map for “WDC WD10JPVT-00A1YT0 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

disk1s2: Scan for Volume Headers

disk0s2: Scan for Disk Labels

disk1s2: Scan for Disk Labels

Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices

disk0s2+disk1s2: Scan for Metadata Volume

Logical Volume Group has a 2170 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

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Load and verify Transaction Segment

Incorporate 43 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 Volume

Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3

Load and verify 5388E543-6974-4251-BDBD-FA850C121897

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Live Virtual Addresses

Newest transaction commit checkpoint is valid

Load and verify Segment Cleaning

The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.

Incorrect size for volume “Cybernet”

Problems were found with the partition map which might prevent booting

Error: Incorrect size for logical volume.

.


I got the same when I did a safe boot and when rebooted from the recovery partition.y question is, do I repair or could it damage my setup? eg is Disk Utility being accurate and it can repair the error, or is it a phantom issue that should be ignored bearing in mind it's a DIY fusion drive and it could end up getting mashed?


Thanks!

MacBook, OS X Mountain Lion (10.8.5), DIY Fusion Drive - 512gb SSD 1TB HD

Posted on Oct 24, 2013 9:03 AM

Reply
Question marked as Best reply
User profile for user: Eric Root
Eric Root
User level: Level 10
684,069 points

Posted on Oct 24, 2013 11:33 AM

How is your computer performing? If it is okay, then you can leave it for now, but at some point, you will need tom boot into the Recovery Volume and repair the disk. It shouldn't hurt to try this, but make sure you do a backup before doing anything.

View in context
4 replies
User profile for user: Alexander Grove
Alexander Grove Author
User level: Level 1
19 points

Oct 24, 2013 11:40 AM in response to Eric Root

Hi,


The computer's running fine since I sorted the sleep issue. No issues as far as I can tell, which is why I was surprised to see the error. What does the error actually mean - is it saying that the volume is a different size than the computer thinks it should be and therefore it'll just change a few values? In which case I suppose a repair is harmless? I just don't want to repair and then reboot to find the volume corrupted.

Reply

Disk Utility error when verifying DIY fusion drive

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up