poppalocs

Q: disk utility stopped verifying; need repair... over and over and over

I've gone through the restart, Command+R drill 4 times. Repaired the disk using "Disk Utility." Restarted after repair, ran disk utility to verify the repair and BAM disk utility stops verifying and instructs me to restart ... etc.

 

The errors have been consistent: orphaned blocks, invalid volume free block count. But when I use utility disk after restarting and pressing command+r, the "repair disk" does not appear to do anythign beyond "Load and Verify" freespace summary and block accounting. Am I missing a step?

 

Any suggestions appreciated.

MacBook Pro, OS X Mountain Lion (10.8.2), 2.9 GHz i7; 8GB DDR3

Posted on Jan 2, 2013 1:47 AM

Close

Q: disk utility stopped verifying; need repair... over and over and over

  • All replies
  • Helpful answers

  • by sig,

    sig sig Jan 2, 2013 5:05 AM in response to poppalocs
    Level 8 (35,798 points)
    Mac OS X
    Jan 2, 2013 5:05 AM in response to poppalocs

    If Disk Utility cannot repair the disk then you need a stonger disk repair utility like Disk Warrior. Your other option is to reformat the hard drive and reinstall your files.

  • by poppalocs,

    poppalocs poppalocs Jan 2, 2013 8:58 AM in response to sig
    Level 1 (4 points)
    Jan 2, 2013 8:58 AM in response to sig

    Thank you for the recommendation. I will look into Disk Warrior.

     

    After originally posting I continued searching the forums and, of course, google. During my search I came across the following support article that essentially says to ignore the problem. http://support.apple.com/kb/TS2028

     

    Thoughts?

     

    Btw, I don't know if I have a "journaled" disk or not.

  • by ~Bee,

    ~Bee ~Bee Jan 2, 2013 10:10 AM in response to poppalocs
    Level 7 (31,792 points)
    Mac OS X
    Jan 2, 2013 10:10 AM in response to poppalocs

    poppa --

     

    Repaired the disk using "Disk Utility."

     

    Are you talking about Repairing Permissions using DU, or Repairing Disk via the Install Disk?

  • by sig,

    sig sig Jan 2, 2013 3:13 PM in response to ~Bee
    Level 8 (35,798 points)
    Mac OS X
    Jan 2, 2013 3:13 PM in response to ~Bee

    Hi Bee, based upon the OP's initial post I am assuming he means Repair Disk.

    "The errors have been consistent: orphaned blocks, invalid volume free block count."

    Those would show up on a Repair Disk not a Repair Permissions.

  • by poppalocs,

    poppalocs poppalocs Jan 2, 2013 5:07 PM in response to sig
    Level 1 (4 points)
    Jan 2, 2013 5:07 PM in response to sig

    Correct. But to answer Bee, I use disk utility via restart, Command+R.

  • by poppalocs,

    poppalocs poppalocs Jan 2, 2013 5:09 PM in response to ~Bee
    Level 1 (4 points)
    Jan 2, 2013 5:09 PM in response to ~Bee

    Any thoughts on the support article stating that the "errors" can be ignored?

     

    Seems like someone at Apple oughta be able to design DU to advise user (such as moi) that the error can be ignored...wishful (ignorant) thinking.

  • by sig,

    sig sig Jan 3, 2013 12:18 AM in response to poppalocs
    Level 8 (35,798 points)
    Mac OS X
    Jan 3, 2013 12:18 AM in response to poppalocs

    That article does not pertain to the OS you are running. "This article has been archived and is no longer updated by Apple."

    It pertains to using fsck not Disk Utility for:

    Products Affected

    Mac OS X 10.3.9, Mac OS X 10.4, Mac OS X 10.5, Mac OS X Server 10.2, Mac OS X Server 10.3, Mac OS X Server 10.4, Mac OS X Server 10.4.7, Mac OS X Server 10.5

  • by ~Bee,

    ~Bee ~Bee Jan 3, 2013 5:00 AM in response to sig
    Level 7 (31,792 points)
    Mac OS X
    Jan 3, 2013 5:00 AM in response to sig

    Hi sig --

     

    Got it, thanks.  I keep forgetting there are no more "disks!"

     

  • by poppalocs,

    poppalocs poppalocs Jan 3, 2013 9:46 AM in response to sig
    Level 1 (4 points)
    Jan 3, 2013 9:46 AM in response to sig

    Yah, I saw that. But being that the underlying issue is the same; right now I'm leaning toward just ignoring it. The only reason I even know the "issue" exists is because I decided to verify the disk. Since I don't have any issues with startup, shutdown, etc., I'm going to continue to look for solutions short of formatting and resintallation.

     

    Anyway, thank you for taking the time to suggest a solution.