• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Volume header needs minor repair
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Volume header needs minor repair


  • Subject: Re: Volume header needs minor repair
  • From: Vlad Beffa <email@hidden>
  • Date: Sat, 8 Sep 2007 07:30:53 +0200

I ran Disk Utility and get the same message. I have OS 10.4.10 with Disk Utility 10.5.6 (198.12).

Vlad


    I've always booted into single user mode and run fsck manually. It found and fixed whatever was wrong. 

Running diskutil or Disk Utility to verify/repair the volume is probably preferred.

--


-dhan


------------------------------------------------------------------------
Dan Shoop                                                   AIM: iWiring
Systems & Networks Architect                      http://www.ustsvs.com/
email@hidden                                http://www.iwiring.net/
1-714-363-1174


"The wise man doesn't give the right answers, he poses the right
questions." -- Claude Levi-Strauss




Hi everybody,


I'm well aware that this list might not be the most appropriate place for my question, but I've spent a long, long time looking for an answer on the web and didn't find anything helpful.

Ok, so here's I go: On three different Intel-based Macs, when letting Disk Utility check the boot volume (journaled HFS+), I'm occasionally getting, in big read letters, a message saying that verification of the volume failed and that the "Volume header needs minor repair".

The document at http://docs.info.apple.com/article.html?artnum=107250 says that this error message can safely be ignored on journaled HFS+ volumes. However, the document specifically claims to apply to Mac OS X 10.3.9 or earlier only.

I've always booted into single user mode and run fsck manually. It found and fixed whatever was wrong. Still, I'm wondering if that's really necessary, or if the information in the above mentioned document also applies to Mac OS X 10.4 and up, and the error can still safely be ignored.

As a side note, I've got the strange (but as of yet unproven) feeling that the issue regularely occurs after installing a new Software Update that requires a reboot. I guess I'll keep an eye on that, but for now let's only sum the question up again: Does the information in the above mentioned document still apply to 10.4+ and can the error messages mentioned in there still safely be ignored?

Any hints would be much appreciated!


Greetings,
Nils

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: EVFILT_SIGNAL - observe "standard" signals before they are delivered?
  • Next by Date: thread_policy_set
  • Previous by thread: Re: EVFILT_SIGNAL - observe "standard" signals before they are delivered?
  • Next by thread: thread_policy_set
  • Index(es):
    • Date
    • Thread