FreeBSD 6.4/i386 on Proliant DL360 G5 - drive failing but camcontrol says ok?

[Søren Klintrup]

Hi,

Per default camcontrol uses cached data from boot, you can update the data
using camcontrol inquiry da1 -D, that will output upated data, this has
worked for us on all versions smartarray controllers, if you have one that
it doesn't work on I'd love to know :-)

You should be able to get a few hints from my check_smartarray.sh script at
http://soren.klintrup.dk/proliant/.

Regards,
Søren


On Tue, Sep 7, 2010 at 9:49 AM, Karl Pielorz <kpielorz_lst at tdx.co.uk> wrote:

>
> Hi All,
>
> We've got a number of FreeBSD boxes running proliant DL360/G5's - we have
> stuff on there that periodically does:
>
> "
> # camcontrol devlist
> <COMPAQ RAID 1  VOLUME OK>         at scbus0 target 0 lun 0 (da0,pass0)
> <COMPAQ RAID 1  VOLUME OK>         at scbus0 target 1 lun 0 (da1,pass1)
> <COMPAQ RAID 1  VOLUME OK>         at scbus0 target 2 lun 0 (da2,pass2)
> "
>
> However, for this machine - there's a red light on one of the drives that
> constitutes 'da1' - yet camcontrol says it's "fine".
>
> We know that camcontrol does change when a drive actually 'fails', and
> shows the various stages the array goes through as it rebuilds with a new
> drive to recover - but this time it's not showing anything very helpful.
>
> Does anyone know if there's some way of getting the 'red light' status from
> the server? - From watching the drives (yeah, highly scientific) the machine
> doesn't appear to be sending any traffic to the drive with the red light on
> :(
>
> I'm going to power cycle the box when I get a chance to see what the
> onboard RAID controller reports for that drive/array - but it'd obviously be
> handy if we could know something was up with it sooner...
>
> -Kp
>
> _______________________________________________
> freebsd-proliant at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-proliant
> To unsubscribe, send any mail to "freebsd-proliant-unsubscribe at freebsd.org
> "
>