"Failed to enable ownership"
 

I was trying to upgrade my MacBook Intel Core HD (80GB) to a Western Digital 500GB one by following the instructions in this article (http://www.macworld.com/article/5806...upgrade.htmlHi). However I always got the "Failed to enable ownership" error when I tried to use SuperDuper (v2.4) copy my HD to the new one. It does not matter whether I chose "Backup -all files" or "Backup -user files". I also attempted to check off the "ignore owndership on this volume" option on the external drive, but it always reverted back to the unchecked state after SuperDuper failed. Please help! Thanks in advance!

| 02:25:07 PM | Info | Copy Mode : Erase, then copy files
| 02:25:07 PM | Info | Copy Script : Backup - all files.dset
| 02:25:07 PM | Info | Transcript : BuildTranscript.plist
| 02:25:08 PM | Info | PHASE: 1. Prepare to Copy Files
| 02:25:08 PM | Info | ...ACTION: Preparing Macintosh HD
| 02:25:08 PM | Info | ......COMMAND => Verifying the integrity of volinfo.database
| 02:25:08 PM | Info | volinfo.database OK
| 02:25:08 PM | Info | ......COMMAND => Enabling permissions on Macintosh HD
| 02:25:08 PM | Info | Refreshing Disk Arbitration ...
| 02:25:08 PM | Info | ......COMMAND => Verifying that permissions are enabled for Macintosh HD
| 02:25:08 PM | Info | Permissions on '/' are enabled.
| 02:25:08 PM | Info | ...ACTION: Erasing Untitled 1
| 02:25:08 PM | Info | ......COMMAND => Preserving Untitled 1 UUID
| 02:25:08 PM | Info | 438FA455D6F750AF
| 02:25:08 PM | Info | ......COMMAND => Preserving spotlight indexing state
| 02:25:08 PM | Info | ......COMMAND => Erasing Untitled 1
| 02:25:42 PM | Info | Could not unmount Untitled 1 for fast disk erase, defaulting to slower directory-by-directory erase...
| 02:25:42 PM | Info | ......COMMAND => Restoring Untitled 1 UUID (438FA455D6F750AF)
| 02:25:42 PM | Info | 438FA455D6F750AF
| 02:25:42 PM | Info | ......COMMAND => Restoring Spotlight search indexing state on Untitled 1
| 02:25:42 PM | Info | ...ACTION: Preparing Untitled 1
| 02:25:42 PM | Info | ......COMMAND => Enabling permissions on Untitled 1
| 02:25:42 PM | Info | Refreshing Disk Arbitration ...
| 02:25:42 PM | Info | ......COMMAND => Verifying that permissions are enabled for Untitled 1
| 02:25:42 PM | Info | Permissions on '/Volumes/Untitled 1' are enabled.
| 02:25:42 PM | Info | ......COMMAND => Verifying that Untitled 1 ACL support matches Macintosh HD
| 02:25:43 PM | Info | error (22) from /Volumes/Untitled 1. (Invalid argument)
| 02:25:43 PM | Error | ****FAILED****: result=5632 errno=22 (Unknown error: 0)

Restart your Mac, deanriver.

I did. It didn't work. Now when I plug in my external drive, my MacBook either wants to initialize it, in which case I get a permission denied error message, or recognizes the drive but I can not unamount it. It looks like my external drive is held hostage by some phantom program, even though it has nothing on it.

I don't know what that would be. But if it says it wants to "initialize" it, it's because it's not responding properly. Might be a defective drive.

it is possible that the failed clone has left the drive in an unreadable state...

try using disk utility to repartition the new drive... check the options in the repartition tab to make sure that the GUID partitioning scheme is selected...

it's a little counter-intuitive, but you can choose to repartition the drive as a single volume, you need to go through the partitioning process to check/set the correct partitioning scheme...

Thanks for all your help. I can't initialize the drive -- it will give me a "permission denied" message. Maybe the first partitioning attempt left it in an unreadable state? Are there other disk management tools other than Disk Utility that I can use to erase it and re-partition it? Maybe I can use a PC to format it then re-partition it using my MacBook?

I can't see how that could happen: a partition is a soft operation that just writes data to the drive. Perhaps you should try starting up from the Leopard DVD and partitioning from there.

i've seen some recent reports of people having trouble repartitioning in 10.5.5 and 10.5.6, but there are so many other variables that it's hard to know really...

if you have another machine available you may as well try to return the drive to some kind of sensible state by formatting on it first...