HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Error 51 on SAN connected blades

 
jfk8680
Occasional Advisor

Error 51 on SAN connected blades

Hi,

We have a large SAN box (a HP XP12000) in our datacenter which provides SAN storage to numerous blade servers running various editions of Windows 2000 Server. On a couple of them we are experiencing a lot of Event ID 51 messages in the event viewer:

Type: Warning Event ID: 51
User: N/A
Computer:

Description:
An error was detected on device \Device\Harddisk2\DR2 during a paging operation.

Data:
0000: 03 00 22 00 01 00 72 00 .."...r.
0008: 00 00 00 00 33 00 04 80 ....3..?
0010: 2d 01 00 00 00 00 00 00 -.......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 00 02 00 00 00 ........
0030: 01 00 00 00 28 00 00 00 ....(...
0038: 00 12 00 00 00 00 00 00 ........
0040: 28 20 12 90 04 af 00 00 ( .?.¯..
0048: 08 00 ..

I have checked everything I can think of: driver versions, types of blades used, operating system, hotfixes etc. etc. I can find no difference between servers that suffer from this error and servers that do not display this error.

We have installed hotfix KB830051 on our SAN attached servers and this seemed to resolve the problem but after a couple of days the Event ID 51 messages were flooding the event viewer again.

I have analyzed the data in the event viewer using KB article Q244780 and the error message is the same on all servers, except for the starting sector and the number of sectors:

SCSISTATUS 0x00 SCSISTAT_GOOD
SRBSTATUS 0x12 SRB_STATUS_DATA_OVERRUN
SCSISENSE 0x00 SCSI_SENSE_NO_SENSE
SCSICDB 0x28 SCSIOP_READ
SECTOR 0x129004af
# SECTORS 8

I have also checked if the blades that suffer from the error are connected to the SAN through the same fabric switch or if they are connected to the same port on the SAN. Neither was the case...

I am kind of at wits end here and have no idea where to look now. We have had contact with HP and Microsoft over this issue but that is not going anywhere soon at the moment either...

Did anybody experience this in the past or have any bright ideas how to proceed??

Thanks,

Jeffrey