scsi sense errors in event viewer

Question

Once an hour I get a handful of warning message in my Event Viewer.  They are all the same except the change denoting a different physical disk (7-14).  There is a mix of SATA and SAS drives in an MD1000.  The SATA drives have not produced the error.  One SAS drive to supposedly fail last week after being online for only 1 week.  All green lights on the MD1000 and OMSA shows all is normal, but I keep getting the event log warnings.  Can anyone explain what the error or CDB is that is causing this?  Should I worry about it?  Is this causing the drives to fail?   Specs: PE 2900 PERC 6/e w/512mb MD1000 with 7 Seagate 1TB SATA drives and 8 Seagate 450gb SAS drives.      The Event viewer message: Event Type: InformationEvent Source: Server AdministratorEvent Category: Storage ServiceEvent ID: 2095Date:  9/2/2008Time:  9:49:13 AMUser:  N/AComputer: *******Description:SCSI sense data Sense key:  5 Sense code: 24 Sense qualifier:  0:  Physical Disk 0:0:7 Controller 1, Connector 0   Here is a snippet of the Perc6 Controller Logs taken from OMSA: 09/02/08  9:49:03: EVT#08954-09/02/08  9:49:03: 113=Unexpected sense: PD 12(e0x11/s11), 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 09/02/08  9:49:03: DEV_REC:IllegalReq- CDB: 12 1 dc 1 1d 0 09/02/08  9:49:03: ILLEGAL REQ: pRdm(a0752800) Cmd=3, Sns=a0752840 DevId[12] Tgt 10 09/02/08  9:49:03:   info:       0, aslen= a, cmdSpecific[3]= 0 [2]= 0  [1]= 0 [0]= 0 09/02/08  9:49:03: asc=24, Ascq  0, Sks:c8, fp[0]= 0, fp[1]= 3 09/02/08  9:49:03: EVT#08955-09/02/08  9:49:03: 113=Unexpected sense: PD 1a(e0x11/s14), 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 09/02/08  9:49:03: DEV_REC:IllegalReq- CDB: 12 1 dc 1 1d 0 09/02/08  9:49:03: ILLEGAL REQ: pRdm(a062a800) Cmd=3, Sns=a062a840 DevId[1a] Tgt d 09/02/08  9:49:03:   info:       0, aslen= a, cmdSpecific[3]= 0 [2]= 0  [1]= 0 [0]= 0 09/02/08  9:49:03: asc=24, Ascq  0, Sks:c8, fp[0]= 0, fp[1]= 3 09/02/08  9:49:03: EVT#08956-09/02/08  9:49:03: 113=Unexpected sense: PD 1b(e0x11/s13), 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 09/02/08  9:49:03: DEV_REC:IllegalReq- CDB: 12 1 dc 1 1d 0 09/02/08  9:49:03: ILLEGAL REQ: pRdm(a0781800) Cmd=3, Sns=a0781840 DevId[1b] Tgt e 09/02/08  9:49:03:   info:       0, aslen= a, cmdSpecific[3]= 0 [2]= 0  [1]= 0 [0]= 0 09/02/08  9:49:03: asc=24, Ascq  0, Sks:c8, fp[0]= 0, fp[1]= 3 09/02/08  9:49:03: EVT#08957-09/02/08  9:49:03: 113=Unexpected sense: PD 1c(e0x11/s12), 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 09/02/08  9:49:03: DEV_REC:IllegalReq- CDB: 12 1 dc 1 1d 0 09/02/08  9:49:03: ILLEGAL REQ: pRdm(a07dbc00) Cmd=3, Sns=a07dbc40 DevId[1c] Tgt f 09/02/08  9:49:03:   info:       0, aslen= a, cmdSpecific[3]= 0 [2]= 0  [1]= 0 [0]= 0 09/02/08  9:49:03: asc=24, Ascq  0, Sks:c8, fp[0]= 0, fp[1]= 3 09/02/08  9:49:03: EVT#08958-09/02/08  9:49:03: 113=Unexpected sense: PD 1e(e0x11/s10), 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 09/02/08  9:49:03: DEV_REC:IllegalReq- CDB: 12 1 dc 1 1d 0 09/02/08  9:49:03: ILLEGAL REQ: pRdm(a05f9c00) Cmd=3, Sns=a05f9c40 DevId[1e] Tgt 11 09/02/08  9:49:03:   info:       0, aslen= a, cmdSpecific[3]= 0 [2]= 0  [1]= 0 [0]= 0 09/02/08  9:49:03: asc=24, Ascq  0, Sks:c8, fp[0]= 0, fp[1]= 3 09/02/08  9:49:03: EVT#08959-09/02/08  9:49:03: 113=Unexpected sense: PD 1f(e0x11/s9), 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 09/02/08  9:49:03: DEV_REC:IllegalReq- CDB: 12 1 dc 1 1d 0 09/02/08  9:49:03: ILLEGAL REQ: pRdm(a05b2e00) Cmd=3, Sns=a05b2e40 DevId[1f] Tgt 12 09/02/08  9:49:03:   info:       0, aslen= a, cmdSpecific[3]= 0 [2]= 0  [1]= 0 [0]= 0 09/02/08  9:49:03: asc=24, Ascq  0, Sks:c8, fp[0]= 0, fp[1]= 3 09/02/08  9:49:03: EVT#08960-09/02/08  9:49:03: 113=Unexpected sense: PD 20(e0x11/s8), 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 09/02/08  9:49:03: DEV_REC:IllegalReq- CDB: 12 1 dc 1 1d 0 09/02/08  9:49:03: ILLEGAL REQ: pRdm(a05cf400) Cmd=3, Sns=a05cf440 DevId[20] Tgt 13 09/02/08  9:49:03:   info:       0, aslen= a, cmdSpecific[3]= 0 [2]= 0  [1]= 0 [0]= 0 09/02/08  9:49:03: asc=24, Ascq  0, Sks:c8, fp[0]= 0, fp[1]= 3 09/02/08  9:49:04: EVT#08961-09/02/08  9:49:04: 113=Unexpected sense: PD 21(e0x11/s7), 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 09/02/08  9:49:04: DEV_REC:IllegalReq- CDB: 12 1 dc 1 1d 0 09/02/08  9:49:04: ILLEGAL REQ: pRdm(a0522a00) Cmd=3, Sns=a0522a40 DevId[21] Tgt 14 09/02/08  9:49:04:   info:       0, aslen= a, cmdSpecific[3]= 0 [2]= 0  [1]= 0 [0]= 0 09/02/08  9:49:04: asc=24, Ascq  0, Sks:c8, fp[0]= 0, fp[1]= 3      - Jake

dell-richard g · Answer

All commands and sense data information is located in SCSI specifications. From your log file, it appears that the problematic command is operation code 12 (CDB), which is an Inquiry command. Because of this, the target will respond with sense data of 05 24 00, which means illegal request (5) and and asc/ascq of 24 00 which means invalid field in the CDB format. This means that one of the fields in the defined CDB 12 01 dc 01 1d 00. I would suspect that it is either the EVPD bit 01 (12 01), paged code DC or the second 01 (reserved) field this is the cause.

You need to determine the source of the command. One way to do this is to turn off some unnecessary services that may generate such commands. As a start, turn off system management software and see if the messages stop.

JakeVer1 · Answer

Thanks Richard.  I'll remove/stop what I can and see what happens.

JakeVer1 · Answer

After uninstalling Dell's OMSA software I have not recieved any of the hourly error messages.

Maybe Dell will have to update OMSA to handle Seagate's newest 450gb Cheeta's. For now I guess I'll have to use LSI's MegaRAID software to check in on the MD1000 and my drives.

Thanks again Richard.

dell-richard g · Answer

Ok, thanks for the feedback.  I wll report this to the OM team and reply back if there is an update.

PowerVault

Was this post helpful?