UNSOLVED

wjgore

updated

11 years ago

W

wjgore

1 Message

0

16917

May 29th, 2015 15:00

Command Timeout errors/Medium Errors on an R710

Hola,

I have an R710 that is perpetually complaining of command time out errors on several disks. OMSA storage commands show all disks in OK status, but the alertlog shows multiple:

Severity      : Non-Critical
ID            : 2405
Date and Time : Fri May 22 11:56:58 2015
Category      : Storage Service
Description   : Command timeout on physical disk:  Physical Disk 0:3:6 Controller 1, Connector 0

... on several disks. There have been complains of service degradation, and nothing else in OMSA seems to correlate.
Exported the lsi log, and found multiple instances of:

05/22/15  8:23:43: DEV_REC:Medium Error DevId:emotion-14: devHandle 10 RDM=806d0c00 retires=0

05/22/15  8:23:43: MedErr is for: cmdId=19, ld=2, src=1, cmd=1, lba=62a680, cnt=180, rmwOp=0

05/22/15  8:23:43: ErrLBAOffset (7) LBA(20e280) BadLba=20e287

05/22/15  8:23:45: EVT#43598-05/22/15  8:23:45: 113=Unexpected sense: PD 06(e0x0f/s3) Path 5000c500350c3fdd, CDB: 28 00 00 20 e2 80 00 01 80 00, Sense: 3/11/00

05/22/15  8:23:45: Raw Sense for PD 6: f0 00 03 00 20 e2 87 0a 00 00 00 00 11 00 81 80 00 9d

05/22/15  8:23:45: DEV_REC:Medium Error DevId:emotion-14: devHandle 10 RDM=806f3400 retires=0

05/22/15  8:23:45: MedErr is for: cmdId=19, ld=2, src=1, cmd=1, lba=62a680, cnt=180, rmwOp=0

05/22/15  8:23:45: ErrLBAOffset (7) LBA(20e280) BadLba=20e287

05/22/15  8:23:45: BBM_CheckCmdTimer: TIMER_WITHIN_LIMIT secs 5

05/22/15  8:23:45: EBB_RecoverReadErrors: Issue WV for pd=06, lba=20e287

05/22/15  8:23:45: Issuing write verify pd=06 physArm=0 span=0 startBlk=20e287 numBlks=1

05/22/15  8:23:46: reassignMsgDone: cmdId 19, src 1, orgId 4

05/22/15  8:23:46: EVT#43599-05/22/15  8:23:46: 110=Corrected medium error during recovery on PD 06(e0x0f/s3) at 20e287

05/22/15 11:56:15: DM: Chip 0 Paused

05/22/15 11:56:15: Chip <0> Slots: Cur=[231]

05/22/15 11:56:15: [e9]= 3 [eb]= 3 [ec]=10 [ed]= c [ee]= b [ef]= 4 [f0]= 6 [f1]= 2

05/22/15 11:56:17: DM: Timing wheel expired - Chip 0 Slot e9

05/22/15 11:56:17: Chip <0> Slots: Cur=[233]

05/22/15 11:56:17: [e9]= 3 [eb]= 3 [ec]=10 [ed]= c [ee]= b [ef]= 4 [f0]= 6 [f1]= 2

05/22/15 11:56:17: TIMEOUT: rdm 8055e000, devHandle 0065, mid 012e, Cmd 01, devId 0023, devState 0020, devFlags f1c0000f

05/22/15 11:56:17: DM_PL_AllocateTaskMgmtFrame: TM mid=81a pTaskMgmt=c04d5e00

05/22/15 11:56:17: TIMEOUT: rdm 8062c800, devHandle 0065, mid 0467, Cmd 01, devId 0023, devState 0020, devFlags f1c8200f

05/22/15 11:56:17: TIMEOUT: rdm 80679e00, devHandle 0065, mid 006c, Cmd 01, devId 0023, devState 0020, devFlags f1c8200f

05/22/15 11:56:17: DM_TMWheelScanAllMsg (slot e9):Scanned 57, Timeout 3 Msg mask 21000

05/22/15 11:56:17: EVT#43600-05/22/15 11:56:17: 267=Command timeout on PD 23(e0x29/s6) Path 5000039388c81aa3, CDB: 28 00 1b 89 31 40 00 00 80 00

05/22/15 11:56:17: EVT#43601-05/22/15 11:56:17: 267=Command timeout on PD 23(e0x29/s6) Path 5000039388c81aa3, CDB: 28 00 1b 89 2f 40 00 00 40 00

05/22/15 11:56:17: EVT#43602-05/22/15 11:56:17: 267=Command timeout on PD 23(e0x29/s6) Path 5000039388c81aa3, CDB: 28 00 33 d7 80 c0 00 00 40 00

05/22/15 11:56:17: EVT#43603-05/22/15 11:56:17: 268=PD 23(e0x29/s6) Path 5000039388c81aa3  reset (Type 03)


Anybody have an idea what the cause may be, and how to fix it?

  • DELL-Todd S

    4 Apprentice

    •

    1837 Posts

    1571

    0

    Posted June 2nd, 2015 14:00

    Hi,

    I would recommend reposting this question on the Dell PowerEdge HDD/SCSI/RAID forum.   You would probably have better luck getting a response there than on here.

    Hope this helps.

    Todd