"Torsten Neumann" writes... > Package: arrayprobe > Version: 2.0-1 > Severity: important > > This is a raid5 configuration with hot spare. After rebuilding the array > it shows: > > # arrayprobe -f /dev/cciss/c1d0 > OK Arrayprobe All controllers ok > > but > > # hpacucli controller slot=3D1 array A physicaldrive all show > > Smart Array 6400 in Slot 1 > > array A (Failed) > physicaldrive 1:0 (port 1:id 0 , Parallel SCSI, 0 Byte, Failed) > physicaldrive 1:1 (port 1:id 1 , Parallel SCSI, 300 GB, OK) > physicaldrive 1:2 (port 1:id 2 , Parallel SCSI, 300 GB, OK) > physicaldrive 1:3 (port 1:id 3 , Parallel SCSI, 300 GB, OK) > physicaldrive 1:4 (port 1:id 4 , Parallel SCSI, 300 GB, OK) > physicaldrive 1:5 (port 1:id 5 , Parallel SCSI, 300 GB, OK) > physicaldrive 1:8 (port 1:id 8 , Parallel SCSI, 300 GB, OK, active = > spare) > > If running arrayprobe via cron once a day the failed drive might not be > reported at all. That's not what I expect from a status checker.
Wow that really sucks. I will forward the bug to upstream, but I don't know how much work he is still doing on this tool, we may need to debug it ourselves. Thanks for the report, I will take a look and see if I can figure out why it's doing that. Offhand I suspect it's due to the fact that the tool only reports the last state from the controller and the hot-spare is making the array "OK" in those terms. -- Matt Taggart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
