failed to enable ownership
 

I'm running into a problem...

I wanted to transfer my Snow Leopard install to a different drive. I successfully used SD! to clone my startup drive to a different internal drive (that has been in use for quite a while successfully). I had no problem starting (booting) off the new drive.

I then went to backup (clone) using SD! the new drive. Upon starting SD!, I got an error message "failed to enable ownership." Here's the log:

| 06:06:38 PM | Info | SuperDuper!, 2.6.2 (87), path: /Applications/$Misc Utils/$Backup Utils/SuperDuper!/SuperDuper!.app, Mac OS 10.6.2 build 10C540 (i386)
| 06:06:38 PM | Info | Started on Thu, Apr 29, 2010 at 6:06 PM
| 06:06:38 PM | Info | Source Volume: Snow Leopard, mount: /, device: /dev/disk0s3, media: WDC WD6400AAKS-00A7B0, interconnect: Internal SATA, file system: "Journaled HFS+", OS: 10.6.2 (10C540), capacity: 232.11 GB, used: 56.94 GB, directories: 189581, files: 818376, ejectable: NO, ACLs: Enabled
| 06:06:38 PM | Info | Target Volume: Snow Leopard BU, mount: /Volumes/Snow Leopard BU, device: /dev/disk4s2, media: ST340062 0AS, interconnect: External FireWire, file system: "Journaled HFS+", OS: 10.6.2 (10C540), capacity: 399.74 GB, used: 53.93 GB, directories: 187716, files: 810301, ejectable: YES, ACLs: Enabled
| 06:06:38 PM | Info | Copy Mode : Smart Update
| 06:06:38 PM | Info | Copy Script : Backup - all files.dset
| 06:06:38 PM | Info | Transcript : BuildTranscript.plist
| 06:06:38 PM | Info | PHASE: 1. Prepare to Copy Files
| 06:06:38 PM | Info | ...ACTION: Preparing Snow Leopard
| 06:06:38 PM | Info | ......COMMAND => Verifying the integrity of volinfo.database
| 06:06:38 PM | Error | sh: /usr/bin/grep: Permission denied

Any thoughts about what this might be due to?

Self-help info below...

I repaired permissions on the new volume and ran into a huge slew of them! (This didn't affect the SD error.) Seemed odd, since I had repaired permissions on the source drive as part of the cloning process. Then, I realized I had used smart backup to clone the source to the target, and the target was a Leopard volume while the source was a Snow Leopard volume. I'm now going to try an erase and copy from the source drive and see if that gets me farther.

Did you try repairing the source with Disk Warrior?

No, but what I DID do was to reclone using Erase and Copy vs. Smart Update, and that did the trick. Cloning a Snow Leopard volume to a Leopard target with Smart Update made something very unhappy!

Anyway, all's well that ends well. Thanks.