Disk Utility error -39 when making image of HD backup

Whenever Apple releases a substantial update I first make a backup of my boot disk to an external Firewire drive before installing it. Before overwriting the existing backup, however, I make a compressed image with Disk Utility on another partition.
With 10.4.4 and 10.4.5 making the image fails with error -39. Somewhere I read that the error had to do with Disk Utility's not being able to cope with large disk images.
Is anybody experiencing this problem? Is there a solution, a workaround, or another program that I could use?

1. For reasons I don't know disc images seem to become more fragile the larger they get. They also can be subject to file corruption that affects the entire disc image, whereas file corruption on a clone would only affect certain files.
2. You cannot put multiple clones on the same volume. Each clone must be on a separate volume, but you can have multiple volumes on a single drive simply by partitioning the drive accordingly. Of course you need a drive large enough to accommodate each clone. Each clone should be to a space equal to the capacity of the cloned drive.
3. I'm not a big fan of TM, although I must confess it has become more reliable since it's release, especially with Snow Leopard. However, there are many backup utilities that can create clones, perform incremental updates, and archive changed files. See the following:
Backup Software Recommendations
Carbon Copy Cloner
Data Backup
Deja Vu
Silver Keeper
MimMac
Retrospect
Super Flexible File Synchronizer
SuperDuper!
Synchronize Pro! X
Synk Pro
Synk Standard
Tri-Backup
Others may be found at VersionTracker or MacUpdate.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.

Similar Messages

Disk Utility Error 61 when attempting to create disk image on external driv

I would like to make occasional archive backups of my three macintosh computers. I bought a new Western Digital 2TB drive for this purpose, and formatted it as Mac OS Extended. Trying to do a disk image backup using Disk Utility, I follow the directions:
- Startup from an install DVD.
- Start Disk Utilities and select "Restore"
- Drag "Macintosh HD" into the Source box
- Click on "New Image" and select compressed and 128-bit AES encryption
This leads to the error message: Unable to create "....." (error -61)
I have enocountered this problem both with my iMac G5 and a MacBook, both running Leopard.
Does anyone know what this error means, what I am doing wrong, and/or if there is another way to create disk image backups? Help!

1. For reasons I don't know disc images seem to become more fragile the larger they get. They also can be subject to file corruption that affects the entire disc image, whereas file corruption on a clone would only affect certain files.
2. You cannot put multiple clones on the same volume. Each clone must be on a separate volume, but you can have multiple volumes on a single drive simply by partitioning the drive accordingly. Of course you need a drive large enough to accommodate each clone. Each clone should be to a space equal to the capacity of the cloned drive.
3. I'm not a big fan of TM, although I must confess it has become more reliable since it's release, especially with Snow Leopard. However, there are many backup utilities that can create clones, perform incremental updates, and archive changed files. See the following:
Backup Software Recommendations
Carbon Copy Cloner
Data Backup
Deja Vu
Silver Keeper
MimMac
Retrospect
Super Flexible File Synchronizer
SuperDuper!
Synchronize Pro! X
Synk Pro
Synk Standard
Tri-Backup
Others may be found at VersionTracker or MacUpdate.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.

Disk utility errored out when attempting to repair Macintosh HD

My iMac suddenly got really slow this morning, occasionally freezing for a few minutes. I ran disk utility to repair permissions, MacJanitor and then restarted to no avail. Then I started up using the original install CD (10.4.4), ran the hardware test and passed, and attempted to repair the disk with Disk Utility. I got through the first steps, but then when checking the Catalog File, I got the following error:
Invalid Node Structure
Volume Check Failed
Error: Underlying task reported failure on exit.
Before I exited, I repaired disk permissions again, and this time it found a bunch of bad permissions...when I restarted, system was still slow, so I know I still have a problem
Any suggestions on what to do next?
Thanks,
Eric

Try that disk repair a few more times, you never know!
But more then likely it won't be able to repair an Invalid Node Structure. That's a pretty serious error.
If Disk Utility can't fix it, you'll need a more robust utility for the repair. I would recommend DiskWarrior. It is the best at directory repairs. It rebuilds then actually replaces your old directory. I feel every Mac owner should have a copy. Make sure you get the disk so you can boot up on it to run repairs. You can also install it on another drive and run it from there to repair this one. DW works faster that way.
I use DW once a month to try and catch errors in my system from getting too far out of hand.
If you have a good backup, hopefully a clone of your system before you had issues, an Erase and Install will also rid you of this issue. But, beware! You will lose everything on the drive with this procedure. Let us know if you need help with that!
Cheers! DALE

A Disk Utility error message when creating a dmg file

I was trying to create an encrypted dmg file on a USB Drive. It was going smoothly, I had entered the password twice, and then 30 seconds later I got an error message: "unable to create "name-dmg" -illegal seek"
I tried the Help menu, as well as Sherlock to search AppleCare but couldn't find a thing.
Any ideas?

1 The DU info says....
Name.....Kingston
Type.....Volume
Disk Identifier....Disk2s1
Mount Point....../volumes/KINGSTON
File System....Mac OS Extended
Connection bus...USB
Partition type....Apple_HFS
Writable.....Yes
Universal Unique identifier...(too long to write it too)
Capacity....7.5GB
Free Space....&.5GB
Used.......12.5MB
Number of Files....6
Number of Folders....4
Owner enabled.......No
Can turn owners off....Yes (I'll say)
Can be formated....Yes
Bootable....Yes
Supports Journaling....Yes
Journaled.....No
S.M.A.R.T. Status.....Not supported
Disk number....2
Partition number....1
2. The file names I tried were "Financial" then the default on "Disk2s1". By default I mean it's already inserted when the window appears.
3. The size of the image of the image I want to create is 7GB. But like I said this latest attempt a field for selecting a size wasn't in the window. I did set it for 7GB originally.

Disk Utility Problems - Can't make image or restore

I am having difficulty in making disk images & restoring using disk utility.
Issue 1 - Making an image of a DVD for the purpose of burning a copy (non commercial)
In DU I select the DVD in the sidebar, click new image DVD/CD master & save to desktop. The progress indicator reached about halfway & I get the following message: Unable to create "image name.cdr" - input/output error.
The source DVD in in the internal optical drive.
What causes this problem & can it be fixed? Why is the image .cdr not .dmg?
Can an image be made directly from a DVD?
As a workaround I used DU's restore function to copy the entire DVD contents to a free (27GB) partition on an internal HDD (not system disk) in the hope that I could make an image fron there. As soon as I clicked on restore both the DVD & target drive unmounted. After the progress bar reached 100% I got the following error message: Restore Failure. An error (5) occurred while copying. Input/output error
However if mounted in DU the partition has been renamed to the DVD name & the contents seem to be the same as the DVD.
What is error 5?
I then created an image from this partition using DVD/CD-R master format which worked OK but created a 27GB image - too large to burn!
How can I make the image small enough to fit on a DVD-R?
Can an image be made directly from a DVD?
Is this normal DU behaviour??
Once I get this right I plan to used DU to backup to an external HDD (I'm in the process of recovering from a drive failure and although I have most of my data back through partial backups & recovery like many before me I'm going to have better backups from now on!!)
Any help would be apprecialted.
Thanks in advance.
John

It may be the the disc after all...
I'm still having the same problem, but I also discovered that I cannot get the install disc to get past the "spinning gear" stage when trying to start up with it, so yes, it's most definitely useless! My MacBook is still under warranty so I phoned Apple, and explained the problem and everything I did to ensure it wasn't hardware related. So they're sending me new install discs. I'm not 100% convinced yet that the problem is the install disc, but we'll see...my only doubt remains from the fact that I was able to make a disc image of it on my G4. That said...
I did a hardware test (long version, and everything is reportedly fine), played dvd movies, burned cd's, installed software from discs, etc, and it seems the drive is working fine, however, it could possibly be sensitive to even the slightest smudge or scratch (the install disc has a few very slight marks on it that shouldn't be a problem, and I cleaned it thoroughly). The only other time I had a problem was when I went to rip a song from a cd to iTunes where it hung and and then failed to complete the task. (The cd itself played without issue though.) I checked it for dirt/scratches: it had a couple of barely imperceptible smudges and one shallow scratch. I cleaned it, tried it again and iTunes was able to import from it after that. This remains the only time (so far) I've had a problem with a disc besides my install disc.
I want to be able to repair disk before I install 10.5.3, and back up everything, including the install discs. My Macbook came with 10.5.2 and except for this problem, everything's been working fine.
When I get my new install discs, I'll post how that went. They should arrive within a week or so.
DrHouseTF: I checked out your thread. I've never tried to make copies of game disks via DU, but maybe it's due to copy protection measures on the disc itself?
Message was edited by: iMsP
Message was edited by: iMsP

Disk utility not working when upgraded to Yosemite

I have two MacBook pros (one is a mid 2010 13 inch and new Mid 2014 15 inch Retina), both of which disk utility stopped working when updated to OS X Yosemite from Mavericks. It says "You can't use this copy of Disk Utility with this version of OS X. Open the copy of Disk Utility located in the Utilities folder of the Applications folder of your startup disk." I was able to fix the old 13 inch by clearing the hard drive and pressing CMD+R to reinstall the OS but the new macbook I have not been able to fully clear the SSD. And for some weird reason my bootcamp partition on my 15 inch is being read as a totally separate hard drive instead as a partition.
Any help on totally erasing the hard drives and making them one is greatly appreciated!

If you don't already have a current backup, back up all data, then reinstall the OS.* You don't need to erase the startup volume, and you won't need the backup unless something goes wrong. If the system was upgraded from an older version of OS X, you may need the Apple ID and password you used.
If you use FileVault 2, then before running the Installer you must launch Disk Utility and select the icon of the FileVault startup volume ("Macintosh HD," unless you gave it a different name.) It will be nested below another icon with the same name. Click the Unlock button in the toolbar and enter your login password when prompted. Then quit Disk Utility to be returned to the main Recovery screen.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it. The same goes for Xcode. All other data will be preserved.
*The linked support article refers to OS X 10.10 ("Yosemite"), but the procedure is the same for OS X 10.7 ("Lion") and later.

Disk Utility Error: The underlying task reported failure on exit 1

    #!/bin/bash
      # Author : Bill Hernandez
    # Location : Plano, Texas
    # Updated : Saturday, June 6, 2009 (1:48 PM)
    # script name : setdisk_ownerenabled
    # make sure to set permissions to execute
    <hr>
    # Description :
    <hr>
    # I've noticed that sometimes when using disk utility I cannot repair permissions, or I might get :
    # ERROR: The underlying task reported failure on exit 1
    # This shell script seems to have solved the problem.
    # It worked very well for me,
    # IF YOU USE THIS SCRIPT, IT IS AT YOUR OWN RISK...
    # DO NOT USE IT UNLESS YOU UNDERSTAND WHAT IT DOES
    # After running it, it is best to restart before using Disk Utility again
    <hr>
    # Details :
    <hr>
    # After partitioning a disk using "Disk Utility", and then begin using it, at some point I would get
    # an arror message when trying to save to one of the partitions, yet when I looked at the permissions
    # everything looked fine. I would then try to use Disk Utility to repair permissions and end up with a
    # cryptic error that pretty much told me nothing.
    # I noticed that while in Disk Utility, if I selected a partition the lower LH corner of the dialog
    # showed : Owners Enabled : No
    # I tried selecting the partitions at the Desktop and doing a (CMD-I) and at the very bottom of each
    # info dialog there was a checkbox :
    # [ ] ignore ownership of this volume
    # which I would check, even after logging in as root, and I couldn't seem to get a consistent way
    # to get rid of the permissions dialog failure, so I found the vsdbutil command which can be used
    # as follows to get partition, or disk info :
    # $ vsdbutil -c /Volumes/driveor_partitionname
    # ----> Permissions on '/Volumes/driveor_partitionname' are enabled.
    # if it is not enabled you can enable the disk or partition using :
    # $ vsdbutil -a /Volumes/driveor_partitionname
    # It will set "Owners Enabled : Yes"
    # This below script loops through the mounted disks, partitions, etc. and gives you information.
    # You can leave the three flags below all set to TRUE, or selectively use what you want and change
    # the rest to false...
    <hr>
    # CHOOSE {"TRUE", "FALSE"}
    <hr>
    getvolumestatus="TRUE"         # get "Owners Enabled : (Yes|No)" status
    setvolumestatus="TRUE"         # set "Owners Enabled : Yes"
    list_volumes="TRUE"                   # show volume names
    <hr>
    # DO NOT CHANGE ANYTHING BELOW HERE
    <hr>
    if [ $getvolumestatus == "TRUE" ]; then
     echo '============================='
     echo '$getvolumestatus'
     echo '============================='
     # get "Owners Enabled : (Yes|No)" status
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     vsdbutil -c $i
     done
    fi
    <hr>
    if [ $setvolumestatus == "TRUE" ]; then
     echo '============================='
     echo '$setvolumestatus'
     echo '============================='
     sudo echo -n
     # set "Owners Enabled : Yes"
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     sudo vsdbutil -a "$i"
     echo "setting Owners Enabled : Yes for ---> $i"
     done
    fi
    <hr>
    if [ $list_volumes == "TRUE" ]; then
     echo '============================='
     echo '$list_volumes'
     echo '============================='
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     echo $i
     done
    fi
    <hr>


As it turns out, this didn't completely solve the problem, it solved part of the problem.
Here is a summary to the root cause of the problem.
SUCCESS...
Problem Summary : The system crashed and would hangup during boot, tried many things, until I eventually erased the disk and started over again.
iMacG5 24 GHZ Intel with One internal disk partitioned into 3 logical drives
Cub_1 OS X 10.5.7
Cub_2 OS X 10.5.7 (Carbon Copy Cloner backup of Cub_1)
Cub_3 OS X Server 10.5.7 (standard os x server setup)
At some point after setting up standard preferences, OS X Server crashed.
When I tried to restart, the machine would hang up during boot.
Finally after several attempts, ran Disk Utility from install dvd and repaired Cub_3
When I tried to run "Repair Permissions" on Cub_3 from install dvd, I got an error
Disk Utility Error: The underlying task reported failure on exit 1.
Rebooted, and started in single user mode (CMD-S) during boot until I saw the unix commands on the screen
RAN : root # fsck -fy
Then I began seeing the same command filling the screen :
posix_spawnp("/usr/sbin/mDNSResponder") could not find file or directory
Called Enterprise Support and spoke to Frank Alcorn, he said this was most likely a permissions problem and asked me to try repairing permissions from the install dvd. I told him about the error, but nevertheless I tried it again and got the same Disk Utility Error: The underlying task reported failure on exit 1..
He asked me to try booting into single user mode again, and to try
root # chmod 775 /
root # reboot
During the reboot process the machine got hung up again, and could not get the single user mode to work at all.
Frank said the command needed to be :
root # chmod 1775 /
Frank asked me if I had changed anything in file sharing, and I told him I had. He asked me what I had shared, and I said the entire drive Cub_3. He asked me what I had done for permissions, if I had denied permissions to anyone. I told him that I had set myself up as the only user that could have access to it, and when he said that's where the problem was the lightbulb went off, and it made sense.
Shortly after I set the sharing preferences is when the server crashed. It all makes sense now...
Frank said not to share the entire disk, only portions (share points) of it. I had done this in Panther Server, and Tiger Server and it worked fine, but apparently Leopard Server works a little differently, maybe more secure.
It seems to me that if sharing the entire disk, which is what I needed would cause such a problem there should have been some sort of warning from the operating system, but there wasn't. I had run into this problem several times over the past three weeks since I had started working with Leopard Server, but in each case I ended up re-installing OS X Server and starting over again.
I told him I would try to reboot from the OS X partition (Cub_1) and try it from there.
He asked me to let him know if it worked, and I said I would...
Problem FIX :
I booted back into the partition containing OS X (Cub_1) and did the following via the Terminal.
$ su - root
$ chmod 1775 /
$ reboot
During the reboot process I held down the (OPTION) key, and selected Cub_3 (the os x server partition) and sure enough after a few minutes of holding my breath the login window magically appeared. So I logged in, and did not have to re-install the server. Hallellujah....
This solved the boot hang problem. It is great to finally have an answer. In retrospect it makes sense, but that's why its hindsight...
The reason for sharing the entire disk in my mind was that since I was the only user on the system, it was easier to have one disk mounted on my workstation rather than several folders. It made sense to me, it still does. I don't need a bunch of folders, just one disk is easier...

Hard drive says I have more than 300 GB available with a 500 gb capacity. Yet I get "Low Disk Space" error messages when I do anything.

Hard drive says I have more than 300 GB available with a 500 gb capacity. Yet I get "Low Disk Space" error messages when I do anything.
Attempted solutions:
-I created a new User Account and I can download large files with no issues.
-I ran "Repair Disk Permissions" but still get warnings.
Google Drive Warning:
Spotify Warning:
But on my other user account I can use spotify and download large files, etc.

Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
This time you'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
Boot into Recovery. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

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: Creating a new blank image receiving "file too large" error.

Hello All!
I'm trying to create a 10GB non-encrypted, non-compressed RW blank image via the disk utility. The DU runs for a few minutes then barfs out "file too large" error. I have over 30GB free on my HDD. I tried with a smaller size of 6GB to no avail. Also tried unsuccessfully to create from a file (about 4 GB). My ultimate goal is to create a case-insensitive image to run an extremely important program needed for high priority work productivity (i.e. WoW). Thanks in advance for any advice! You will be my new best friend if you help me resolve this. =D
Hollie
"There are only 10 types of people in this world: Those who understand binary, and those who don't."

Hi Hollie, and welcome to the forums!
Have you created images before successfully?
Is this to/on your boot drive, or an external drive?
Have you done any Disk/OS maintenance lately?
We might see if there are some big temp files left or such...
How much free space is on the HD, where has all the space gone?
OmniDiskSweeper is now free, and likely the best/easiest...
http://www.omnigroup.com/applications/omnidisksweeper/
WhatSize...
http://www.macupdate.com/info.php/id/13006/
Disk Inventory X...
http://www.derlien.com/
GrandPerspective...
http://grandperspectiv.sourceforge.net/

Disk Utility stops responding when creating a CD/DVD image

I'm using a PowerBook G4 (Intel processor) and recently updated from 10.5.8 to Snow Leopard.
I've been copying some personal DVDs (Non-commercial so not copy protected) with Disk Utility.
It was working just fine under 10.5.8, and for the first DVD after updating.
However now when I try to create an image from the DVD, the dialog box opens as though it is
reading from the DVD (As usual) but the progress bar doesn't move.
When I try to cancel, the spinning beach ball comes up and end up having to force quit.
I have tried with various DVDs but the result is the same.
I have shutdown and restarted, and even reset the P-RAM for good measure, but to no effect.
There is no Disk Utility file in the preferences folder so I was unable to trash preferences.
FYI: I bought the computer in Japan so I am using the Japanese OS, but I expect that should
make no difference to the problem.
Any suggestions for troubleshooting would be greatly appreciated.
Thanks in advance!!

Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.
Isolating an issue by using another user account
If the problem is still there, try booting into the Safe Mode using your normal account. Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don't do them all at once.
Safe Mode
Safe Mode - About

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.

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 is crashing when trying to create a new image

Seriously need some help if anyone has an idea of why disk utility is crashing while trying to create a disk image. I'm not finding any other info on this issue.
My HD is failing and being replaced tomorrow and I'm desperately trying to create disk images of both my mac HD and of bootcamp for the new drive being installed.
Any recommendations or suggestions would be truly appreciated.

Thank you for responding so quickly. I do have Carbon Copy Cloner, but if disk utility isn't working, getting it to restore is going to be an issue, though haven't attempted a restore since the HD has to be replaced.
CCC also doesn't clone bootcamp either unfortunately.
Currently running "verify permissions" using Disk Utility and so far so good, it hasn't crashed, it seems to be an issue related to imaging with disk utility.
Then I am going to attempt using the install disk to see if I can get disk utility again and try imaging Bootcamp again too.

Disk Utility errors: No such file -or- No space left on device (50GB+ free)

I am trying to make an image out of a _NTFS formatted_ parition, using around 4,5GB of data, of a freshly installed Windozs. It's for debugging tons of machines I have been given (to debug..) and I need an image done. Note that debating if using an image as a solution is good or not is not the point of this thread.
When I try to make a new image out of the parition (clicking "New Image"), using the defaults settings, I enter my admin pass, then I'm being shown "No space left on device". Wierd. The device I am writing the image onto has 51GB left, and the Trash is emptied.
I tried changing the image format to all the possible types in Disk Utility, but I get the same error: No space left on device.
I then changed the device, this time I used a volume with 10GB free on it. Then, I only managed to get a standard DMG compressed image, where I need a "DVD/CD master" one. I'm still confused, because no other image type worked.
Then I tried making a new image (not from a disk or volume, empty) and then just copy data to it (I'm sure it's really not the way to go, but still). After creating the empty image (I opted for an 8GB, DVD burnable style, "DVD/CD master"), I got the wierd error: No such file (straigth after the image creation, in Disk Utility).
More info about volumes and stuff:
Data to be imaged:
A single partition on a volume (connected with IDE to Mac Pro, but I don't see why it would matter)
Where I can save it:
I got a big bunch of volumes right here, internally.
I tried one with 50GB free, but failed. Another one, on another disk, with 10GB, but failed.
Also, this error comes often in Disk Utility and other unix OS I think, and mostly for no real known reason (in OS X), as most issues I found were still unresolved.
Thanks for any help

Hey,
Im having the same exact problem.
Toast even says it has a medium error with this drive.
I cant burn with toast and it wont play other DVD-R movies
that I have burnt on other systems.
What is the fix?

Disk Utility error -39 when making image of HD backup

Similar Messages

Maybe you are looking for