Unable to clone HD in Disk Utility

I have bought a new Hard Drive for Time Machine, and was wanting to clone my old TMHD to the new HD so as to not lose any of my old back-ups and to then continue backing up on the new HD.
My old HD is a 250gig and the new one is 1tb.
In Disk Utility I select the old drive as source and the new drive as destination and then click restore.
It thinks about it for a while and then comes back with the error that the file is too large. But if I am trying to copy a 250gig to a 1tb how can it be too large?
Both drives are MS-DOS(Fat), but all my external drives are so I don't think that would be an issue.

Okay, I have finally completed the task that I set about trying to complete a week ago.
I reformatted the drive s instructed above as one partition of GUID Mac OS Journalled format.
I then wanted to clone my Time Machine back up hard drive to the new hard drive in Disk Utility. When I tried using the restore function, it would copy all the back-up's that had been created using "Backup", but would error out on the first app when copying the time machine backups.
Confused, I then tried Carbon Copy Cloner and it too errored out, but on the third app in the apps folder of the first time machine back up file.
Before giving up I tried to clone the hard drive using Super Duper!
11 hours later I now have a perfectly working cloned hard drive. I redirected my time machines to the new hard drive and it backed up to the correct folder as if nothing had changed. So all is good now and I just wanted to thank everyone for their advice.
Thanks.
PS. I have no idea why DU and CCC errored when copying... but at this point, I don't really care. It worked with Super Duper!

Similar Messages

Error message while trying to clone harddrive using Disk Utility

I've been trying to clone my MacBook Pro's harddrive in advance of installing Leopard. I've been trying to clone to a LaCie Ethernet Disk mini. It's connected to my computer with a USB cable. It does about 1/3 of the disk, then I get the following error message:
An error (2) occurred while copying. (No such file or directory)
At this point the disk cloning stops.
An advice would help, thanks.

kory wrote:
I'm trying to use Disk Utility to clone it. I have verified and repaired both the MacBook Pro HD and the external HD with Disk Utility.
*Hi Kory, Welcome (Back)* to Apple's Users Help Users Forums.
In addition to Utilities Restore, these are popular Cloners.
http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html
Purchase at $27.95 will allow smart backups that look at the bu files and only move over new ones. It's quick at ~7 mins to change ~1 gig out of 20.
Be sure to test that the clone boots and apps behave properly.
Here are other popular cloners.
http://www.bombich.com/software/ccc.html
http://www.prosoftengineering.com/products/drivegeniusinfo.php?PHPSESSID=909c070fb2e13b35097fa9cc1340bfc0
Good Luck, JP
Message was edited by: Jpfresno "In addition to ..."

Clone CD using Disk Utility

Hi. I attempting to make an exact duplicate of a music CD using Disk Utility. It seems to create an image of the disk fine, the dmg file being of appropriate size corresponding to the size of the audio cd. However when I attempt to burn this disk image, nothing happens. I mean, Disk Utility acts as though it's working, but once complete the newly created CD is blank. ??
This is really confusing. If anyone has any advice or perhaps could suggest some third party application for creating, mastering, and burning disk images then that'd be neat.
Thanks.
Billy

I record talks at seminars, edit the content, and burn the CDs for participants.
I've previously used Disk Utility to image the audio CDs for an easier burn at a later date. I tried this recently for the first time since Leopard came out and it no longer works.
So I tried it with Disco, and it also fails to image the disc, doesn't even offer it as an option. Funny, I just updated Disco to the latest version several days ago, this reduced function was not noted in the version log.
Strange, has the RIAA gotten something changed so we can't do this anymore? I'm trying to image a disc of my own recordings. It's outrageous that I can't image my own audio disc.
I also tried using Carbon Copy Cloner, it failed several times, I tried another method and it seemed to be working, only to announce that it had failed.
Anyone with any clues about this?
Joel.

Clone Drive using Disk Utility

Greetings,
Recently my 15, Aluminum FW800 has had the black screen of death. where I can only make out the faintest images on the screen. I took it to my local Genius bar, where he suggested that I send it in for the flat fee of 320 to get it fixed. I figured thats a good deal, so I agreed.
The problem, however, is that he said they may replace the hard drive... thus I need a complete backup of my drive. I used the backup utility in Tiger and selected the entire drive, and 4 hours later I had it copied to an external drive. However, I have also heard that you can clone a drive using disk utility. I figure if this is possible, i might as well try, since I have the space and redundancy is the key to an effective backup.
As mentioned above, though, I can only barely make out the screen, and have no instructions on how to do this backup. Does anyone know of a link that will guide me step by step through this process? I would hate to press the wrong button and erase my drive before its necessary.
Any help would be appreciated.
Thanks

Don't forget that applications have Help menu and Disk Utility has Restore feature (tab).
Before you start, make sure to do Get Info on the drive you want to restore to (target) and turn OFF the "Ignore Ownership" first.
Click on the left side icon for the volume you want to backup (source) and drag it into the appropriate field. Same for target volume.
Apply and sit back while it copies.
When done, use First Aid to Repair Permissions on the target (I would also do same for your source before you begin).
If you don't see and can't repair permissions on the target, something isn't right.
Now make sure you can boot from the target. Make sure it shows up in Startup Disk and try.

Can Disk Utility clone just like CCC and Super Duper?

Is it true that I can create a clone simply using disk utility?
Ive been searching for hours - and i cannot find any support docs on this.
can it be done?
Thanks

Yes. But it's so much easier to use Super Duper.
Here's the Apple doc. I think you want.
DALE

Internal hard drive/repair: SMART status; Disk Utility, Tech Tool & More

machine: 12" PowerBook 1.5 GHz PowerPC G4 (Aluminium) with 80GB internal HD
internal hard drive (original): Hitachi Travelstar 5K100 series HTS541080G9AT00
hard drive firmware: MB4AA5AJ
ATA version: 6
ATA standard: ATA/ATAPI-6 T13 1410D revision 3a
I have monitored the SMART status etc. of my internal drive with smartmontools for some time. Occasionally, I would see an error or a failed self-test but later testing always succeeded and things did not seem to be problematic.
At the beginning of this week, I started to see a lot of failed self-tests (though some still passed), a rising number of bad ("pending") sectors and reallocation attempts (though no reallocated sectors) and various other errors. The computer seemed to have trouble reading from the disk at times and Carbon Copy Cloner reported two I/O errors when cloning (a later clone succeeded). fsck showed errors although running fsck -fy repeatedly seemed to resolve them.
The Apple hardware tests initially reported an error (2STF/8/3:ATA-100 ata-6-Master) but I hadn't realised I should disconnect peripherals before running it so I did that and repeated the test which found no issues. I ran the extended test a total of three times with no errors.
As I continued to have problems, I booted from my clone and had Disk Utility wipe the drive by writing zeros to it. (I thought trying to get it to write everywhere would either finish the drive off or force it to reallocate the bad blocks. As I understand it, in normal use, the drive won't reallocate the blocks unless it can recover the data in the hopes of reading it at a later time.)
I then continued monitoring the disk using smartmontools. At this point, short self-tests succeed but extended self-tests "disappear". They don't fail, they simply vanish. They begin and smartctl shows the test in progress but then no error or result is logged - it is as if the test was never run. The first time I did this, I got an error saying the SMART attributes could not be read but subsequent tests do not trigger even an error. Short self-tests continue to pass.
There are now (according to SMART) zero bad ("pending") sectors but zero reallocated sectors, which seems odd. The raw read error rate fluctuates (zero one minute, many thousands a while later) although I am not sure it did not do this before.
Disk Utility claims the disk does not support SMART status even though smartctl clearly shows it does. Disk Utility claims the volume is "OK".
I ran Tech Tool Deluxe 3.04 from CD and 3.1.1 from my clone. In both cases, I ran all available tests on the drive. No problems were found.
I am seeing some problems even while booted from my clone - yesterday, the system froze completely and I had to force a shut-down by switching off the power (fsck then found a minor error but repaired it). Just before this happened, I was unable to mount a disk image and was trying to rectify the situation when the system froze. It is possible that the errors fsck corrected were implicated in the freeze, rather than caused by it, since Disk Utility found and repaired similar errors for the other two clones I have (on different partitions of my external drive - yes, I know this is sub-optimal).
Here is some current output from smartmontools:
---output: smartctl -q noserial -a disk0---
smartctl version 5.38 [powerpc-apple-darwin8.11.0] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Travelstar 5K100 series
Device Model: Hitachi HTS541080G9AT00
Firmware Version: MB4AA5AJ
User Capacity: 80,026,361,856 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 3a
Local Time is: Sat Jul 3 20:28:52 2010 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 645) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 55) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 RawRead_ErrorRate 0x000b 100 100 062 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
3 SpinUpTime 0x0007 142 142 033 Pre-fail Always - 2
4 StartStopCount 0x0012 097 097 000 Old_age Always - 5793
5 ReallocatedSectorCt 0x0033 100 100 005 Pre-fail Always - 0
7 SeekErrorRate 0x000b 100 100 067 Pre-fail Always - 0
8 SeekTimePerformance 0x0005 100 100 040 Pre-fail Offline - 0
9 PowerOnHours 0x0012 039 039 000 Old_age Always - 26720
10 SpinRetryCount 0x0013 100 100 060 Pre-fail Always - 0
12 PowerCycleCount 0x0032 098 098 000 Old_age Always - 4168
191 G-SenseErrorRate 0x000a 100 100 000 Old_age Always - 0
192 Power-OffRetractCount 0x0032 100 100 000 Old_age Always - 201877487644
193 LoadCycleCount 0x0012 001 001 000 Old_age Always - 2209599
194 Temperature_Celsius 0x0002 141 141 000 Old_age Always - 39 (Lifetime Min/Max 16/46)
196 ReallocatedEventCount 0x0032 100 100 000 Old_age Always - 194
197 CurrentPendingSector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMACRC_ErrorCount 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 2138 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
PoweredUpTime is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 2138 occurred at disk power-on lifetime: 26716 hours (1113 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
10 51 00 09 4f c2 a0 Error: IDNF
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
b0 d6 01 09 4f c2 a0 00 08:30:04.500 SMART WRITE LOG
b0 d5 01 09 4f c2 a0 00 08:30:04.300 SMART READ LOG
b0 d1 00 00 4f c2 a0 00 08:30:04.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 d0 00 00 4f c2 a0 00 08:30:04.000 SMART READ DATA
b0 da 00 00 4f c2 a0 00 08:30:04.000 SMART RETURN STATUS
Error 2137 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 28 18 95 98 e4 Error: UNC 40 sectors at LBA = 0x04989518 = 77108504
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:37.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:30.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
Error 2136 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 21 1f 95 98 e4 Error: UNC 33 sectors at LBA = 0x0498951f = 77108511
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:30.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
Error 2135 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 22 1e 95 98 e4 Error: UNC 34 sectors at LBA = 0x0498951e = 77108510
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
25 00 80 40 93 98 e0 00 1d+01:30:13.500 READ DMA EXT
Error 2134 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 28 18 95 98 e4 Error: UNC 40 sectors at LBA = 0x04989518 = 77108504
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
25 00 80 40 93 98 e0 00 1d+01:30:13.500 READ DMA EXT
25 00 80 c0 92 98 e0 00 1d+01:30:12.100 READ DMA EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBAof_firsterror
# 1 Short offline Completed without error 00% 26717 -
# 2 Short offline Completed without error 00% 26717 -
# 3 Short offline Completed without error 00% 26717 -
# 4 Short offline Completed without error 00% 26717 -
# 5 Short offline Completed without error 00% 26716 -
# 6 Short offline Completed without error 00% 26715 -
# 7 Short offline Completed without error 00% 26714 -
# 8 Short offline Completed without error 00% 26697 -
# 9 Extended offline Completed: read failure 10% 26692 75071682
#10 Short offline Completed without error 00% 26687 -
#11 Extended offline Completed: read failure 10% 26676 77108511
#12 Short offline Completed: read failure 40% 26663 296917
#13 Short offline Completed without error 00% 26657 -
#14 Short offline Completed: read failure 10% 26646 296918
#15 Short offline Completed: read failure 70% 26645 296905
#16 Short offline Completed: read failure 10% 26644 296910
#17 Short offline Completed: read failure 10% 26644 296910
#18 Short offline Completed: read failure 40% 26643 296916
#19 Short offline Completed: read failure 20% 26643 296909
#20 Extended offline Completed without error 00% 26620 -
#21 Short offline Completed without error 00% 26618 -
Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum.
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENTTESTSTATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
---end output---
Self-tests 1-8 were all run after I erased the disk. The others were run before I did so. Not listed are the extended self-tests I've started since erasing which, as I say, have simply disappeared.
The checksum error regarding the log is normal for this disk. At least, I've got that error ever since I started using smartmontools for monitoring so I assume it is normal. (I installed this version of the software in about April 2008 and have used it since.) Also, starting offline testing has never succeeded on this disk (I think I checked into this at the time but can't quite remember - this is not new, anyway).
Questions
how should I interpret all this? (Why does Disk Utility say SMART is not supported while smartctl clearly shows it is at the same time? Why do the extended tests simply vanish? Is the drive definitely dying?) I do not want to replace the disk unless I absolutely have to because I understand that replacing disks in 12" PBs is no small matter and cost is an issue. I do not want to replace the machine unless I have to because cost is an issue and, also, I really like this computer and have no idea what I would want in its place, even if expense were no obstacle.
if it isn't clear whether the drive is dying or not, is there some further strategy I can use to establish this?
if the drive is dying, is a machine of this age worth repairing and, if it is, under what circumstances is it worth doing so? For example, it might be worth doing if you can do the job yourself, but that might be quite impractical for non-expert (not to mention, inexpert) users.
if there is a hardware problem (which I obviously think is very, very probable at this point), is it definitely a dying hard drive? (I've seen people write ominous things about disk controllers etc. which I gather are more serious - or less repairable - than a "mere" dying disk.)
what questions should I be asking you and what are the answers to those questions?!
Many thanks for your patience in reading this far.
- cfr

The 12" PB internals are a bit more complex, for PB's. If you don't want to replace the hard drive yourself or pay someone to install it, you could always get an external firewire hard drive, and use it to boot from and for general usage. Would have to be firewire, since the PB won't book from a USB device. One example of what you could get is a 160GB external hard drive: http://eshop.macsales.com/item/Other%20World%20Computing/MS4U5160GB8/ . All the choices with that case are listed here: http://eshop.macsales.com/shop/firewire/on-the-go
Have you called any Apple Authorized Service Providers to see what they would charge to install a drive for you? Whether you bought it or they supplied it? You can find a local one in the US at http://www.apple.com/buy/locator/service/

Disk Utility won't start up in 10.5.3

I have been unable to open up my Disk Utility at all. I was able to do so earlier, perhaps with 10.5.0 while I was mounting my external hard drive. Now, I cannot mount the hard drive, and therefore cannot use Time Machine all because DIsk Utility won't open. I've diagnosed my hardware with "Disk 1" and found no problem. And, I've reinstalled the operating system. Any ideas?

Chris:
I just had the same issue on my son's MacBook. As long as you have a wired keyboard, the following will work.
1. Shut down the computer if it is on.
2. Press the power button to start the computer.
3. Immediately press and hold the Command (Apple) key and the "s" key for single-user mode.
4. Type mount -uw / (then press the Return Key) wait for next line to appear with # root/
(there is a space between t and - and another space between w and /)
5. Then Type "passwd" (without quotation marks then press the Return Key)
6. Enter new password (this will be for the root user account) (watch your fingers when you type because it doesn't show what you are typing, then hit the Return Key after you type it.
It will prompt you to retype the new password again, so retype it again and then hit the Return Key) wait for next line to appear...
7. Then Type "reboot" (without the quotes and hit the Return Key)
after the computer restarts and comes up with the login window....
8. Login with any of your usernames just to get the desktop up.
9. After desktop comes up choose System Preferences, then choose accounts. Unlock if you have to and using the username: root ..... and the password you just setup in the single user mode You now should be able to make users including your existing user account an admin.
After you log back in under your real account, it is advisable to deactivate the root user account. To do this,
1. Click the Finder icon in the Dock.
2. From the Go menu, choose Utilities.
3. Open Directory Utility.
4. Click the lock in the Directory Utility window if you need to unlock the utility.
5. Enter an administrator account name and password, then click OK.
6. Choose Disable Root User from the Edit menu.
Hope this helps.
David

Please help! My LG external hard disk is not showing in finder and trouble using disk utility

I used my LG external HDD disk drive on my mac a couple of times but now it's not being recognised by my mac anymore and doesn't show up on finder.
I found the disk in disk utility and when i verified it, it said:
Unable to bootstrap transaction group 3164: incorrect block type
Unable to bootstrap transaction group 3163: incorrect block type
Unable to bootstrap transaction group 3162: incorrect block type
Unable to bootstrap transaction group 3161: incorrect block type
No valid commit checkpoint found
The volume AE055338-D940-488B-A5E9-0A6F4701832A was found corrupt and needs to be repaired
Error: This disk needs to be repaired. Click repair disk
I clicked repair disk and it said:
Unable to bootstrap transaction group 3164: incorrect block type
Unable to bootstrap transaction group 3163: incorrect block type
Unable to bootstrap transaction group 3162: incorrect block type
Unable to bootstrap transaction group 3161: incorrect block type
No valid commit checkpoint found
The volume AE055338-D940-488B-A5E9-0A6F4701832A was found corrupt and cannot be repaired
Error: This disk needs to be repaired. Click repair disk
I tried several other times to repair it by clicking repair but the same information kept popping up.
I'm also unable to erase or partition the disk. I have no important files on it so I don't mind deleting them all but i'm unable to do so using disk utility. Please advice on what to do or the steps to take from here. Thanks

http://

'volume check failed', and disk utility can't fix it

I was planning to create a new bootable backup today and ran 'repair disk' from an install disk before cloning.
Unfortunately I grabbed a Panther disk by mistake, and only discovered it was the wrong disk as I took it out. By then, DU had run through the 'repair' - changing quite a few things - until it showed 'volume cannot be repaired'.
I've tried to correct them using DU from the Tiger install disk, but without any luck. DU shows:
+Invalid catalogue record type+
+Volume check failed+
+Error: the underlying task reported failure on exit+
+1 Volume could not be repaired because of an error+
My iBook still appears to be running perfectly, but obviously I need to repair the disk before I can clone it. Disk Utility can't do it - could DiskWarrior?
I'd really appreciate some advice on the options open to me, and the best way to do it.

Success!
I powered down and ran DiskWarrior a 2nd time to rebuild the directory. This time I skipped the recommended Preview stage and went straight to confirming Rebuild. Everything now seems to be fine again. DU finds no faults with the disk, and the iBook feels significantly quicker and snappier.
Two things I learnt that might be helpful - the first is, it's easy to be careless for just a moment and end up in a time-consuming mess. It's the first time I've done it, and I won't be doing it again.
Second thing is, when people say DiskWarrior is slow to boot, they mean it - it took at least 10 minutes to show up on screen, which is unsettling. And the Preview stage, for me, was equally unnerving.
Still, it worked - superbly - all my data is intact, the iBook is overhauled and working faster than ever.

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.

Warning signs when using disk utility for my power mac g5

I have a dual 2GHz PowerPC G5. I just upgraded to the latest Leopard & installed FCP2. I noticed when I use Repair Disk Permissions, there are so many warning signs & I'm not sure what to make of it. I do notice that my computer freezes a lot, can someone help interpret these warning signs for me? And, how do I fix it? Here are some samples of those warning signs during repair disk permissions:
Warning: SUID file "sbin/mount-nfs' has been modified and will not be repaired.
Warning: SUID file "sbin/unmount" has been modified and will not be repaired.
Warning: SUID file "sbin/ping' has been modified and will not be repaired
Warning: SUID file "sbin/ping6" has been modified and will not be repaired
Warning: SUID file "sbin/route" has been modified and will not be repaired
The list goes on and on, please help.
many thanks in advance.

The catalog is the index for all the files on disk. It is useless without the related disk files so cloning just the catalog isn't really an option. You would need to clone the entire drive (SuperDuper!, Carbon Copy Cloner and even Disk Utility will do this).
Disk Warrior is a utility to clean up the catalog, make it into an order that should speed up file operations. It has potential to loose files because of the nature of it's job, but it is pretty reliable in my opinion. The catalog is like a telephone directory for files
The repairing of permissions involves the system keeping receipts of all the things that are installed & updated (with the appropriate permission values) and then the repair permissions utility resets the files to what the receipts say. The recieots are kept in the /Library/Receipts folder. You haven't deleted anything from there have you? if you have you would need to replace them with copies from a similar system, not an easy task.
I believe the items contained in /sbin/ are system binaries that come from the BSD package when installing Mac OSX. I would consider doing software updates then try repairing the permissions again.

Unable to clone hard drive from early 2008 macbook using disk utility, error 254

Attempting to upgrade my early 2008 Macbook hardrive, currently 160gb to a 250gb drive. Using Mac Disk Utility to restore from drive in computer to the 250 gb drive currently attached via usb. Receiving error, Could not validate source, error 254. I know this process works as I recently upgraded our MacbookPro to 1 TB. The 250gb drive I am attempting to clone to is from that computer. I have formated the 250gb drive, mac osx extended journaled, guid. Not sure how to proceed. Suggestions?

To transfer your current hard drive I like the free application Carbon Copy Cloner. It makes a bootable copy of everything on your hard drive http://www.bombich.com/index.html You'll need a cheap SATA external hard drive case. Put the new drive in the case then format and partition the new drive and clone your old drive to the new one. Check that it's set up right by booting up from the external drive. Then replace your old hard drive with the new one and put your old one in the external case.

Disk Utility: Unable to create "ImageName.dmg" error -39

Ladies,
Gentlemen,
I used Disk Utility to backup the internal hard drive of my iMac G5 iSight.
The last backup of the hard drive was unsuccessful, ending with next message: Unable to create "ImageName.dmg"; error -39.
The iMac is running OS X 10.4.11.
I proceed as follows:
Boot from the OS X 10.4.2 installation DVD and firing up Disk Utility.
Menu option: File, New, Disk Image from disk0s3 (Mac HD)
The target disk is Porche_LaCie FireWire drive.
After +/- 2 hours I end up with the above message.
The hard drive has following characteristics:
Name : Mac HD
Type : Volume
Disk Identifier : disk0s3
Mount Point : /
File System : Mac OS Extended (Journaled)
Connection Bus : ATA
Partition Type : Apple_HFS
Device Tree : sata/k2-sata@0/@0:3
Writable : Yes
Universal Unique Identifier : 9AFCA71A-DD8B-376E-9776-EE7EDDBB328C
Capacity : 148,9 GB (159.907.627.008 Bytes)
Free Space : 96,9 GB (103.996.362.752 Bytes)
Used : 52,1 GB (55.911.264.256 Bytes)
Number of Files : 419.419
Number of Folders : 104.321
Owners Enabled : Yes
Can Turn Owners Off : Yes
Can Repair Permissions : Yes
Can Be Verified : Yes
Can Be Repaired : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : Yes
S.M.A.R.T. Status : Verified
Disk Number : 0
Partition Number : 3
The target drive characteristics:
Name : Porche_LaCie
Type : Volume
Disk Identifier : disk1s1
Mount Point : /Volumes/Porche_LaCie
File System : Mac OS Extended (Case-sensitive, Journaled)
Connection Bus : FireWire
Partition Type : Apple_HFS
Device Tree : fw/node@d04b7417066788/sbp-2@c000/@0:1
Writable : Yes
Universal Unique Identifier : BCCEBED2-08F5-3C21-8750-75716AF060B9
Capacity : 232,9 GB (250.056.705.024 Bytes)
Free Space : 160,8 GB (172.646.076.416 Bytes)
Used : 72,1 GB (77.410.627.584 Bytes)
Number of Files : 15
Number of Folders : 4
Owners Enabled : No
Can Turn Owners Off : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : Yes
S.M.A.R.T. Status : Not Supported
Disk Number : 1
Partition Number : 1
The target drive already contains 3 earlier images. The biggest image has a size of 28,14 GB. And as you can see this drive ha enough place for other images.
So what is going wrong?
I Googled for this error -39 without any success and I have not found any thing about this particular error in Apple's discussions or support pages.
I would feel a lot safer with a decent image of my Hard Drive. I already lost one and do not want to repeat this again...
Can any one help?

If you want to create a backup of your system volume, then do not use disc images. They are not bootable. Here's a far better solution:
How to Clone Using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the backup or destination volume from the left side list.
3. Click on the Erase tab in the DU main window. Set the format type to Mac OS Extended (journaled, if available) and click on the Erase button. This step can be skipped if the destination has already been freshly erased.
4. Click on the Restore tab in the DU main window.
5. Select the backup or destination volume from the left side list and drag it to the Destination entry field.
6. Select the startup or source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
You can also do the same using other backup utilities that can create bootable backups:
Backup Software Recommendations
My personal recommendations are (order is not significant):
1. Retrospect Desktop (Commercial - not yet universal binary)
2. Synchronize! Pro X (Commercial)
3. Synk (Backup, Standard, or Pro)
4. Deja Vu (Shareware)
5. Carbon Copy Cloner (Donationware)
6. SuperDuper! (Commercial)
7. Intego Personal Backup (Commercial)
8. Data Backup (Commercial)
Also read How to Back Up and Restore Your Files.

Disk Utility Unable to Repair External FireWire Hard Disk

Hello all.
This is the External FireWire Hard Disk that has been giving me problems for days, it is a Backup/Clone Disk of my sis's Mac mini Core Duo, and may explain why it was so hard and took so much pain to copy some of the data out, at times it failed to mount, and I manage to rescue some data after using Disk Warrior, but Disk Warrior was also unable to replace it with a new directory.
Anyway, so I (was able to) mount the hard disk, and I was successful in erase and reformating it.
But when I (try to) repair it with Disk Utility's First Aid, this report is what I get:
(The usual 'Checking...' text lines, text in BOLD indicates RED colour text)
Checking HFS Plus volume
Checking Extents Overflow file
Checking Catalog file
Checking Catalog hierarchy
Checking volume bitmap
Volume Bit Map needs minor repair
Checking volume information
The volume Untitled could not be repaired after 3 attempts
Error: The underlying task reported failure on exit
1 HFS volume checked
1 volume could not be repaired because of an error
Repair attempted on 1 volume
1 volume could not be repaired
Then a window dropped down from the top says:
First Aid failed
Disk Utility stopped repairing "Untitled" because the following error was encountered:
The underlying task reported failure on exit
(OK Button)
I guess this hard disk is really a gone case?? I am quite OK just to replace it with a brand new one... maybe all the trouble I had in the beginning is because I may already have a faulty backup drive to begin with???
Thanks and cheers

Hi Kappy,
I knew there was something about "not mixing" PPC and Intel versions of dealing with the external drive.
The drive was originally prepared on an Intel Mac mini Core Duo. But it should also mount normally on a PPC mac as an external hard drive right?
Here's the sequence of events:
1. Tried to boot from the Back Up/Clone Drive of the Mac mini Core Duo, through my MacBook Core 2 Duo, but failed to boot up
I had to shut down the MacBook (prolonged Bluescreen)
2. When I reboot the MacBook, and tried to mount the ext drive as normal, nothing happens, I knew something was wrong
3. Able to reach the vendor, use the Mac mini again to erase and reformat the drive, then check with DU, everything is OK
Clone with SuperDuper
After that check again with DU, not everything is alright, there are errors.
4. Brought the drive home, try to mount on my iMac G5, nothing happens.
I did a check on this forum, and the reply was that I should be able to use Disk Warrior 4 (Universal) on a PPC to fix an Intel-based ext drive. I was very specific and detail in my post/question
5. So anyway, I have no other option, I ran Disk Warrior 4 from my PPC iMac G5 and scan the ext drive, trying to fix it.
It reported the drive is too damaged to be replace with a new Directory, but gave me a Preview Mode. I use this to copy some data out.
But not sure if the data is OK or not.
6. After that, I was able to mount the drive in my iMac G5, so I just use DU and erase and reformat the drive, with Zero Data
7. Ran DU again, and that's where I am now, at the very first post, getting error messages that I cannot fix the drive
Thanks and cheers

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.

Unable to clone HD in Disk Utility

Similar Messages

Maybe you are looking for