ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Drive Array Controllers No Longer Redundant ?

linuxfix
Visitor

Drive Array Controllers No Longer Redundant ?

I see this error in my ILO for a DL380 with 16 drives:

 

/system1/log1/record3
Targets
Properties
number=3
severity=Caution
date=12/17/2011
time=11:10
description=Drive Array Controllers No Longer Redundant

 

I also see this  from hpacucli:

$ sudo hpacucli
HP Array Configuration Utility CLI 9.10.5.18
Detecting Controllers...Done.
Type "help" for a list of supported commands.
Type "exit" to close the console.

=> ctrl slot=0 ld all show

Smart Array P410i in Slot 0 (Embedded)

array A

logicaldrive 1 (931.5 GB, RAID 1, OK)

array B

logicaldrive 2 (931.5 GB, RAID 0, OK)

array C

logicaldrive 3 (931.5 GB, RAID 0, OK)

array D

logicaldrive 4 (931.5 GB, RAID 0, OK)

array E

logicaldrive 5 (931.5 GB, RAID 0, Failed)   <-----------------------

array F

logicaldrive 6 (931.5 GB, RAID 0, OK)

array G

logicaldrive 7 (931.5 GB, RAID 0, OK)

array H

logicaldrive 8 (931.5 GB, RAID 0, OK)

array I

logicaldrive 9 (931.5 GB, RAID 0, OK)

array J

logicaldrive 10 (931.5 GB, RAID 0, OK)

array K

logicaldrive 11 (931.5 GB, RAID 0, OK)

array L

logicaldrive 12 (931.5 GB, RAID 0, OK)

array M

logicaldrive 13 (931.5 GB, RAID 0, OK)

array N

logicaldrive 14 (931.5 GB, RAID 0, OK)

array O

logicaldrive 15 (931.5 GB, RAID 0, OK)

 

Has anyone seen this, and is there are way to resolve this?  

 

Can I replace a drive, or just rebuild the array? 

 

Thanks

2 REPLIES
linuxfix
Visitor

Re: Drive Array Controllers No Longer Redundant ?

So the one logical drive failed,....

 

I forced a reenable with the hpacucli in linux:

>ctrl slot=0 ld 5 modify reenable 

 

this "logical drive failure" is happening on more and more drives of mine.

 

I have 14 drives with raid 0 in my hosts....Im not sure if this is causing an array failure.

 

linuxfix
Visitor

Re: Drive Array Controllers No Longer Redundant ?

My suspicion is this has to do with a firmware issue...

I found out there is a new firmware adressing incorrect cache data being reported back to the controller.

I'll have the firmware updated, force the logical drive back online... and hope for the best.