Proliant DL580 not showing Logical Disks on RA4100

[Jeroen Hems]

Hi there, at Radio Netherlands we run Exchange on a cluster of two DL580's, equiped with two 64-bit FC Host Adapters each, that are connected to a RA4x00 enclosure, which is equiped with two RA4100 Raid controllers.

The cluster layout is drawn in the attached file.

On on of the nodes (MINORCA) we cannot see the LUNs that we've created on the array. Windows Device Manager shows 4 Logical SCSI Disks on RA controller 1 and 1 Logical SCSI Disk and three Disk drives on RA controller 2.

We use securepath v.3.2. An old one, I know, but if it works don't mess with it, my mom says ;-)

On the other node Device Manager shows 8 Logical SCSI Disks. So the RA4100 controllers and the enclosure seem to work fine.

I've replaced every FC cable from MINORCA to the disk enclosure, but that didn't solve it, so doesn't seem to be a cabling problem.

In SPM I can't find any problems, all paths are present and verified. So it seems to be a problem in Windows 2000.

I was wondering if anyone had similar problems, and what else they did to solve it.

Thanx,

Jeroen Hems

[Jeroen Hems]

In eventviewer, the following Raidisk event pops up:

===
Event Type: Error
Event Source: raidisk
Event Category: None
Event ID: 1026
Date: 11/8/2004
Time: 6:52:20 PM
User: N/A
Computer: MINORCA
Description:
The Driver has detected a path failure to Subsystem ID 80440092. Dump Data 0 contains the Phys Path Info < Port | Bus | Target | 0 >. Dump Data 1 contains the Driver Status. Dump Data 2 contains the HBA Slot Number (ffffffff if unavailable).
Data:
0000: 000c000f 005c0002 00000000 c4000402
0010: 00000000 00000000 00000000 00000000
0020: 00000000 00000000 04010000 00444f46
0030: 00000003
===

The following is an excerpt of the SecurePath 4.0c for Windows Installation and Reference guide:

===
Event Id = 1026
Event Text
The Driver has detected a path failure to Subsystem ID "subsystemidentifier". Dump Data 0 contains the Phys Path Info < Port | Bus | Target | Lun >. Dump Data 1 contains the Driver Status. Dump Data 2 contains the HBA Slot Number ffffffff if unavailable).
Dump Data 3 contains extended Driver Status.

----

Description

The path identified in the longword at offset 0x28 of the data field of this message has been marked as a failed path by Secure Path.

The HBA slot number correlates the "port" in the above path information to the physical location in the server.

Other information provided is descriptive only to engineering.
===

When verifying all paths in SPM, they all check out fine, and I don't get the repair option.

Jeroen