Posted on 03-01-2010 12:28 AM
Are all the error messages identical, other than individual machine
identifiers of course? It would seem odd that you'd suddenly have a
slew of machines all need their hard drive repaired at the same time.
If they were not all identical messages, at what other points were the
machines failing in their error logs?
-Dusty-
Dustin Dorey
Technology Support Cluster Specialist
Independent School District 196
Rosemount-Apple Valley-Eagan Public Schools
dustin.dorey at district196.org
651|423|7971
Posted on 03-01-2010 12:34 AM
Dustin,
Yes, all of the error messages have this identical infomation:
The volume Macintosh HD needs to be repaired
Error detected while verifying/repairing volume disk0s2 Macintosh HD:
Filesystem verify or repair failed (-9957)
Finished verify/repair volume (filesystem) on disk disk0s2 Macintosh HD
Error detected while verifying/repairing volume disk0s2 Macintosh HD:
Filesystem verify or repair failed (-9957)
I agree that this is very strange!
Jeff
Posted on 03-01-2010 12:38 AM
Have you done a spot check on any of these machines and done a verify with
the GUI or SSH and run the diskutil command to see if you get the same
error?
--
Alan Benedict
?
Macintosh Technician
The Integer Group
O: 515-247-2738
C: 515-770-8234
http://www.integer.com
Posted on 03-01-2010 01:13 PM
Yes, and I haven't seen any problems on the few I've checked out...
Alan Benedict <abenedict at integer.com> on March 1, 2010 at 2:38 PM -0600 wrote:
Jeff
Posted on 03-02-2010 12:25 AM
Hi,
I get exactly the same message and have done for well over a year if not longer, from version 6 of casper and no to 7.
I did post on here before but got no reply, i get 5-10 of these a day so i built a netboot image that would boot and repair the local drive and then restart the mac back to its local drive, this fixes the problem for a while but it comes back, it happens on all my macs eventually so i have no idea what causes it, but it seems to have little or no effect.
Sorry i cant help with the cause but now i just ignore them as it seems to have little impact and more hassel running the disk repair netboot than just leaving it until the next image is ready
But it still like to know if anyone else can find the cause
Criss
?xml version="1.0" encoding="ISO-8859-1"?> Default Title
Criss Myers
Senior Customer Support Analyst (Mac Services)
iPhone Developer
Apple Certified Technical Coordinator v10.5
LIS Development Team
Adelphi Building AB28
University of Central Lancashire
Preston PR1 2HE
Ex 5054
01772 895054