PDA

View Full Version : "Failed to Enable Ownership" with Leopard


Drdul
10-27-2007, 08:51 PM
I upgraded my MacBook Pro to Leopard, set everything up all nice and spiffy, tried to create a sparse disk image on an external drive, and got this:

X Failed to enable ownership on MBP

Where "MBP" is the name of the hard drive in my MacBook Pro. I repaired permissions no luck. I logged in as administrator still no luck.

As a last resort, I connected a firewire external drive with a copy of my Tiger install, booted that, and launched SD. Syccess! I created a sparse disk image of MBP on the external drive with no problems.

I am assuming that this "failed to enable ownership" thing is a Leopard-specific glitch. If so, any idea as to when this can be resolved? Not that I'm in a hurry it's just that the availability of a SD upgrade is one of the factors that will determine when I upgrade my Mac Pro, which is my primary, mission-critical computer.

Thanks!

dnanian
10-27-2007, 09:26 PM
We're not yet compatible with Leopard, but I'd need to see the log from those runs to be able to tell what was going on.

Drdul
10-27-2007, 09:30 PM
Too late the logs are gone. When I'm finished doing some other "fun" stuff with the computer, I'll try to run SD again from the Leopard volume, and I'll post the log info. All I remember from the previous versions was that the last line in the log repeated the "failed to enable ownership" bit and suggested I restart the computer, which didn't fix the problem.

Cheers!

dnanian
10-27-2007, 09:35 PM
The logs shouldn't be gone: cmd+click the title bar of the log and choose the "logs" folder. Or, better, click "Send to shirt pocket" and send them all to me.

Drdul
10-28-2007, 05:26 AM
| 03:51:00 PM | Info | SuperDuper!, 2.1.4 (82), path: /Applications/SuperDuper!.app, Mac OS 10.5 build 9A581 (i386)
| 03:51:00 PM | Info | Started on Sat, Oct 27, 2007 at 3:51 PM
| 03:51:00 PM | Info | Source Volume: MBP, mount: /, device: /dev/disk0s2, media: FUJITSU MHW2160BHPL, interconnect: Internal SATA, file system: "Journaled HFS+", OS: 10.5 (9A581), capacity: 148.73 GB, used: 30.63 GB, directories: 127452, files: 556581, ejectable: NO, ACLs: Enabled
| 03:51:00 PM | Info | Target Image: /Volumes/External/Backup/MBP Image.sparseimage, name: MBP Image
| 03:51:00 PM | Info | Copy Mode : Erase, then copy files
| 03:51:00 PM | Info | Copy Script : Backup - exclude Movies.dset
| 03:51:00 PM | Info | Transcript : BuildTranscript.plist
| 03:51:00 PM | Info | PHASE: 1. Prepare to Copy Files
| 03:51:00 PM | Info | ...ACTION: Preparing MBP
| 03:51:00 PM | Info | ......COMMAND => Verifying the integrity of volinfo.database
| 03:51:00 PM | Info | volinfo.database OK
| 03:51:00 PM | Info | ......COMMAND => Enabling permissions on MBP
| 03:51:00 PM | Info | Refreshing Disk Arbitration ...
| 03:51:01 PM | Info | ......COMMAND => Verifying that permissions are enabled for MBP
| 03:51:01 PM | Error | Could not enable permissions for volume MBP : please restart your Macintosh

dnanian
10-28-2007, 10:08 AM
Did you restart your Mac?

Drdul
10-29-2007, 12:46 PM
Yes I did, and it didn't solve the problem.

dnanian
10-29-2007, 02:06 PM
OK. Please see the FAQ entry on this issue and follow the steps there to remove your 'volinfo.database'... but, before you remove it, please attach it to an email message to me at support...

Drdul
10-29-2007, 08:40 PM
I must be dense I can't find anything in the frequently asked questions forum to do with this issue (I even searched for "volinfo" with no luck). Can you point me towards the FAQ entry?

Thanks!

dnanian
10-29-2007, 08:59 PM
http://www.shirt-pocket.com/forums/showthread.php?t=318

Drdul
10-29-2007, 09:39 PM
Here's what's in volinfo.database (note that the first line is a blank line, which I assume is what's messing things up):

***begin volinfo.database***

7D824989959DAEA0: 00000001
7D824989959DAEA0: 00000001
7D824989959DAEA0: 00000001
7D824989959DAEA0: 00000001
7D824989959DAEA0: 00000001
7D824989959DAEA0: 00000001
***end volinfo.database***

After removing volinfo.database from /var/db, I ran SD, and it executed everything just fine.

BTW, is it my imagination, or is there really an extra quarter of a million files in Leopard? SD used to report just under 300,000 files for a backup, and now it reports around 550,000.

Cheers!

dnanian
10-29-2007, 09:45 PM
Actually, the blank line doesn't mess *us* up, but it does mess up the utility that sets ownership status, which is why there are so many repeats of the same value. Ugh, another OSX volinfo.database bug... lovely.