Hard drive repair "updating boot partitions for the volume as required"

On my machine, it happens almost instantaneously. Here are two examples:

+2010-07-18 19:05:01 -0700: Volume repair complete.+
+2010-07-18 19:05:01 -0700: Updating boot support partitions for the volume as required.+
+2010-07-18 19:05:02 -0700: Repair tool completed:+

+2010-08-22 13:42:24 -0700: Volume repair complete.+
+2010-08-22 13:42:24 -0700: Updating boot support partitions for the volume as required.+
+2010-08-22 13:42:24 -0700: Repair tool completed:+

This leads me to conclude that something's hosed on your machine. BTW, I use CCC to update multiple clones on a daily basis and get the same result, as above, so that's not causing your issue.

WZZZ wrote:
To test, I just let it go for a full hour. The message never disappeared.

I think I may have mislead you -- if you are looking in the 'details' text area of Disk Utility & have the "Show details" box checked, the message won't disappear. Assuming the repair completes without finding anything wrong, you will just see as the last three lines:

The volume <volume name> appears to be OK. (in green)
Volume repair complete.
Updating boot support partitions for the volume as required.

If you do not have the "Show details" box checked, you won't normally see the final 'updating' message at all.

What disappears in the Disk Utility user interface is the "Repairing Volume. Estimated time: xx minutes" text & the progress bar at the bottom of the window. When it does, you know the process is complete. If you try to quit Disk Utility before this, while the repair is still in progress, you will get a warning message about the inadvisability of doing so.

I apologize for any confusion my lack of clarity in my previous post has caused you.

Thanks very much for the clarification; this was making me kind of crazy. If I look in the DU Log, then I see the message "Repair Tool Completed." (Thinking something was amiss, I reapplied the 10.6.4 Combo, which certainly did no harm.)

But now, unfortunately, a new question has arisen while all this was going on. When I was checking to see if the message would be different on the Internal and clear up there, DU booted from the Clone kept telling me that the Internal could not be unmounted. This would usually happen temporarily if Spotlight were busy indexing (the Clone is in Privacy, anyway) or some file on the Internal were temporarily in use, but this seems permanent. Since I'm booted from the Clone when this happens, l can't look in AM to see what's hanging the Internal, so don't quite know how to troubleshoot this. Should I start a new thread for this? Seems like I've now hijacked the crap out of this one.

Was afraid to unmount the Volume manually, since I didn't know what was causing the problem from DU and thought I might end up in a bigger mess. I ran DU from the Install Disk instead when this happened.

I closed out all open Apps before rebooting to the Clone.





Message was edited by: WZZZ

You're correct. To see everything, open the DiskUtility.log file in the Console app. Results above.

It probably would be best to start a new topic for this issue to give it wider exposure, & because it is becoming a little confusing to keep the details of your system distinct from others.

However, from what you say the issue may have something to do with how you made the clone, so if you do start a new topic please make sure you include the details about that.

Hi,

I need some assistance with this topics. Recently when I tried to boot into my backup OS drive (on an external drive), I keep getting a crash screen at the boot up (full grey screen) asking me to hold down the power to shut down.

I did a repair disk from DU and it gave me the same message as the original poster. However, the progress bar at the bottom is complete so I'm not sure if I should be waiting or not? This message lead me to think if my boot partition have problem that caused me unaable to boot from an external drive?

Hello,
I had the same message and eventually it disappeared and then said the repair is complete.

Peace,
michael

I'm not sure if this has been addressed here, but I'm running into the same thing and I'm under a strict deadline. The drive I'm trying to verify and repair is actually a raided storage drive. At the recommendation of DU, I clicked repair, it said "Repair Complete" and went into Updating boot support partition mode for an hour... this isn't a boot drive nor will it ever be.

The "progress" bar is just barber pole and now it feels like I'm waiting for nothing.

I would boot from OS X DVD and also use Disk Warrior (though Disk Warrior will cause RAID with system to show up as "EFI" when using Option boot). Boot from some place that can un-mount your array. Maybe even a small 10.6.6 emergency system.

Read the part "Last Block" and even "Protective MBR" to see what Apple is up to.

http://developer.apple.com/library/mac/#technotes/tn2006/tn2166.html

Microsoft actually provides a pretty good discussion of use of GPT drives and layout:

http://www.microsoft.com/whdc/device/storage/GPT-on-x64.mspx

There is no guarantee that a new drive, especially when you get into TB sized, are without weak or bad sectors.