Sandbox/Disk Utility

[bill s]

What I meant was that when booted from Macintosh HD I got the same error message when attempting to verify Sandbox permissions. Macintosh HD permissions verify/repair are normal. I didn't do anything unusual. Just upgraded from new CD and downloaded & installed 10.4.2 combo update. Updated some application programs also similarly. Everything else seems normal.

[dnanian]

Searching around a bit with Google shows that this is a pretty common error when Disk Utility has a problem -- I don't think it has anything to do with SuperDuper! at all. Try running the following at a Terminal command prompt:

sudo diskutil repairPermissions /

When you do that, what output do you get?

[bill s]

Here is what I got.

Last login: Mon Sep 19 06:44:51 on ttyp1
Welcome to Darwin!
[ip68-100-12-211:~] juliusso% Started verify/repair permissions on disk disk1s5 Sandbox
tcsh: Started: Command not found.
Determining correct file permissions.
buffer overflow!
[ip68-100-12-211:~] juliusso% Determining correct file permissions.
tcsh: Determining: Command not found.
[ip68-100-12-211:~] juliusso% buffer overflow!
tcsh: buffer: Command not found.
[ip68-100-12-211:~] juliusso%

[dnanian]

Um: I don't think you did the right thing there, Bill. You want to copy and paste just this line:

sudo diskutil repairPermissions /

into Terminal. You seem to have copied and pasted something totally different -- the output from a repair permissions operation.

[bill s]

I thought that's what I did.
I just now did what you prescribed, copied & pasted:

Last login: Mon Sep 19 06:45:46 on ttyp1
Welcome to Darwin!
[ip68-100-12-211:~] juliusso%
[ip68-100-12-211:~] juliusso% sudo diskutil repairPermissions /
Password:
Started verify/repair permissions on disk disk1s5 Sandbox
Determining correct file permissions.
buffer overflow!

[dnanian]

OK, Bill.

The implication here is that you've got either a bad executable file or receipt, and that's what's causing the trouble. When the repair permissions part of OSX reads it, it gets confused and fails... and generates an error.

When the Disk Utility version sees this happen, it fails with that weird "disconnected" message. But the cause of that message is the failure of the underlying tool, and that cause of that is some file on your drive that's corrupted.

Figuring out what is going to be a challenge, though. We pretty much know it's not an OS executable or receipt, because it happens on both your upgraded sandbox and on your original drive (right?). So, it must be a 3rd party receipt or application.

The first thing I'd do to diagnose it would be to run Disk Utility or Disk Warrior on the drive and repair it. If that doesn't help, more radical steps will need to be taken.

[bill s]

Thanks Dave

I'll try to repair the disk. If not successful, I guess the best bet would be to erase Sandbox and reclone it. Then reinstall Tiger, etc. Do you agree?