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!

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.

Similar Messages

Disk utility error when erasing an external hard drive

Hi,
Not sure if this is the most appropriate fourm list to post this but I thought I'd give it a try.
I am running snow leopard on my MBP and am trying to use disk utility to erase and format an ext. HD. While the disk icon does not show up on the desktop when I connect it to my mac, Disk utility does show the ext. hd in the left column, but no matter what format I try, even just using one partition and selecting zero out all data, I get the following error: "disk erase failed with the error: POSIX reports: The operation couldn't be completed. Cannot allocate memory".
Is the hd dead? Are there other options? I do have disk warrior, version 4.1.1 and it does not regonize the ext. hd.
Please advise.
Thanks,

Thanks for the reply. Yes, I did select the ext hd as the one I wanted to erase (my internal hd is my start up drive). After I selected the ext hd, (there is no volume listed under it so the only thing I can select is the hd itself). that is when I selected erase and then Mac journaled, then named the hd and then after selecting erase, I got the error. Also as a matter of note, if I select firstaid, both the repair and verify permissions are dimmed, so I can't even try to repair the disk. That is when I tried disk warrior hoping that could examine the hd, but since it is not mounted on the d/t, it doesn't show as a drive to check. I don't understand why the ext hd shows up in disk utility, but not the d/t. Also of note is the fact that when I connect that ext had to my Mac with a fw cable, a window opens saying that the drive is not readable and do I want to initialize it or ignore. I choose to initialize and that is when I get the error. Also of note is that I have tried both security options of "don't erase data" and "zero out data" and still get the same error.
Hope this clarifies things a bit.

Disk Utility error when restoring a drive to another drive: Error 6

"Device not configured."
I have a 24" iMac with a 250gig hard drive, and a firewire enclosure with a 160 gig hard drive. The iMac has a windows partition that I am trying to back up on the firewire drive, so that I can repartition and make the windows section bigger, but I keep getting errors when trying to restore.
If I uncheck erase destination, and then click restore, it starts to copy for a few minutes, but after 2-3 gigs of copying I get another error:
"Restore Failure An error (2) occurred while copying. No such file or directory"
This happens again and again and again and again. Any ideas?

Thanks for the different responses. Just a few more details. My internal hd is only using 63 of 100g.
So I don't think the disk space issue for disk utility would be the answer to my particular problem. I have also tried using superduper to back up this same drive; however, it would not complete the task either. Would it be better to just back up the user folders separately and maybe the applications folder and then just use the mac os dvd's to install on my new drive? ( I don't guess backing up the applications folder would do any good; they would have to all be reinstalled. ) Just trying to find a way to get this done without having to do to much reinstall work. Any other ideas?

Disk Utility Error- Filesystem verify or repair failed.

I ran Disk Utility and before it finished I received Filesystem verify or repair failed error message.
It says to run repair but I can't
HELP!!! What do I do? What is wrong?
Thanks

Hi , and a warm welcome to the forums!
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.

Disk Utility Freezes When Verifying HD

Not sure what's gone wrong here--hoping you folks can help me out.
I wanted to make sure my OS X directory was in okay shape, so I tried to "verify disk" using Disk Utility. After a few seconds, the application becomes completely unresponsive. Activity Monitor shows the process as "Not Responding" in red. Attempting to quit the process locks Activity Monitor. Shortly after, the entire system is frozen.
I've deleted the preference files in my home folder, but that didn't change the behavior.
The same issue occurs in my mother's account.
I booted up from my install disc and tried to repair the disk. It failed with the error "The Disk 'Macintosh HD' could not be unmounted. I then clicked the "verify disk" button, and my disk "appears to be OK."
Any ideas what's causing this unusual behavior? I'd like to get things working as they should, if possible.
Oh, and this is my MacBook, running OS X 10.5.6. The Macintosh HD partition is 66.9 GB & 12.36 GB is free.
Just realized I haven't repaired permissions; going to do that now, then try again and see if repairing permissions makes any changes.
~Lyssa

DaddyPaycheck:
I'm running DU from my computer. It came with Leopard installed (I bought this computer last spring). If I'm running it from my computer, I should be running the latest version then, right?
Carolyn:
*Are you referring to the com.apple.DiskUtility.plist?*
Yes, that's the one! I deleted it, then tried running DU to verify the disk again, but the same issue occurred--the application froze.
*"Oh, and this is my MacBook, running OS X 10.5.6. The Macintosh HD partition is 66.9 GB & 12.36 GB is free. 12GB out of 70 is cutting it kind of close. You really need to be in the 10 to 15% free drive space range minimally."*
If I've calculated things right, I should have about 10GB free in order to have 15% of my drive free. I know I'm cutting it a little close, but this is the best I can do, for now.
As mentioned in my initial post, I can't repair the disk. Disk Utility fails with this error: "The Disk 'Macintosh HD' could not be unmounted." The Verify Disk option does work, and comes back with the report of "The Disk appears to be OK."
I used BootCamp to partition my drive for Windows, so I can't repair the entire drive, just the "Macintosh HD" portion. S.M.A.R.T. status is verified.
I'll give the AHT a go after I get home from class later today. I'll also try the steps in the article you linked--thanks!
If you folks have more suggestions, let me know.
~Lyssa

DIsk Utility Hangs When Formatting USB flash drive

I have a 4gb USB drive (Jetflash by Transcend) that's been usable formatted as FAT. I'd read that i/o would be a lot faster if I formatted as Mac OS Extended instead. In fact, I've done this with previous USB drives with success. When I try to reformat the drive in Disk Utility, it stalls at "Preparing to Erase." I've also tried going through Partition instead, but again, just stalls at the beginning. This is not a freeze or hang or spinning ball moment, but it will just sit there not doing anything. I can quit out of DU at any time. I've left DU alone, thinking this just may take a while, but it has stayed this way up to 3 hours. Suspiciously, there are no blinking lights on the usb drive during this process. I realize every USB flash drive must have different firmware that reacts differently to Macs and I may just be unable to Mac-format this. I've also taken the drive to other Macs all running 10.4.7 with the same results. Any ideas or workarounds will be appreciated. Thanks.

Update: I've tried on a 3rd mac, my g5/1.8 at home and plugged the USB flash drive to a powered usb hub. Now Disk Utility doesn't stall, but instead immediately states that it can't access the partition map. As the drive has public/private partition capability and also security features, I'm going to assume that's the reason for it to be only formattable as FAT. So now I'm looking for large capacity flash drives that are mac-formattable or find information that throughput is the same on a USB drive no matter how it's formatted.

Disk Utility can't verify or repair hard drive

I started up my Tibook using the install disk and ran disk utility to try and repair my hard drive and it went through the verification process and then said that there was an error and it could not repair the disk. It says that it needs repaired, any suggestions?
Also, when I come back to my computer after being gone several hours, I'm having trouble getting the computer to respond. It's not supposed to go to sleep or go to screen saver, but when I come back, the programs take a long time to respond - any ideas on how to fix this?
thanks in advance.

This is what Disk Utility says when I try to verify:
Verifying volume “Hard Drive”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Overlapped extent allocation (file 479297)
Overlapped extent allocation (file Overlapped extent allocation (file plications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs/eco85.html)
Overlapped extent allocation (file 640270 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs/eco9.html)
Overlapped extent allocation (file 640272 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/dev.html)
Overlapped extent allocation (file 640273 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/dw.html)
640273 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/dw.html
ped extent allocation (file %@)",1)
640274 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/kbshortcuts.html
Overlapped extent allocation (file 640275 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/la.html)
Overlapped extent allocation (file 640276 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/sp.html)
Overlapped extent allocation (file Overlapped extent allocation (file Japanese.lproj/Backup Help/pgs2/tips.html)
Overlapped extent allocation (file 640278 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/toc01.html)
Overlapped extent allocation (file 640279 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/toc02.html)
Overlapped extent allocation (file 640280 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/toc03.html)
640280 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/toc03.html
640281 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/toc04.html
Overlapped extent allocation (file 640282 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/toc06.html)
Overlapped extent allocation (file 640283 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/pgs2/tocstart.html)
Overlapped extent allocation (file Overlapped extent allocation (file /wn.html)
Overlapped extent allocation (file 640286 /Applications/Backup.app/Contents/Resources/Japanese.lproj/Backup Help/shrd/nav.js)
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Volume Bit Map needs minor repair
Checking volume information.
Invalid volume free block count
(It should be 2799915 instead of 2799941)
Volume Header needs minor repair
The volume Hard Drive needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair

TS1440 I followed all of the directions after seeing that my laptop flashed the folder with the question mark. But when I went to disk utility to repair/ verify issues w/ start up disk it would not allow me to.button to repair/verify is there but cant be

I followed all of the directions after seeing that my laptop flashed the folder with the question mark. But when I went to disk utility to repair/ verify issues w/ start up disk it would not allow me to. The buttons to repair and modify we're there but they were grey and couldn't be pressed.

Were you trying to repair the disk you were booted from? You can't do that - you need to boot from your install disk, and choose 'Disk Utility' from the 'install' menu.

Ok i get this error when hooking my dvd drive up and tring to use my windows 7 cdNo Bootable device. Insert boot disk and press any key. i have tried to use command key i see the cd icon and hit that and i get the error

ok i get this error when hooking my dvd drive up and tring to use my windows 7 cdNo Bootable device. Insert boot disk and press any key. i have tried to use command key i see the cd icon and hit that and i get the error

Wiley207 wrote:
Believe it or not, it was the FireWire drive that was the problem! I managed to successfully install Windows 7 using an external USB DVD drive!
Well I am truly staggered, I have tried this on two different MacBook Pros, with three different external USB optical drives. Don't know if you googled as I suggested but you would find hundreds of others who have found same thing. The exception is MacBook Air which works with the Apple writer, but I don't know much about this.
Were you doing any of the special workarounds with refedit etc?
What model USB DVD drive?

Slow boot up on 2012 Mac mini with DIY fusion drive

Hello everyone, I bought a Mac mini (2012) 2 months ago with a stock 500GB HDD.
I added another SSD to make a DIY fusion drive, and everything is working fine, except that I'm experiencing a very slow boot up.
I have confirmed both by information from the OS and some tests with command line tools, that the fusion drive itself is a success and absolutely working fine.
The slow boot up happens on cold boot only (a reboot does not have such problem).
Symptom: the Mac mini is stuck on the gray blank screen for about 40 seconds, and then finally shows up the apple logo.
Everything after this is pretty fast and fine.
I have tried the following methods and none of them seems to help:
1. Go Preferences -> Startup Disk, select the Machintosh HD. (Suggested by Apple in the Fusion Drive FAQ)
2. Verify the whole disk along with the partition with Disk Utility.
3. Reset NVRAM by holding Command+Option+P+R during boot up.
4. Reset SCM/PMU.
Does anyone have an idea on the cause of my problem?
Best regards and thank you.

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Select the messages logged after the boot, during the time something abnormal was happening. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
For example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time, not before. Please include the BOOT_TIME message at the beginning of the log extract.
If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

DIY Fusion Drive Problem (8,2)

Hey,
I wanted to go a step further and create my own DIY Fusion Drive. I had no problems installing the new ssd (128gb Samsung 840 Pro) instead of the hdd (standard mac hdd) and moving the hdd to the place where the optical drive has been.
I then proceeded to boot from a recovery USB Stick runing the mountain lion recovery partition on it. I configured both of these drives without any problems and finally created my Fusion Drive (visible in disk utility).
But here are things getting worse. My original plan was to recover from a TimeMachine Backup i created right before I started working on the Fusion Drive. But no, it said an error occured and I should restart the PC. After googling this error a little bit (and trying the recovery over and over again, different attempts to repair the time machine, which doesn't seemed to be broken etc.), I came up with the idea that my TimeMachine data could be corrupted and a whole backup is not possible. No problem I thought to myself.
You just try to install Mountain Lion fresh with your Recovery USB Stick and then get one or two folder from your backup that you need. But nope, installing Mountain Lion aborted with an error too while checking if my MacBook would fit the installation or something.
Last try: Cmd+R to start internet recovery. Downloaded the whole thing. Now I was able to reinstall LION fresh on my system (which of course would be the basic installation since my macbook came with Lion). Problem is: Lion doesn't know anything about Fusion Drive and I couldn't select any drive to install it on.
Right now I'm really thinking about installing the os on the ssd alone, what I didn't want to do. But I'm not seeing a possiblilty to get the system back up and running they way I wanted it to.
Now it's on you guys. My last hope. Do you have any ideas on how to fix this problem? I read so many guides and neither of them came up with the problems I have. They just say "and after configurating your fusion drive, you just install moutain lion again and you're good" :|
Thank you very much,
MrMütze

I just tried what would happen if a delete the Fusion drive again. I was able to start the installation process of LION to my SSD, but Mountain Lion still aborted with an error while evaluating my system. So it shouldn't be a problem associated with the FusionDrive.

Disk utility can't repair external hard drive

A couple months back, I had to get a whole new hard drive case for my external because the power cord broke. Anyway, It's worked fine until now...
The hard drive doesn't show up with the other volumes.
It does show up on Disk Utility. When I try to repair or verify the drive, it works up until the end, but then it automatically quits and it says this:
Verifying volume “FIREWIRE”
** /dev/disk1s1
** Phase 1 - Read FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
Unable to read directory (Input/output error)
Error: The underlying task reported failure on exit
1 non HFS volume checked
Volume needs repair
Anyway, I have 45GB of music as well as movies and photographs that mean a lot to me so I hope I don't have to erase the drive or anything...
Thanks to anyone who helps me out.

Hmm, I can't seem to find anything on Windows (XP) that will fix my exact problem...
Then again, I am the crappiest Windows user ever so, once again, any help would be great.
I searched "disk repair" on the help and support center, and it gave me a bunch of ways to fix the drive depending on the problem. The thing is, none of the problems seemed to match mine...
Your personal data files are missing or have been corrupted, or you want to revert to a previous version of a file.
After updating a device driver, you can log on, but the system is unstable.
After installing a new device, the system is unstable.
Changes made to your system or application settings are causing your computer to run poorly and you do not know how to restore the previous settings.
After installing an application, the system is unstable or an application is not working properly.
Operating system does not start (the logon screen does not appear)
I'm not really sure what the exact problem is, I just know that it isn't working on the Mac, but it is on the PC.

Disk util error bootstrap transaction group:23102

So out of know where my MacBook Pro (13-inch, Mid 2012 10.10) is having problems. Its hanging up on a lot of things like safari, lagging when I turn the volume down, and more. When I try to boot to recovery mode using option nothing shows but my hd, when I do CMD R i am able to go to disk utill. When I tried verifying disk I get these messages. If I hit repair on the top mac had drive(see pic) it just keeps telling me to repair. If I do a verify disk in the second mac hd that is under it and indented it tells me to back up my stuff and reinstall. This transaction group error changes on me many times.
Also I have my fire fault turned off It was on but i turned it off

MRDJones wrote:
… I replaced hard drive …
That was sensible.
… I used a external enclosure on the failed hard drive but I get the same error when trying to use disk utility on it. … The drive will not mount.
Those symptoms are consistent with a failing or failed hard drive.
Related
Storage problems, Core Storage, Disk Utility, checksums, fsck_cs and cksum mismatches

Is this a spurious disk utility error?

Still mianly running Tiger from my internal drive, but will transition to Leopard.
I have installed Leopard on an external drive - if I run Disk Utility to check the internal Tiger drive from Leopared i'm told the Volume Header needs minor repair.
If I run the same test using Tiger's Disk Utility, then I do not get this but there's an odd %) entry, unless it was always there:
*Verifying volume “Macintosh HD”*
*Checking 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 Macintosh HD appears to be OK.*
*Mounting Disk*
*1 HFS volume checked*
* Volume passed verification*
So could the error from Leopard Disk Utility be spurious (eg related to changing Startup disk to the external one), or if likely to be real is it safe to Repair from Leopard - I cannot currently find my Tiger installation disc to run DU from there!
AC

Do not use Leopard's Disk Utility to repair disk of Tiger OS. They are different OS's and have different parameters. Nothing to query about. If you can't find your Tiger installer disk then try booting (holding command-s), when you see the white text type:
fsck -yf hit return
repeat until no errors are found. Then type:
reboot -n hit return
Again do not use Leopard to repair a Tiger disk.
Then go find your Tiger installation disk. It should be in a zip lock bag in the drawer next to your Mac.

Weird Error When Verifying External HDDs

Hello
I'm getting a weird error when verifying my 2 external HDDs. Both give me an "invalid leaf record count" error. But only when I check them with the OSX install cd. If I check them in my user account, they come up OK. Both drives also gave me a "reserved fields in the catalog record have incorrect data" error. Disk Utility was able to fix that error, but not the invalid leaf error. I have tried multiple repairs, but DU says the volume cannot be repaired. The other weird thing is when I ran the first repair, it said 1 HFS Volume Repaired and 1 Volume could not be repaired. I have also tried using Disk Warrior, but it gives a "this volume appears to be formatted with a newer version of the OS" error.
Both these drives I had plugged into my mom's iMac (running 10.5--my eMac is running 10.3.9) because I had firewire problems back in June. Did 10.5 modify something that has 10.3 mixed up?
Is there something I can do to fix this or do I need to do another re-install?
Music Luver
"+I hear her playing music+..." ~ Barry Manilow

OS X 10.5 does add additional attributes bits to the file descriptors, so using the drive under 10.5 would be expected to add those additional bits to at least the disk directory plus any modified files.
When you then check the drives using utilities created prior to OS X 10.5, those older utilities don't understand the additional bits and report then as errors (DU), of the utilities check first and refuse to run if the disk is tagged as from a latter OS version (DW).
There's a generic warning about mixing older utilities with newer OS versions in Only use Mac OS X 10.4-compatible disk utilities with Mac OS X 10.4 volumes.
I'd be ready to shrug the error reports off as spurious; however, that DU "corrected" the reserved bits suggests the drive directories will be rewritten again should you again move the drives to a 10.5 computer. Are you seeing any actual problems wiuth reading or writing to the external drives? If not, write it off to 10.5 settings bits that earlier versions ignore; it shouldn't affect your data.

Disk Utility error when verifying DIY fusion drive

Similar Messages

Maybe you are looking for