View Full Version : Clone Failing

Movable Beast
10-29-2006, 02:13 PM
After having tremendous success with SuperDuper! on a number of small servers that I've set up for my clients, I decided to replace my old backup solution with SD! The server I'm working on runs iTools 7.5 on Mac OS X 10.3.8 and has a lot of files packed onto an 80 GB drive with about 23 GB available. I'm trying to clone the boot drive to another 80 GB drive, but every time I try the backup is failing when only about 65,000 - 67,000 of the files (or about 3.61 GB) out of 1,163,517 files getting copied. The symptom is the same every time - the backup progresses very slowly until it gets to this point, then the count of files evaluated stops and the copy stops. If I don't Stop the backup, things get progressively slower until I am forced to reboot the machine (it's remote, so I have to use my hosting provider's control panel to power down and then power up again). I've tried the standard scripts as well as a script I created to clone just the /Library/Tenon folder and it fails at about the same point every time.

Any ideas?


10-29-2006, 05:42 PM
Well, the proximity to 4GB makes me think that you're backing up to an image. True?

Movable Beast
10-29-2006, 11:15 PM
No, to an external 80GB drive. However, I'm trying a disk image on that drive right now to see if that will work...


About 10 minutes later -->

SD! won't create a disk image on the backup drive. Here's the message I'm seeing in the log:

| 09:20:59 PM | Info | SuperDuper!, 2.1.3 (80), path: /Applications/SuperDuper!.app, Mac OS 10.3.9 build 7W98 (ppc)
| 09:20:59 PM | Info | Started on Sun, Oct 29, 2006 at 9:20 PM
| 09:20:59 PM | Info | Source Drive: Server One, mount: /, device: ST9808210A, interconnect: Internal ATA, file system: "Journaled HFS+", OS: 10.3.9 (7W98), capacity: 74.41 GB, used: 51.33 GB, directories: 79992, files: 1163390, ejectable: NO, ACLs: Disabled
| 09:20:59 PM | Info | Target Image: /Volumes/Server One Backup/Backup.sparseimage, name: Backup
| 09:20:59 PM | Info | Copy Mode : Erase, then copy files
| 09:20:59 PM | Info | Copy Script : Backup - all files.dset
| 09:20:59 PM | Info | Transcript : BuildTranscript.plist
| 09:20:59 PM | Info | PHASE: 1. Prepare to Copy Files
| 09:20:59 PM | Info | ...ACTION: Preparing Server One
| 09:20:59 PM | Info | ......COMMAND => Verifying the integrity of volinfo.database
| 09:21:00 PM | Info |
volinfo.database OK
| 09:21:00 PM | Info | ......COMMAND => Enabling permissions on Server One
| 09:21:00 PM | Info | Refreshing Disk Arbitration ...
| 09:21:03 PM | Info | ......COMMAND => Verifying that permissions are enabled for Server One
| 09:21:03 PM | Info | Permissions on '/' are enabled.
| 09:21:03 PM | Info | ...ACTION: Mounting Backup
| 09:21:03 PM | Info | ......COMMAND => Preparing Backup
| 09:21:04 PM | Info | Initializing...
| 09:21:04 PM | Info | Creating...
| 09:21:04 PM | Info | Finishing...hdiutil: create failed - Invalid argument
| 09:21:04 PM | Error | ****FAILED****: result=256 errno=0 (Unknown error: 0)


10-30-2006, 08:20 AM
Yeah, known issue, but don't use an image if you can write directly to the drive.

OK -- so, slows down and isn't an image. Any AntiVirus? Anything else on FireWire with the drive? What specific brand/model of drive is it?

I could also really use the log from the failed runs... might be easier to do this in email since it's unlikely the diagnostic process will help other users, but, of course, it's up to you.

Movable Beast
11-02-2006, 06:21 PM
Hi, Dave - and thanks for all of the help!

I have no antivirus running on this machine. There's only the one drive on Firewire and no other FW devices at all. Here's the info about the target drive:


Capacity: 74.53 GB
Manufacturer: Oxford Semiconductor Ltd.
Model: OXFORD IDE Device LUN 0
Removable Media: No
Detachable Drive: Yes
BSD Name: disk1
OS9 Drivers: No
Speed: 400 Mb/sec Speed
Unit Spec Id: 24734
Firmware Revision: MO4O
Unit Software Version: 10483

Server One Backup:

Capacity: 74.41 GB
Available: 73.95 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk1s3
Mount Point: /Volumes/Server One Backup

I will send a log file to you shortly. I did go in with Disk Utility and actually had to repair this volume, so I'm trying the backup again. If that ends up fixing the problem I'll kick myself! :p


Movable Beast
11-02-2006, 09:19 PM
Well, that didn't work. Again, the disk copy got to about 4 GB and died, locking up the server. I had to power it down to start things up again. The log file is on its way, although I'm not sure what it will include since I had to "ungracefully" power down the server and start up again.


11-02-2006, 09:20 PM
You've got some kind of hardware problem going on here, Steve...