I am ahaving a SEVERE problem with my RAID array. I am running a xserve
10.3.9 with an xserve RAID ver1.3.3 and whenever I attempt to use the disk
utility to check the status of the raid I receive the following errors:
-Volume check failed
-Error: the underlying task reported failure -9972
- Keys out of order
- the volume cannot be repaired.
The only way I have been able to resolve this is to erase what little data
is on the volume and run the utility again. It works fine for a few days and
goes back to the original errors.
Has anyone experieced this and may be able to assist me?
You have a major filesystem error. This isn't a hard error, that is
it isn't with any failing hardware components, but rather that the
data structures the disk filesystem uses are foobar. This type of
error normally occurs when the filesystem is uncleanly shutdown or
system components crash badly. You may also want to examine to make
sure your XServe RAID is properly attached and that there aren't any
connectivity issues between them.
This particular error is unrepairable. To recover what you can from
the volume, back it up, erase the volume, and restore it.
Some will claim that DiskWarrior will fix this error. It will not, it
will just appear to have done so. What will happen is taht it will
recover what it can from the volume but you will end up with missing
and/or corrupt files, though the volume's filesystems datastructures
will be repaired.
At 5:10 PM -0600 8/11/05, Philip Ershler wrote:
A couple of bits of information that might help folks to assist you.
1. Is this a brand new XServer RAID, if not how old is it?
2. How have you got the RAID configured?
3. Have you replaced any of the drives in any of the sleds with
drives you purchased yourself?
4. Do you ever get any Yellow Lights on any of the drives
(indicating that the S.M.A.R.T. technology in the drive has detected
any sort of problem)?
All of these are hardware issues. However the issue present is purely
one of filesystem datastructure corruption, and that normally only
occurs when th kernel's filesystem craps out for some reason. So I'd
think the issue is software related, or at least accessibility
related between the XServe and XServe RAID, not with any drive
modules themselves, or realted to how the RAID itself is configured.
--
-dhan
------------------------------------------------------------------------
Dan Shoop AIM: iWiring
Systems & Networks Architect http://www.iwiring.net/
email@hidden http://www.ustsvs.com/
iWiring provides systems and networks support for Mac OS X, unix, and
Open Source application technologies at affordable rates.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
