Shirt Pocket Discussions

Shirt Pocket Discussions (https://www.shirt-pocket.com/forums/index.php)
-   General (https://www.shirt-pocket.com/forums/forumdisplay.php?f=6)
-   -   Error Halted Backup! (https://www.shirt-pocket.com/forums/showthread.php?t=663)

GadgetFan 09-06-2005 11:35 PM

Error Halted Backup!
 
Error Halted Backup!

I am a Mac newbie (a recent switcher), using SuperDuper as an aid to upgrading my Mac mini to Tiger. I have run into a permissions error and am stuck. I'd appreciate any help!

What has worked great so far:
* Installed SuperDuper on Panther on my internal drive (Macintosh HD)
* Backup - all files, Erase and backup completed to two external firewire partitions (belt and suspenders). These boot fine.
* Did an Erase and Install of Tiger to _another_ external firewire partition (called Sandbox), then used Migrate to pull over my stuff from Macintosh HD (the old Panther drive).
* Tested and configured the new Tiger installation, booting from Sandbox, for a few days. All is well so now I want to clone back to Macintosh HD.

What does not work:
*Booted from Sandbox (Tiger)
* Set SuperDuper to Backup - All files to Macintosh HD; Erase , then Copy (overkill, compared to Smart Copy?) on the theory I shouldn't have to do a defrag any time soon. This is where things don't work. Cloning Sandbox to Macintosh HD has failed twice with the message: "An error occurred that halted execution." The specific error message from the log each time is:

|07:47:01 PM|Info| ......COMMAND => Verifying that permissions are enabled for Macintosh HD
|07:47:01 PM|Error| Could not disable Ignore Permissions

The first time this occurred before the Erase Macintosh HD step. I looked at info and decided for some reason to unlock the little lock beside Owner: system. Ran SuperDuper again and got the same error, but not until _after_ Macintosh HD was erased. (I am not panicked, because the Tiger partitions and two old Panther partitions are still here. But I want to be able to boot from my (now empty) internal drive.)

Macintosh HD shows Owner: system, Group: suzanne, and that my access and group access is Read only. (I am suzanne, but maybe I am not now the _same_ suzanne that used to be referenced on this drive?)

I am doing all this from my Tiger user account on Sandbox. I am an administrator.

On Sandbox, I have read and write permission, System is owner, and my group (admin) can read and write.

Do I make the ownership and permissions on Macintosh HD the same as those as on Sandbox, to be able to proceed? If so, how? Edit them in Get Info? Repartition Macintosh HD and try again? Also, what did I do wrong to begin with?

The complete log entries are below in case they help. Thanks!

__________________________________________________ _________
[***] Tuesday, September 06, 2005 07:12:14 PM US/Pacific
|07:12:14 PM|Info| SuperDuper!, version 74, path: /Applications/SuperDuper!.app, OS: 10.4.2 (8C46)
|07:12:14 PM|Info| Source Drive: /, name: Sandbox, device: /dev/disk2s5 type: hfs, OS: 10.4.2 (8C46), capacity: 74.38 GB, used: 67.06 GB, directories: 78410, files: 329850
|07:12:14 PM|Info| Target Drive: /Volumes/Macintosh HD, name: Macintosh HD, device: /dev/disk0s3 type: hfs, OS: 10.3.9 (7W98), capacity: 74.41 GB, used: 64.26 GB, directories: 52624, files: 230879
|07:12:14 PM|Info| Copy Mode : Erase, then copy files
|07:12:14 PM|Info| Copy Script : Backup - all files.dset
|07:12:14 PM|Info| Transcript : BuildTranscript.plist
|07:12:14 PM|Info| PHASE: Volume Preparation
|07:12:14 PM|Info| ...ACTION: Repair Permissions on Sandbox
|07:12:14 PM|Info| ......COMMAND => Repairing permissions on Sandbox
|07:12:20 PM|Info| parent directory ./Users/Shared/SC Info does not exist
|07:12:58 PM|Info| Started verify/repair permissions on disk disk2s5 Sandbox
|07:12:58 PM|Info| Determining correct file permissions.
|07:12:58 PM|Info| We are using special permissions for the file or directory ./Library/Widgets. New permissions are 16877
|07:12:58 PM|Info| We are using special permissions for the file or directory ./usr/lib/php/build/acinclude.m4. New permissions are 33060
|07:12:58 PM|Info| The privileges have been verified or repaired on the selected volume
|07:12:58 PM|Info| Verify/repair finished permissions on disk disk2s5 Sandbox
|07:12:58 PM|Info| ...ACTION: Erase Macintosh HD
|07:12:58 PM|Info| ......COMMAND => Erasing Macintosh HD
|07:13:08 PM|Info| Journaling has been enabled on /dev/disk0s3
|07:13:08 PM|Info| ......COMMAND => Restoring Macintosh HD UUID (A03F11D9A51D000D)
|07:13:08 PM|Info| ...ACTION: Enable Permissions
|07:13:08 PM|Info| ......COMMAND => Enabling permissions on Sandbox
|07:13:08 PM|Info| Refreshing Disk Arbitration ...
|07:13:08 PM|Info| ......COMMAND => Verifying that permissions are enabled for Sandbox
|07:13:08 PM|Info| Permissions on '/' are enabled.
|07:13:08 PM|Info| ......COMMAND => Enabling permissions on Macintosh HD
|07:13:08 PM|Info| Refreshing Disk Arbitration ...
|07:13:08 PM|Info| ......COMMAND => Verifying that permissions are enabled for Macintosh HD
|07:13:08 PM|Error| Could not disable Ignore Permissions
[***] Tuesday, September 06, 2005 07:46:51 PM US/Pacific
|07:46:51 PM|Info| SuperDuper!, version 74, path: /Applications/SuperDuper!.app, OS: 10.4.2 (8C46)
|07:46:51 PM|Info| Source Drive: /, name: Sandbox, device: /dev/disk2s5 type: hfs, OS: 10.4.2 (8C46), capacity: 74.38 GB, used: 67.06 GB, directories: 78410, files: 329852
|07:46:51 PM|Info| Target Drive: /Volumes/Macintosh HD, name: Macintosh HD, device: /dev/disk0s3 type: hfs, OS: 10.3.9 (7W98), capacity: 74.41 GB, used: 0.04 GB, directories: 4, files: 9
|07:46:51 PM|Info| Copy Mode : Erase, then copy files
|07:46:51 PM|Info| Copy Script : Backup - all files.dset
|07:46:51 PM|Info| Transcript : BuildTranscript.plist
|07:46:51 PM|Info| PHASE: Volume Preparation
|07:46:51 PM|Info| ...ACTION: Erase Macintosh HD
|07:46:51 PM|Info| ......COMMAND => Erasing Macintosh HD
|07:47:01 PM|Info| Journaling has been enabled on /dev/disk0s3
|07:47:01 PM|Info| ......COMMAND => Restoring Macintosh HD UUID (A03F11D9A51D000D)
|07:47:01 PM|Info| ...ACTION: Enable Permissions
|07:47:01 PM|Info| ......COMMAND => Enabling permissions on Sandbox
|07:47:01 PM|Info| Refreshing Disk Arbitration ...
|07:47:01 PM|Info| ......COMMAND => Verifying that permissions are enabled for Sandbox
|07:47:01 PM|Info| Permissions on '/' are enabled.
|07:47:01 PM|Info| ......COMMAND => Enabling permissions on Macintosh HD
|07:47:01 PM|Info| Refreshing Disk Arbitration ...
|07:47:01 PM|Info| ......COMMAND => Verifying that permissions are enabled for Macintosh HD
|07:47:01 PM|Error| Could not disable Ignore Permissions

GadgetFan 09-07-2005 02:45 AM

Tested one of my theories, and still fails the same way. I hope for sage advice tomorrow!

*couldn't change permissions on Macintosh HD, so I used Disk Uitlity to Erase it. Then I could change permissions in Get Info, so I tried setting it just like the other working (external) boot drives, namely:
You can: Read & Write
Owner: system, Read and Write
Group: admin, Read and write
Others: Read only

logged out and in again, holding down shift.
re-ran SuperDuper Again. Failed again, same as before.

Checked and SuperDuper had also re-set the permissions on Macintosh HD back where there were before:
You can: Read only
Owner: system, Read and Write
Group: suzanne, Read only
Others: Read only

Log follows:
[***] Tuesday, September 06, 2005 11:35:47 PM US/Pacific
|11:35:47 PM|Info| SuperDuper!, version 74, path: /Applications/SuperDuper!.app, OS: 10.4.2 (8C46)
|11:35:47 PM|Info| Source Drive: /, name: Sandbox, device: /dev/disk2s5 type: hfs, OS: 10.4.2 (8C46), capacity: 74.38 GB, used: 67.06 GB, directories: 78410, files: 329926
|11:35:47 PM|Info| Target Drive: /Volumes/Macintosh HD, name: Macintosh HD, device: /dev/disk0s3 type: hfs, OS: N/A, capacity: 74.41 GB, used: 0.04 GB, directories: 4, files: 10
|11:35:47 PM|Info| Copy Mode : Erase, then copy files
|11:35:47 PM|Info| Copy Script : Backup - all files.dset
|11:35:47 PM|Info| Transcript : BuildTranscript.plist
|11:35:48 PM|Info| PHASE: Volume Preparation
|11:35:48 PM|Info| ...ACTION: Repair Permissions on Sandbox
|11:35:48 PM|Info| ......COMMAND => Repairing permissions on Sandbox
|11:35:53 PM|Info| parent directory ./Users/Shared/SC Info does not exist
|11:36:27 PM|Info| Started verify/repair permissions on disk disk2s5 Sandbox
|11:36:27 PM|Info| Determining correct file permissions.
|11:36:27 PM|Info| We are using special permissions for the file or directory ./Library/Widgets. New permissions are 16877
|11:36:27 PM|Info| We are using special permissions for the file or directory ./usr/lib/php/build/acinclude.m4. New permissions are 33060
|11:36:27 PM|Info| The privileges have been verified or repaired on the selected volume
|11:36:27 PM|Info| Verify/repair finished permissions on disk disk2s5 Sandbox
|11:36:27 PM|Info| ...ACTION: Erase Macintosh HD
|11:36:27 PM|Info| ......COMMAND => Erasing Macintosh HD
|11:36:37 PM|Info| Journaling has been enabled on /dev/disk0s3
|11:36:37 PM|Info| ......COMMAND => Restoring Macintosh HD UUID (471053F3C7F67DB9)
|11:36:37 PM|Info| ...ACTION: Enable Permissions
|11:36:37 PM|Info| ......COMMAND => Enabling permissions on Sandbox
|11:36:37 PM|Info| Refreshing Disk Arbitration ...
|11:36:37 PM|Info| ......COMMAND => Verifying that permissions are enabled for Sandbox
|11:36:37 PM|Info| Permissions on '/' are enabled.
|11:36:37 PM|Info| ......COMMAND => Enabling permissions on Macintosh HD
|11:36:37 PM|Info| Refreshing Disk Arbitration ...
|11:36:37 PM|Info| ......COMMAND => Verifying that permissions are enabled for Macintosh HD
|11:36:37 PM|Error| Could not disable Ignore Permissions

GadgetFan 09-07-2005 02:58 AM

Tried one more time.

I used Disk Utility to re-partition Macintosh HD. Still one partition, still the same name. That did something else yet again with owner and permissions, but at least I owned the disk and had rights.

However, SuperDuper fails with the same error of being "unable to disable Ignore Permissions".

dnanian 09-07-2005 08:12 AM

Hi, GadgetFan. Sorry that I didn't catch you early enough to have you avoid doing all that extra work.

In any case, you'll find this exact problem dealt with in this FAQ. Hope that helps!

GadgetFan 09-07-2005 12:08 PM

Thanks for the info. I will try it in a minute.

But first, please tell me this. I assume this is someting I must do after _any_ Tiger installation, including an Erase and Install, since that is what I did. I did not do an "upgrade". (I assume the FAQ means "upgrade" only in the sense that Tiger is better than previous versions of OS X. Or does it have something to do with there having been multiple boot disks on this machine already?)

So should someone with a new Mac with Tiger pre-installed also follow this step before using SuperDuper?

Thanks!

dnanian 09-07-2005 12:16 PM

That's right. I don't know if the pre-load has the problem too, but the issue is that the Tiger installer misformats this file, and forgets to put a carriage return in it between two lines.

That causes the other tools that deal with Ownership to misread the file... and therein lies the problem.

Erasing it avoids the issue because it's post-install... and the tools in Tiger itself are fine.

You need only take this step if you get the error, though. And, once fixed, it should be fine unless you reinstall.

GadgetFan 09-07-2005 01:01 PM

Thanks!

I am using this as a learning opportunity, since that's one of my reasons for switching to the Mac anyway. (I'm also switching friends and relatives, and I want to get them using SuperDuper so I want to understand what to tell them about it.)

So here's another peripherally related question, if you don't mind.

Last night right after my posts I went ahead and installed Tiger fresh on my Macintosh HD drive, since it was erased anyway. (I wanted to see how the permissions looked, etc.) And I did the software updates. If I go ahead and use Migration Assistant to get my stuff back over from Sandbox, I think I will have two virtually identical Tiger partitions. What will the differences be?

I realize I could skip this and clone back the rest, now that I know the trick. I'm just wanting to know if there is much difference in the outcome, e.g. saving me steps after I migrate. Migrate won't move everything, and neither will Sandbox. Are those lists the same?

Thanks again!

SuperDuper! is great, by the way. Other than this permissions surprise it has been slick as a whistle. I am embarrassed I didn't see the FAQ entry. I thought I had looked. Obviously I didn't, or I was more tired than I thought.

dnanian 09-07-2005 01:20 PM

You *cannot* get your stuff from a Sandbox if that was created with the Safety Clone scripts. Don't try! It'll get really screwed up.

Instead, you'd migrate from the original volume.

And, honestly, I don't know what all the differences might be between a migrated volume and the original... it's different for every setup!

GadgetFan 09-07-2005 07:07 PM

Thanks for the warning. It is just _named_ Sandbox, though. It is the clean, full Tiger install I described earlier.

dnanian 09-07-2005 07:14 PM

OK, good. Don't want to see data loss here! :)

GadgetFan 09-09-2005 02:56 PM

Just FYI, Miration Assistant wouldn't work. It just did the spinning beachball forever while looking for Users to import from my firewire Tiger partition. Maybe it is a problem with importing from another Tiger install, maybe not.

However, once I performed the permissions fix above, I was able to clone back to the internal drive just fine.

Thanks.

dnanian 09-09-2005 05:11 PM

That's strange: it certainly should have allowed you to -- I've done this a number of times. How long did you leave it?

GadgetFan 09-09-2005 07:56 PM

The first time, I think I left it a long time, i.e. hours. It would let me select which drive, but not which User; it would stall trying to bring up a list. I did the permissions correction you described, on the theory it couldn't hurt, and rebooted. I tried again, and I think I let it go for about 15-30 minutes. Even 5 minutes would be silly, I think.

When I used Migrate to move from my Panther setup to the newly installed Tiger, I don't remember how long it took to identify the list of Users and let me pick, but I think that's because it was nothing untoward.

dnanian 09-09-2005 08:46 PM

Well, weird. I don't know why it didn't work for you!


All times are GMT -4. The time now is 05:37 PM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2024, vBulletin Solutions, Inc.