Unsolved

This post is more than 5 years old

18 Posts

1685

October 10th, 2017 21:00

errors in dset report r420 server

hi

dell r420, Xeon E5-2430 proc, 32 gb ram, 2x600 gb drives in raid 1 + 2x600 gb drives in raid 1

host OS - windows 2008R2

Guest - 2 X windows 2008R2 VPS

FIRMWARE

iDRAC7 Version 1.66.65 (Build 7)

Lifecycle Controller 2 Version 1.4.2.12

BIOS 2.4.2

PERC H310 Mini 20.13.1-0002

ISSUES

1) server is slow to respond

2) in windows we are receiving a continuous flow of warnings, several per second as follows

Source:        Microsoft-Windows-WHEA-Logger
Level:         Warning
Description: A corrected hardware error has occurred.

3) Errors in SERVER DSET report

10/08/17  0:32:49: prDiskStart: starting Patrol Read on PD=00
10/08/17  0:32:49: prDiskStart: starting Patrol Read on PD=01
10/08/17  0:32:49: prDiskStart: starting Patrol Read on PD=02
10/08/17  0:32:49: prDiskStart: starting Patrol Read on PD=03
10/08/17  0:32:49: EVT#05197-10/08/17  0:32:49:  39=Patrol Read started
10/08/17  4:38:49: prCallback: PR completed for pd=03
10/08/17  4:38:53: prCallback: PR completed for pd=02
10/08/17 20:27:15: EVT#05198-
10/08/17 20:27:15: 113=Unexpected sense: PD 01(e0x20/s1) Path 5000c5007108a3e9, CDB: 2f 00 06 4c 0 00 00 10 00 00, Sense: 3/11/00
10/08/17 20:27:15: Raw Sense for PD 1: f0 00 03 06 4c 62 0d 0a 00 00 00 00 11 00 81 80 00 97
10/08/17 20:27:15: DEV_REC:Medium Error DevId[1] devHandle b RDM=c0453e00 retires=0
10/08/17 20:27:15: ErrLBAOffset (20d) LBA(64c6000) BadLba=64c620d
10/08/17 20:27:15: prCallback: Medium Error on pd=01, StartLba=64c6000, ErrLba=64c620d
10/08/17 20:27:15: prRecQueue: starting pd=01 recovery - blocking host commands
10/08/17 20:27:15: prRecGo: Ready to attempt recovery errLBA=64c620d on pd=01
10/08/17 20:27:15: prRecGo: dataErr found on ld=0, span=0, physArm=1, logArm=0, row=c98c4, strip=c98c4, startRef=30000000d,type=0
10/08/17 20:27:15: prRecGo: data NOT valid in cache
10/08/17 20:27:15: prRecCallback: READ from mirror arm successful; send WV to pd=01
10/08/17 20:27:16: prRecCallback: WV has successfully completed on pd=01
10/08/17 20:27:16: EVT#05199-10/08/17 20:27:16:  93=Patrol Read corrected medium error on PD 01(e0x20/s1) at 64c620d
10/08/17 20:27:33: EVT#05200-10/08/17 20:27:33: 113=Unexpected sense: PD 01(e0x20/s1) Path 5000c5007108a3e9, CDB: 2f 00 06 4d 12 0e 00 10 00 00, Sense: 3/11/00
10/08/17 20:27:33: Raw Sense for PD 1: f0 00 03 06 4d 1b 7b 0a 00 00 00 00 11 00 81 80 00 97
10/08/17 20:27:33: DEV_REC:Medium Error DevId[1] devHandle b RDM=c0465200 retires=0
10/08/17 20:27:33: ErrLBAOffset (96d) LBA(64d120e) BadLba=64d1b7b
10/08/17 20:27:33: prCallback: Medium Error on pd=01, StartLba=64d120e, ErrLba=64d1b7b
10/08/17 20:27:33: prRecQueue: starting pd=01 recovery - blocking host commands
10/08/17 20:27:33: prRecGo: Ready to attempt recovery errLBA=64d1b7b on pd=01
10/08/17 20:27:33: prRecGo: dataErr found on ld=0, span=0, physArm=1, logArm=0, row=c9a36, strip=c9a36, startRef=30000007b,type=0
10/08/17 20:27:33: prRecGo: data NOT valid in cache
10/08/17 20:27:33: prRecCallback: READ from mirror arm successful; send WV to pd=01
10/08/17 20:27:35: prRecCallback: WV has successfully completed on pd=01
10/08/17 20:27:35: EVT#05201-10/08/17 20:27:35:  93=Patrol Read corrected medium error on PD 01(e0x20/s1) at 64d1b7b
10/08/17 20:27:36: EVT#05202-10/08/17 20:27:36: 113=Unexpected sense: PD 01(e0x20/s1) Path 5000c5007108a3e9, CDB: 2f 00 06 4d 1b 7c 00 10 00 00, Sense: 3/11/00
10/08/17 20:27:36: Raw Sense for PD 1: f0 00 03 06 4d 1b 7c 0a 00 00 00 00 11 00 81 80 00 97
10/08/17 20:27:36: DEV_REC:Medium Error DevId[1] devHandle b RDM=c0465600 retires=0
10/08/17 20:27:36: ErrLBAOffset (0) LBA(64d1b7c) BadLba=64d1b7c
10/08/17 20:27:36: prCallback: Medium Error on pd=01, StartLba=64d1b7c, ErrLba=64d1b7c
10/08/17 20:27:36: prRecQueue: starting pd=01 recovery - blocking host commands
10/08/17 20:27:36: prRecGo: Ready to attempt recovery errLBA=64d1b7c on pd=01
10/08/17 20:27:36: prRecGo: dataErr found on ld=0, span=0, physArm=1, logArm=0, row=c9a36, strip=c9a36, startRef=30000007c,type=0
10/08/17 20:27:36: prRecGo: data NOT valid in cache
10/08/17 20:27:36: prRecCallback: READ from mirror arm successful; send WV to pd=01
10/08/17 20:27:37: prRecCallback: WV has successfully completed on pd=01
10/08/17 20:27:37: EVT#05203-10/08/17 20:27:37:  93=Patrol Read corrected medium error on PD 01(e0x20/s1) at 64d1b7c
10/08/17 20:27:38: EVT#05204-10/08/17 20:27:38: 113=Unexpected sense: PD 01(e0x20/s1) Path 5000c5007108a3e9, CDB: 2f 00 06 4d 1b 7d 00 10 00 00, Sense: 3/11/00
10/08/17 20:27:38: Raw Sense for PD 1: f0 00 03 06 4d 1b 7d 0a 00 00 00 00 11 00 81 80 00 97
10/08/17 20:27:38: DEV_REC:Medium Error DevId[1] devHandle b RDM=c0466e00 retires=0
10/08/17 20:27:38: ErrLBAOffset (0) LBA(64d1b7d) BadLba=64d1b7d
10/08/17 20:27:38: prCallback: Medium Error on pd=01, StartLba=64d1b7d, ErrLba=64d1b7d
10/08/17 20:27:38: prRecQueue: starting pd=01 recovery - blocking host commands
10/08/17 20:27:38: prRecGo: Ready to attempt recovery errLBA=64d1b7d on pd=01
10/08/17 20:27:38: prRecGo: dataErr found on ld=0, span=0, physArm=1, logArm=0, row=c9a36, strip=c9a36, startRef=30000007d,type=0
10/08/17 20:27:38: prRecGo: data NOT valid in cache
10/08/17 20:27:38: prRecCallback: READ from mirror arm successful; send WV to pd=01
10/08/17 20:27:39: prRecCallback: WV has successfully completed on pd=01
10/08/17 20:27:39: EVT#05205-10/08/17 20:27:39:  93=Patrol Read corrected medium error on PD 01(e0x20/s1) at 64d1b7d

what should i do to resolve this ?

thanks,

rajesh

PERC H310 Mini 20.13.1-0002

Moderator

 • 

9.7K Posts

October 11th, 2017 07:00

IndianNic,

It looks like PD1 might be on its way out, but to confirm I would like to run a Consistency Check on it.  Which you can do from the controller. Depending on the results it my be that you will need to start thinking about replacing PD1 if need be.

Let me know if this helps.

0 events found

No Events found!

Top