aacraid failures, more info

James Bourne jbourne at mtroyal.ca
Sat Aug 9 20:46:20 CDT 2003


HI,
thought I'd forward this along as well.

I thought, before I reboot the system that has the failed drive, that I'd go
into afacli and see if I can see anything interesting.

Under diag in the history for the controller, I found many error messages.
Don't know if they will help, but here they are.  FWIW, it actually looks
like some of these are passed directly back to the driver, or at least are
reproduced in the driver exactly as they are in the controller history.

Here are the messages.

_diagnostic > show history
Executing: diagnostic show history
No switches specified, defaulting to "/current".



 *** HISTORY BUFFER FROM CURRENT CONTROLLER RUN ***

[00]: ID(1:03:0) Timeout detected on cmd[0x28]
[01]: ID(1:03:0): Timeout detected on cmd[0x28]
[02]:  <...repeats 2 more times>
[03]: SCSI Channel[1]: Timeout Detected On 4 Command(s)
[04]: ID(1:03:0) Cmd[0x28] Fail: Block Range 10738560 : 10738687
[05]: at 335887 sec
[06]: ID(1:03:0) - IO failed, Cmd[0x28]
[07]: ID(1:03:0) Cmd[0x28] Fail: Block Range 8015 : 8062 at 33588
[08]: 7 sec
[09]: ID(1:03:0) Cmd[0x28] Fail: Block Range 18505423 : 18505471
[10]: at 335887 sec
[11]: ID(1:03:0) Cmd[0x28] Fail: Block Range 10738304 : 10738431
[12]: at 335887 sec
[13]: RAID5 Container 1 Drive 1:3:0 Failure
[14]: ID(1:03:0): Timeout detected on cmd[0x28]
[15]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[16]: ID(1:03:0): Timeout detected on cmd[0x28]
[17]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[18]: ID(1:03:0): Timeout detected on cmd[0x28]
[19]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[20]: ID(1:03:0): Timeout detected on cmd[0x28]
[21]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[22]: ID(1:03:0): Timeout detected on cmd[0x28]
[23]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[24]: ID(1:03:0) Timeout detected on cmd[0x28]
[25]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[26]: ID(1:03:0): Timeout detected on cmd[0x28]
[27]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[28]: ID(1:03:0): Timeout detected on cmd[0x28]
[29]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[30]: ID(1:03:0): Timeout detected on cmd[0x28]
[31]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[32]: ID(1:03:0): Timeout detected on cmd[0x28]
[33]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[34]: ID(1:03:0): Timeout detected on cmd[0x28]
[35]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[36]: ID(1:03:0) Timeout detected on cmd[0x28]
[37]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[38]: ID(1:03:0): Timeout detected on cmd[0x28]
[39]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[40]: ID(1:03:0): Timeout detected on cmd[0x28]
[41]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[42]: ID(1:03:0): Timeout detected on cmd[0x28]
[43]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[44]: ID(1:03:0): Timeout detected on cmd[0x28]
[45]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[46]: ID(1:03:0): Timeout detected on cmd[0x28]
[47]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[48]: ID(1:03:0) Timeout detected on cmd[0x28]
[49]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[50]: ID(1:03:0): Timeout detected on cmd[0x28]
[51]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[52]: ID(1:03:0): Timeout detected on cmd[0x28]
[53]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[54]: ID(1:03:0): Timeout detected on cmd[0x28]
[55]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[56]: ID(1:03:0): Timeout detected on cmd[0x28]
[57]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[58]: ID(1:03:0): Timeout detected on cmd[0x28]
[59]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[60]: ID(1:03:0): Timeout detected on cmd[0x28]
[61]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[62]: ID(1:03:0) Timeout detected on cmd[0x28]
[63]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[64]: ID(1:03:0): Timeout detected on cmd[0x28]
[65]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[66]: ID(1:03:0): Timeout detected on cmd[0x28]
[67]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[68]: ID(1:03:0): Timeout detected on cmd[0x28]
[69]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[70]: ID(1:03:0): Timeout detected on cmd[0x28]
[71]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[72]: ID(1:03:0): Timeout detected on cmd[0x28]
[73]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[74]: ID(1:03:0) Timeout detected on cmd[0x28]
[75]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[76]: ID(1:03:0): Timeout detected on cmd[0x28]
[77]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[78]: ID(1:03:0): Timeout detected on cmd[0x28]
[79]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[80]: ID(1:03:0): Timeout detected on cmd[0x28]
[81]: SCSI Channel[1]: Timeout Detected On 1 Command(s)
[82]: ID(1:03:0) Cmd[0x28] Fail: Block Range 0 : 0 at 336214 sec
[83]: 2 can't read mbr dev_t:3
[84]:  <...repeats 1 more times>
[85]: can't read config from slice #[3]
[86]: 2 can't read mbr dev_t:3
[87]: can't read config from slice #[3]
[88]: CT_LogMissingEntry: Log missing entry, container 1, dev 131
[89]: , signature 0xa079c177, nvEntry 326
[90]: CtMarkDead: container 1, deadEntry 1, dev 131, signature 0x
[91]: a079c177
[92]: CtMarkDead: container 1, deadEntry 1, dev 131, signature 0x
[93]: a079c177
[94]: CtMarkDead: container 1, deadEntry 1, dev 131, signature 0x
[95]: a079c177
[96]: RAID5 Failover Container 1 No Failover Assigned
[97]: Drive 1:3:0 returning error
[98]: 2 can't read mbr dev_t:3
[99]: 

Regards
James Bourne

-- 
James Bourne, Supervisor Data Centre Operations
Mount Royal College, Calgary, AB, CA
www.mtroyal.ab.ca

"There are only 10 types of people in this world: those who
understand binary and those who don't."

*****************************************************************************

This  communication  is intended for the use  of the recipient to which it is
addressed,  and  may  contain  confidential,  personal,  and   or  privileged
information.  Please  contact  the  sender  immediately  if  you  are not the
intended recipient of this  communication, and  do not  copy, distribute,  or
take action relying on it. Any communication received in error, or subsequent
reply, should be deleted or destroyed.

*****************************************************************************




More information about the Linux-PowerEdge mailing list