Disk Utility problem after cloning

[macWish]

Originally Posted by dnanian

You should be able to see what file is actually 'open' on the volume using lsof. Try the following:

- Boot from the clone
- Open Terminal
- Use the command:

lsof | grep "internal-volume-name"

That should tell you who/what is holding the drive open...

It looks as if there are a lot of files on the internal hard drive that are open when I boot from the clone. I have attached the Terminal output text file of
lsof | grep "internal-volume-name". This seems to be a problem unique to Tiger as it never happened with the OS 10.3.9 and earlier versions.

[dnanian]

Given that, are you sure you're not running from a Safety Clone, as opposed to a full "Backup - all files" clone?

If not, try naming the backup the *same* as the internal drive, smart update it, and then boot from it. (I explain elsewhere on the forums about aliases resolving using the volume name...)

[macWish]

Originally Posted by dnanian

Given that, are you sure you're not running from a Safety Clone, as opposed to a full "Backup - all files" clone?

If not, try naming the backup the *same* as the internal drive, smart update it, and then boot from it. (I explain elsewhere on the forums about aliases resolving using the volume name...)

My startup disk is a Safety clone. I also have a "Backup - all files" clone. WHen I startup from the full clone, I get the same error with Disk Utility and Disk Warrior run from the startup disk. Since Disk Utility is not aliased to the internal drive on either the Safety clone or the full clone, it should not be aliasing the DU on the internal drive. The same problem occurs with the eDrive cloned by Techtool Pro.

For reasons beyond me, only my internal drive shows up on the desktop. None of the partitions on the external fire drive show up on the desktop. I did not realize they were not there because I have Finder Preferences set not to show the disks on the desktop since I can access them via DragThing or via a Finder Folder where they all show up. The desktop appears to be only place I can try to rename the Safety Clone, short of recloning it with same name as internal drive, if SuperDuper allows that.

For what it is worth, I attached the output of open files when I booted from the Full Clone. It is much smaller.

[dnanian]

Well, the Safety Clone is always going to have a lot of files opened on the original drive, because those items are shared. So that's normal.

But, the "Full Clone" is likely doing this because it's not named the same as the original "Macintosh HD" -- try that, Smart Update it, and I think it'll be resolved.

Disk Utility/Disk Warrior aren't causing the problems as such -- these other items that have auto-started on you are... and those are starting from the original drive, due to the naming & aliases (these are internally stored aliases, not ones you create yourself).

I can't explain the eDrive because I don't know how exactly they do what they do... sorry.

[macWish]

But why did this problem appear with Tiger when it did not exist in Panther?

[dnanian]

I can't answer that: it should have happened and both, and does in our testing...

[macWish]

I renamed a partition on external drive the same as the internal HD and did a full backup-all files. I then booted from the Full Clone. Disk Utility still unable to unmount the internal hd. Assuming that there are no other problems than this unmounting one, I will not try any other work arounds at the moment. When I do want to repair the disk on the internal hard drive, I'll do it in single user mode with AppleJack.

Now with OS X 10.4.1 released this morning, the process may start all over, all nothing in the news of the update mentions this problem and I have yet to hear back from my bug report to Apple.