Disk Utility Restore - Why error -34 ?

I cloned my 700 G3 iBook's 20GB hard drive to a 30GB ext. HD with Disk Utility>Restore before sending it for repair. Now that I have gotten it back I want to restore the data to the computer's HD. I'm getting error -34 (disk full).
So what is the nature of my problem? Must the destination disk be at least as big as the source disk? (Because it is copying the entire 30GB size.) Or must I empty (erase, reformat) the destination disk? (Because it is adding the data to what is already there.)
Thanks

Michael:
You were right. Thanks. The data would have been added to what was already there.
While I had made back-up clones before, this was the first time I needed to put it back into the computer's hard drive.

Similar Messages

  • Disk utility  input/output error, my macintosh HD won't mount and when restoring to another HD fails after setup...

    Disk utility, input/output error, setup fail

    Had issue partitioning 2TB my passport drive, got input/output error while using disk utility.
    Here is what I did to get my external disk back
    In Disk Utility
    1) Try to use erase option first, it failed
    2) Try to partition the disk, failed as well.
    3) Then try erase option again, then ...   it worked !!

  • How to clone disk (Disk Utility Restore, boot: kernel panic)

    Hi, I've tried two times to clone my 120GB system disk (old Core2Duo Mac Mini (macmini2,1)) to a 1TB disk attached via USB cradle. Running Snow Leopard 10.6.8 which long time ago was upgraded from Leopard.
    Used the Disk Utility "Restore" for cloning. Both times Disk Utility completed without errors. However when I swap the 1TB from USB cradle into mac mini (to internal SATA), the result of even a "Save Mode" boot attempt with Shift/Mod key held is always a kernel panic: "unable to find driver for this platform: \"ACPI\"
    As my goal is to clone the existing system to a larger drive, a new install of OS X on the 1TB drive is out of the question. The original 120GB disk boots without problems. But the cloned attempts do not boot.
    Judging from the kernel panic it is as if "Restore" doesn't actually restore, but leaves out files. Thus Disk Utility restore in SL is buggy?
    Or is my cloning method wrong? Currently I just drag the 120GB system disk (the live running system) to the Source, then drag the 1TB USB disk to Destination, and allow full erase of destination, and do the priviledge elevation to root i.e. the usual password prompt. Does successful cloning need something extra...?

    If I understand correctly, what you're doing is copying your 120 GB drive to the 1 TB drive, then swapping the 1 TB drive into your Mac and trying to boot from it, and it fails.
    You're doing it wrong, and that's why it fails. A Finder copy (what you're doing) does not respect permissions or symbolic links, which are required to make the system boot. You need to use something that does respect that.
    Get your hands on a copy of SuperDuper http://shirtpocket.com/
    (free for basic use, but it's well worth the small fee of $27.95 for full access to all features); and/or
    Carbon Copy Cloner http://bombich.com
    and use one of those to make a bootable clone of your 120 GB drive, then you can boot from it.

  • Disk Utility: Restore no longer creates bootable images?

    So I have a new hard drive for my macbook, and followed the procedure I used last time of using disk utility restore to write the current hard drive image to the new disk, with the new disk in a USB enclosure.
    I have done this before, it creates a bootable copy on the new disk, swap the disks away I go.
    This time however the new disk is not bootable. When starting it gets to the grey screen with the rotating white pips then dumps back to a black screen with error messages (like its trying to boot of the network).
    Swapping back to the old disk boots just fine, so its a problem with the image written to the new disk by disk utility restore not being bootable.
    Is this a known issue? I searched the forum with no answers, and am frustrated that its now working as I have run the image twice now at about 5 hours a go for 100GB of data so I am sure its not the copy. Straight after the copy the original disk has about 10 more files than the new disk that's just been imaged, has their been some update to disk utility in the OS X patches that means it no longer copies some key files?
    Note that partition on new disk is GUID as it should be, and I don't want to re-install anything from the install media I want to use make disk utility work as designed.

    I found two references that may help:
    A) At http://everythingapple.blogspot.com/2007/11/use-powerpc-mac-to-create-bootable.h tml it says "PowerPC Macs use the Apple Partition Map, but this poses no problem for Intel Macs, even though Intel Macs use the GUID Partition Table. The reverse is not true however. PowerPC Macs cannot boot disks with a GUID Partition Table."
    1. Open up Disk Utility and select your backup drive. Select the "Partition" tab.
    2. Go to the "Options" and choose "Apple Partition Map", which is the partition type necessary for PowerPC Macs.
    B) Carbon Copy Cloner - Red Dot Warning on main screen: "The target volume will not boot this computer because PowerPC Macintoshes cannot boot from USB devices."
    Looks like I'll have to install the 2.5" SATA drive into my PowerPC MacMini to upgrade my system volume from 80gb to 320gb.

  • I have a mid-2010 27" Quad Core i5 iMac running 10.8.3.  Startup disk recognizes the primary hard drive as a startup volume but will not boot from it.  Have tried zapping PRAM, ran disk utility.  No errors reported  Any thoughts?

    I have a mid-2010 27" Quad Core i5 iMac running 10.8.3.  Startup disk recognizes the primary hard drive as a startup volume but will not boot from it.  Have tried zapping PRAM, ran disk utility.  No errors reported  Any thoughts?

    My bad Eric. The startup preference recognizes the primary as a 10.8.3 startup volume but when u select it the system does not boot. I can only boot from my external backup drive

  • After i enter my password for the wifi in internet recovery mode it just shows a blank screen no disk utility shows why??? NEED HELP

    After i enter my password for the wifi in internet recovery mode it just shows a blank screen no disk utility shows why??? NEED HELP

    Enter your admin passwrod, not Wi-Fi network password.

  • Disk Utility Restore

    I copied my macbook pro's hard drive to an external drive using disk utility restore. Is it normal for the copy's overall size to be smaller than the original? I thought it would be the same size? The external had no data on it. The original is 273.54 GB and the copy is 271.45 GB... Problem?

    May I try to answer your question. When you copy a disk there are a number of files which are not copied such as Trash, swap files and any temporary files that may have on the old disk will not be copied to the new disk. So while the approximately 2 GB of data might at first glance seem like a lot, it is in fact not really that much. I hope that helps you to understand what is happening there.
    |___________________
    Allan

  • Disk Utility Restore Process Input/Output Error

    <Image Edited by Host>
    My niece's MBP specs above. If I posted a picture of this poor machine, there'd be a lynch mob of passionate Apple fans arrive at my door wanting a public hanging...It's been dropped no less than a dozen times. (The ethernet port is stretched out of shape so badly that a standard plug will no longer fit the port!!!).
    Among other physical injuries, the screen won't present an image (just flickers white lines on black background, hinge has partially detatched, suspect the ribbon that transmits the display signal has been compromised). A visit to the Apple store tells us (by plugging into a cinema display via TB) that the hard drive is still in tact and data is salvageable. Keyboard and trackpad both work fine (surprisingly).
    Long story short, she's acquired a new MBA, been read the riot act about looking after it, and I have the unenviable task of salvaging her data, approx 275Gig.
    My objective is to obtain:
    1. A full copy of the data (existing file structures) - Complete
    2. A bootable disk image of the MBP - Incomplete and troublesome
    I have at my disposal:
    Mid 2011 27' iMac (Intel i7) on Mav
    MBPr13 (third host if needed) on Mav
    A home ethernet network with enterprise grade switching
    A Lacie 5BigPro 10TB NAS
    A couple of 1 & 2 TB Toshiba external drives, and
    Enough network adapters, USB cables and thunderbolt cables to suffice. Admin priviliges all round. All disk permissions repaired.
    Current connection config is the MBP thunderbolted to the iMac. I can use TDM (if I need to interface with the MBP using the iMac display) or can boot in Target Disk Mode if I want to see the MBP disk image on the iMac.
    Regarding Objective2: A bootable disk image of the MBP, I first tried to use the Restore function in Disk Utility, but that only works when booting the host in Recovery mode, whcih doesn't support TDM, so I'm flying blind...
    Next try, I booted the MBP in Target Disk Mode, which allowed me to use the Restore process from the iMac's Disk Utility, select the MBP HD, and target an external drive (one of the Toshiba's) plugged in to the iMac via USB.
    I've now tried this Restore 3 times, each time getting the following I/O error (at about 45 munites in to a projected 4 hour process):
    Any thoughts on root cause?
    And (given my screen/display limitations) am I missing a far simpler option?
    Cheers, Sla

    If that were the case you would not get in/out errors. These errors occur because the drive is no longer able to transfer data which is a hardware failure.
    If you want to post an image to the forum then you need to open the message editor and click on the Camera icon you will find in the editor's toolbar. Then select the image you wish to post and click on the Insert button.
    You can try running the Apple Hardware Test to see if it reveals anything.
    Using Apple Hardware Test
    Intel-based Macs- Using Apple Hardware Test

  • Why is Winclone Needed? Can't Disk Utility Restore a Boot Camp Partition?

    Hi. Could we just use Disk Utility to create a backup the Boot Camp Partition running Windows 7 64-bit for example and then just use Disk Utility to restore it if you need to replace your Boot Camp partition?
    Why is Winclone the tool use to create an image of Boot Camp partition as well as to restore a Boot Camp partition? Thank you in advance.
    Gbu.

    Thanks for the reply. How about if you opt for the non compressed image, the DVD/CD Master option (Image Format) when you do the New Image in Disk Utility? Would choosing the DVD/CD Master option be cloning it instead of archiving it? If the images created by Disk Utility are not the exact copy or clone then, it won't be bootable I believe but how come when you create an image of a DVD (to back it up for example) and burn that image, it is bootable which mean it copies it exactly (clone it in effect)?
    What does WinClone do or copy exactly that Disk Utility can't?

  • Disk Utility Restore Error

    Hello All,
    The Boot Camp Assistant told me that I had to reformat my hard drive as Mac OS Extended (Journaled) so I:
    -Cloned the drive with Carbon Copy Cloner,
    -Booted from my external hard drive, and
    -Erased my internal disk (Using Disk Utility).
    Now, when I try to restore (using Disk Utility) from my external to my internal drive, I get one of two errors:
    -RESTORE FAILURE: Lost connection to helper tool.
    -RESTORE FAILURE: Could not establish connection with helper tool.
    Does anyone have any idea what's going on? I've gone through this whole thing once before for Boot Camp, but the last time didn't yield any crazy errors...

    It had occurred to me to try that but the Boot Camp Assistant told me that it couldn't partition my drive because some files could not be moved. If I just clone it back, won't things be just the way they were before? That's just a guess of course, my whole train of thought could be off

  • Why does good disk utility image generate error message?

    I created a disk image of a data cd using disk utility. When I open the dmg file I get the message:
    "The disk image you are opening may be damaged and could damage you system. Are you sure you want to open this image?"
    When I open the image there are no issues and the content is correct. Why is this message being generated and what can I do to keep it from happening?

    Hi Burkely,
    "The disk image you are opening may be damaged and could damage you system. Are you sure you want to open this image?"
    This is a standard message ...
    Dimaxum

  • Disk Utility - Restoring a previous image

    Since I first bought my Mac Mini (February of this year) I've been using the disk utility to make occasional backups (disk images) of my partitions, in case I ever need to restore a whole partition (or create a clone of an existing partition - for example, so that I could test some new software that might cause problems). I've never actually needed to restore a partition (or produce a clone from one of the backup images) until today. However, when I first bought my Mac I did test this feature and it seemed to work.
    A few days ago I realised that I'd soon need to clone a partition so I backed up my Mac HFS partition which is about 90GB in size (my internal disk being 500GB). I then used Coriolis iPartition to create a new, empty Mac HFS partition of the same size, then tried to use Apple's Disk Utility to restore the newly created disk image. However when I came to try the restore, I got an error saying that the image would first need to be "image scanned" before being usable. I then tried an old image that I created when I first bought the Mac and currently, that one seems to be restoring.
    AFAIK I've used the same method to create both images so why did the old one work when the new one didn't??
    Message was edited by: johne53

    Hmmm.... I've just realised that none of the images I've created recently will verify properly. They all get to the end of the first stage (block checksum of partition #1) and then fail with "internal error". The only one which passes the verification process is the very first one which I created a long time ago. That one seems to complete two stages of block verifications (for 2 partitions) then one "file checksum".
    If I try to select a disk image and use "Open Disk Image" (from the right-click menu) I get an error saying "Unable to attach [image-name].dmg. No mountable file systems." This happens with every disk image I've created, apart from the very first one.

  • Disk Utility Crashing - Dyld error

    This is a FYI for a problem I solved...
    Symptoms: Disk utility would crash when opened (crash report below).
    Also opening hwmond or emond from terminal resulted in this error:
    Referenced from: /usr/sbin/hwmond
      Reason: no suitable image found.  Did find:
              /System/Library/PrivateFrameworks/PlatformHardwareManagement.framework/Ver sions/A/PlatformHardwareManagement: no matching architecture in universal wrapper
    Trace/BPT trap: 5
    The fix I found was to remove "/System/Library/PrivateFrameworks/PlatformHardwareManagement.framework" and restore a fresh copy from OSInstall.mpkg (found within the OS X installer) using Pacifist.  I had to resort to this because re-applying the latest OS X combo update didn't fix it.  Neither did resetting dyld cache or repair permissions. I'm not sure why the PlatformHardwareManagement framework broke....  But after replacing that framework Disk Utility is launching fine now. I thought I'd post this in case others are googing a similar error.  Hope this helps!
    Disk Utility crash report (shortened)
    Process:         Disk Utility [368]
    Path:            /Applications/Utilities/Disk Utility.app/Contents/MacOS/Disk Utility
    Identifier:      com.apple.DiskUtility
    Version:         12 (346)
    Build Info:      DiskUtility-346000000000000~225
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [206]
    Date/Time:       2011-11-16 13:00:30.331 -0800
    OS Version:      Mac OS X Server 10.7.2 (11C74)
    Report Version:  9
    Interval Since Last Report:          113 sec
    Crashes Since Last Report:           35
    Per-App Crashes Since Last Report:   4
    Anonymous UUID:                      280A4971-2E24-4B18-A5E5-2DB90E5AE1F5
    Crashed Thread:  0
    Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Application Specific Information:
    dyld: launch, loading dependent libraries
    Dyld Error Message:
      Library not loaded: /System/Library/PrivateFrameworks/PlatformHardwareManagement.framework/Versions /A/PlatformHardwareManagement
      Referenced from: /System/Library/PrivateFrameworks/ServerFoundation.framework/Versions/A/ServerF oundation
      Reason: no suitable image found.  Did find:
              /System/Library/PrivateFrameworks/PlatformHardwareManagement.framework/Ver sions/A/PlatformHardwareManagement: no matching architecture in universal wrapper
    ::snip::
    Console errors:
    11/18/11 10:32:29.642 AM com.apple.emond: dyld: Library not loaded: /System/Library/PrivateFrameworks/PlatformHardwareManagement.framework/Versions /A/PlatformHardwareManagement
    11/18/11 10:32:29.642 AM com.apple.emond:   Referenced from: /System/Library/PrivateFrameworks/ServerFoundation.framework/Versions/A/ServerF oundation
    11/18/11 10:32:29.642 AM com.apple.emond:   Reason: no suitable image found.  Did find:
    11/18/11 10:32:29.642 AM com.apple.emond:           /System/Library/PrivateFrameworks/PlatformHardwareManagement.framework/Ver sions/A/PlatformHardwareManagement: no matching architecture in universal wrapper
    11/18/11 10:32:30.179 AM com.apple.hwmond: dyld: Library not loaded: /System/Library/PrivateFrameworks/PlatformHardwareManagement.framework/Versions /A/PlatformHardwareManagement
    11/18/11 10:32:30.179 AM com.apple.hwmond:   Referenced from: /usr/sbin/hwmond
    11/18/11 10:32:30.179 AM com.apple.hwmond:   Reason: no suitable image found.  Did find:
    11/18/11 10:32:30.179 AM com.apple.hwmond:           /System/Library/PrivateFrameworks/PlatformHardwareManagement.framework/Ver sions/A/PlatformHardwareManagement: no matching architecture in universal wrapper
    11/18/11 10:32:30.223 AM com.apple.launchd: (com.apple.emond[4707]) Job appears to have crashed: Trace/BPT trap: 5
    11/18/11 10:32:30.223 AM com.apple.launchd: (com.apple.emond) Throttling respawn: Will start in 10 seconds

    As Doug has said, & indeed you have tried....you need to run diskutility from the OS install disk. Or more accurately, you need to run diskutility when booted from the install disk.
    The following ( from diskutility help) should explain it clearly.
    Start up your computer using another disk.
    To use the Install Mac OS X disc, insert the disc and restart your computer holding down the Option key, then select the Install Mac OS X disc and click the arrow.
    Open Disk Utility.
    If you're using the Mac OS X Install disk, follow the onscreen instructions until the menu bar appears with the Utilities menu in it., and then choose Utilities > Open Disk Utility.
    Select the startup disk in the list of disks and volumes, then click First Aid.
    Check the S.M.A.R.T. Status at the bottom of the window. If you can't see it, be sure you selected the hard disk your volume is on, and not the volume itself.
    If the S.M.A.R.T. Status is "About to Fail," back up your files on the disk as soon as possible and replace the disk.
    If the S.M.A.R.T. Status is "Verified" or "Not supported," click Repair Disk to repair the disk.
    If Disk Utility tells you to look for links to corrupt files in the DamagedFiles directory, two or more files occupy the same space on your hard disk and at least one of them is likely to be corrupt. Examine each affected file in the DamagedFiles folder, which at the top-level of the affected disk. If you can replace it or recreate the file, delete it. If it contains necessary information, open it and examine its data to make sure it has not been corrupted.
    If Disk Utility reports "The underlying task reported failure," Disk Utility encountered a problem it could not repair. Back up as much of your data as possible, reformat your disk, reinstall Mac OS X, and restore your backed up data.

  • Disk utility - restoring a .cdr question

    i hate the format of the apple discussion forums now.
    not sure if this is the proper place since there is no "community" to discuss Disk Utility and the "restore" function, which is not specific to snow leopard, but since i'm still running 10.6.8, i'll go ahead an post this here.
    in the past, i've successfuly restored disk images onto dedicated hard drive partitions.  i do this for a variety of reasons, namely to have working backups of certain DVD's, such as my install DVD's when internal super drive stopped functioning.
    however, i just tried this following what i think are the proper instructions, but now i can't restore the disk image and can't find the answer anywhere online.
    basically:
    1)  i'm going into disk utility, hooking up an external dvd drive and copying a playable DVD of some live music i purchased
    2)  i'm choosing "create new image" and under compression, choosing "dvd/cd master"
    the problem is that the resulting file comes out as ".cdr" and not .dmg.  i haven't tried it using some type of compression, but for some reason Disk Utility won't let me "restore" from a ".cdr" file, only a .dmg or .iso.
    i've tried changing the extensions.  i've tried converting (within disk utility) the .cdr to .dmg, and i get the same "invalid argument" error as always.
    the only thing i haven't done is tried making another .dmg using some type of compression, or read-only, read-write format.
    it would seem to me that choosing cd/dvd master is the proper category.
    does anyone know why a .cdr will mount, but cannot be used for restore???  and why making a disk image of a disk i own defaults to .cdr and not .dmg?
    thanks.
    666

    Hmmm.... I've just realised that none of the images I've created recently will verify properly. They all get to the end of the first stage (block checksum of partition #1) and then fail with "internal error". The only one which passes the verification process is the very first one which I created a long time ago. That one seems to complete two stages of block verifications (for 2 partitions) then one "file checksum".
    If I try to select a disk image and use "Open Disk Image" (from the right-click menu) I get an error saying "Unable to attach [image-name].dmg. No mountable file systems." This happens with every disk image I've created, apart from the very first one.

  • Disk Utility: Restore Failure

    I'm trying to restore my laptop from a dmg file. I have the laptop connected to another computer in target disk mode. When I try to restore, just after it starts copying I get this error:
    Restore Failure
    An error (2) occured while copying. (No such file or directory)
    I created the image with Carbon Copy Cloner and hdiuti to make it UDRO formatted. The computer I'm using to try and restore it is a G5 tower running Mac OS 10.4.7 and I'm using Disk Utility version 10.5.6. Does anyone know why I'm getting this error? Should I convert it to some other format? Are there other ways to restore the disk that might work, if Disk Utility refuses to?

    Sure you can... You mount the disk image on your Desktop. Run CCC. Select the disk image as Source Disk. Select the hard drive as Target Disk. Go (or Clone).
    (also, CCC does not make disk images; it clones)

Maybe you are looking for