Thank you very much for your reply. I thought these were errors relating to the SCSI Inquiry not being read but the drive came with a Dell Server we have, and it was working fine prior:
Vendor ID : DELL Product ID : MAX3073RC Revision : D206 Though you mention something that is worrying, that the slot failed. Could I make this drive a hot swappable or clear, which I did successfully, if the slot had failed? Is there any way to test a failed slot through these tools? I checked consistency (when the drive was replaced) and all was okay it seems. If the slot failed, it seems to me that the drive may not even be recognized. The drive is a Dell drive (well Fujitsu) - I find it odd it would bug out... Thank you Afra On Thu, 3 Dec 2009, Jefferson Ogata wrote: > On 2009-12-03 07:08, [email protected] wrote: > > To follow up I did the exportlog action when running omconfig and > > /var/log/lsi_1203.log had entries like this: > > > > 12/04/09 0:40:55: ILLEGAL REQ: pRdm(a07e8a00) Cmd=3, Sns=a07e8a40 > > DevId[5] Tgt 5 > > 12/04/09 0:40:55: info: 0, aslen= a, cmdSpecific[3]= 0 [2]= 0 > > [1]= 0 [0]= 0 > > 12/04/09 0:40:55: asc=24, Ascq 0, Sks:c8, fp[0]= 0, fp[1]= 3 > > 12/04/09 0:40:55: EVT#16440-12/04/09 0:40:55: 113=Unexpected sense: PD > > 05(e1/s5), CDB: 12 01 dc 01 1d 00, Sense: 70 00 05 00 00 00 00 0a 00 00 00 > > 00 24 00 01 c8 00 03 > > The CDB decodes as a SCSI INQUIRY (0x12) for page code 0xdc, which is in > the vendor-specific range. Additional sense code 0x24 with additional > sense code qualifier 0x00 indicates "INVALID FIELD IN CDB"; i.e. the > drive responds that it doesn't like the inquiry. This could be a red > herring; perhaps the PERC did an inquiry for a page code that that > particular drive doesn't handle. > > Here's some help for decoding the SCSI info: > > http://en.wikipedia.org/wiki/SCSI_Inquiry_Command > http://www.t10.org/lists/asc-num.htm > > Here's someone who saw something very similar once upon a time: > > http://forums.seagate.com/stx/board/message?board.id=scsi_drives&message.id=133 > > I would pull the drive out and do a self-test on another box. If you > have a generic SAS controller you should be able to do this with > smartctl. If all you have is PERCs you can use megasasctl. There's also > the slim possibility that the slot failed; maybe the previous disk > didn't actually fail. > > _______________________________________________ > Linux-PowerEdge mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq > _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
