SuperDuper! fails to enable ownership

[Nighthawk4]

I have just upgraded from Leopard to Snow Leopard on my iMac.

The way I did this was using SuperDuper. I backed up the internal disk (Leopard) to a volume on an external USB disk. Then I rebooted using that external volume (SuperDuper makes the backup volumes bootable). I ran the install process on the Snow Leopard CD to upgrade that external volume to Snow Leopard, using the complete replacement method. Then I reinstalled the Applications I needed and copied the data from the old installation - so I had a complete new installation of Snow Leopard - but on an external disk.

Having tested to ensure all worked correctly on that, I then erased the original disk and reformatted it, then used SuperDuper again to copy all files from the external disk to the new partition on the internal one. So my internal disk now has a new installation of Snow Leopard, including the Applications and data.

The system boots correctly with no errors and the Applications all seem to be working. The whole thing is so much faster than it used to be. Time Machine has backed up the new volume several times and (as far as I can tell) seems to have completed.

The only problem is that SuperDuper now fails to back up the new volume. It says it failed to enable ownership of the drive.

I tried to repair permissions in Disk Utility (booted off the Snow Leopard CD) and got this error:

**********
2009-12-30 09:33:29 +0000: Disk Utility started.

2009-12-30 09:33:36 +0000: Repairing permissions for “Macintosh HD”
2009-12-30 09:38:30 +0000: Permissions differ on "usr/share/derby", should be drwxr-xr-x , they are lrwxr-xr-x .
2009-12-30 09:38:31 +0000: Repaired "usr/share/derby".
2009-12-30 09:39:01 +0000: Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent" has been modified and will not be repaired.
2009-12-30 09:40:45 +0000:
2009-12-30 09:40:46 +0000: Permissions repair complete
2009-12-30 09:40:46 +0000:
2009-12-30 09:40:46 +0000:


Is there any way to repair the SUID file please?

All of this was done on the same machine by the same user, so I would have thought all rights would have been the same. Clearly I am missing something.

Any ideas please? I really don't want to have to reinstall as apart from this everything seems to be working fine.


Edit - the external volumes do seem to backup successfully - so they do not seem to have this error. The copy process would not have worked if that had not been the case. Only the internal disk seems to have this error.

 

[bobtomay]

There is nothing wrong with your machine.

That is a typical message and is of no concern. That ARDAgent has been the first to appear after a clean install since Leopard came out. There are more messages that can be ignored and can be found here.

It would be nice if Apple would take care of those instead of letting them linger around.

 

[Nighthawk4]

Thanks to Google I found this:

Repairing Permissions and ARDAgent - Mac Forums

I will try deleting the folder and then see if it repairs.

 

[Nighthawk4]

Thanks bobtomay. That makes me feel a lot better.

I still need to resolve the problem if possible so that SuperDuper will backup the new installation. I prefer not to rely solely on Time Machine for this.

Is there a log created by Time Machine, so I can verify it has worked please? It doesn't report any errors, but still like to be sure.

 

[bobtomay]

That particular error in repair permissions would have nothing to do with ownership of the drive for SuperDuper!, so still no reason to do anything about that.

Have to head out to work, so I'll do some checking a little later and see if I can find something for you. We have quite a few SD! users here, so maybe someone else will chime in also.

Will change title of your thread also - get those guys looking.

 

[bobtomay]

Nighthawk, just a thought before I get outta here, one thing you might try, uninstall SD! and then reinstall it.

 

[Nighthawk4]

I fixed the ARDAgent problem by setting the permissions manually to Read & Write, then the Disk Utility corrected them.

I also fixed the SUID error - with advice from SuperDuper! support - by running this:

sudo update_dyld_shared_cache -force

in Terminal.

SuperDuper! is a terrific product - and it seems their After Sales Support is just as good. Thanks guys. Now running SuperDuper! to back up my new installation.

Only Bootcamp to go - although with a combination of Snow Leopard and the latest Parallels I am not sure if I need to bother with that.

 

[bobtomay]

I fixed the ARDAgent problem by setting the permissions manually to Read & Write, then the Disk Utility corrected them.

I also fixed the SUID error - with advice from SuperDuper! support - by running this sudo update_dyld_shared_cache -force in Terminal.

SuperDuper! is a terrific product - and it seems their After Sales Support is just as good. Thanks guys. Now running SuperDuper! to back up my new installation.

Only Bootcamp to go - although with a combination of Snow Leopard and the latest Parallels I am not sure if I need to bother with that.

Part of the reason a lot of us recommend SD!.

So, fixing the SUID error is what it took to get SD! working again?



I BootCamped my Win7 install, although I use it in VMWare, just in case I want to install a game down the road.

 

[Nighthawk4]

Correct - fixing the SUID error enabled SD! to work correctly again.


Can I install 64-bit Win7 directly into Bootcamp or do I have to install XP and then upgrade in Windows? The Bootcamp instructions I downloaded and printed do not mention Win7.

I am fairly sure my iMac will take Win7 and I think it should take the 64-bit version now I have Snow Leopard installed.


Edit - Sorry Bob, the Forum says I can't give you any more Reputation boost until I spread it around elsewhere

 

[Nighthawk4]

Well it seems that the 64-bit version of Windows7 is NOT supported on my iMac.

Although I am sure the Apple Support Site said it was, after I had installed Windows7 and booted the Snow Leopard CD, it said i64 is not supported on this machine.

So I will stick with a VM in Parallels 5, which certainly does support the 64-bit version of Windows7 on the same machine.

Also, my main disk now has 32GB more space available for Mac stuff, as I deleted the Windows partition.



Incidentally, I discovered one small piece of information which may seem odd. The Bootcamp partition created by Leopard as '32GB' is not quite the same size as the one created by Snow Leopard. When I tried to use Winclone to restore my backup from the Leopard Windows partition, it was too big to fit in the new partition created by Snow Leopard - despite choosing the default 'make it 32 GB' in each case.

So I erased and recreated the partition, using iPartition - making it a little larger this time - and Winclone said 'No Windows partition found'. The new partition was formatted as FAT32 and the backup is readable, as Winclone could mount it in Snow Leopard. Presumably this means that Winclone can only restore into a functioning Windows partition - which seems to defeat the object as far as I can see. Disappointing.