Link to home
Start Free TrialLog in
Avatar of okamon
okamon

asked on

how to tell what caused the raid failure?

I have a hp proliant server. I would like to know in case of raid failure, how do I find out what cause it? From what I know there are several possibilities that could cause raid failure:

- 2 hard drives failed
- raid controller failed
- raid configuration corruption

how to identify in each of the above situation? and is there any other possibilities?
Avatar of David
David
Flag of United States of America image

The raid controller's event logs are a good start.  Are you using HP's smart array? If so download their software to look at the logs>
Avatar of okamon
okamon

ASKER

yes, it's hp smart array. How to access the log if i cannot even boot into windows?
Boot SmartStart CD (or Intelligent Provisioning in BIOS) and run ADU/ACU and then upload adureport.txt as an attachment to the thread and we will diagnose, or learn to read the report yourself.
Avatar of okamon

ASKER

thanks. besides using smart start cd, is there a way to tell in bios, or in the raid controller setting?
If the RAID Controller has problems or it is bad then you will simply not have a chance to log into RAID Configuration utility. That should be a sign for you that problem could be with RAID controller and not the RAID set or drive.
ORCA/BIOS isn't very powerful, it really has to be the ACU/ADU but with Gen8 that's built into the boot ROM anyway.
Avatar of okamon

ASKER

thanks. >>If the RAID Controller has problems or it is bad then you will simply not have a chance to log into RAID Configuration utility

how about if the raid configuration corrupted? can I still log into utility? if yes, how to tell it's corrupted?
If the RAID configuration is corrupt, (which happens), then problem solved.  Root cause was controller, not HDD failure.
ASKER CERTIFIED SOLUTION
Avatar of Member_2_231077
Member_2_231077

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It's pretty hard to corrupt the configuration since it's stored on every disk although taking them out and shuffling them can confuse it.

When i worked in HP Presales we always used to tell people that you could take them out and juggle them, cuz you could!   :-)
It is hard, but it happens, especially in multiple failure scenarios.  If somebody wants reliability bordering on infallible, then shift the decimal point over to the left in terms of cost ;)
Avatar of okamon

ASKER

dlethe, I am not sure what you mean here -> If the RAID configuration is corrupt, (which happens), then problem solved.

so how do I tell if it's corrupt? is it just like what noxcho mentioned that I wouldn't even be able to log on to the utility?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of okamon

ASKER

so how do I repair it? will I lose all my data?
No way to give you a definitive answer in all cases w/o having somebody run some analysis.  I doubt anybody will do that for free as it requires talent and software that you don't have, which means sending drives off and paying for a forensic storage expert to look at it.

It is more money than you want to pay. Trust me.  

If you want something that will catch most problems with a high degree of confidence, then look at controller event logs as that is good enough for most people.