Ds2300 and cluster system with HP L3000

[WilliamSmith11]

Hi
I have a cluster system with two Hp L3000 500 MHz and two DS2300, in the attachment is possible to see the scenario.
The configuration for the switch bank 1 in the DS2300 disk storages are
Switch 1 = off (â )
Switch 2 = on (0)
So is configured for a single bus,

The problem is:
The customer right now has five disks in each enclosure, the disk in the slot 5 of each enclosure is not configured, and he has bought four additional disks (A7285A REV HPC5);
One enclosure has hardware path 0/5/0 (installed in the slot 6 of the server) the other one hardware path 0/2/0 (installed in the slot 5 of the server).
When I insert the disks in the slot 6 and slot 7 of the enclosure with hardware path 0/5/0 and I use the Sam send me the following error message,
I donâ t have any disk inserted in the 0/5/0/11 position,

Could be this my problem?
Enclosure Addressing and SCSI IDs
The disk system has 14 available disk slots; SCSI addressing does not follow an .one-to-one. Relationship between slot positions and SCSI addresses. Slot assignments and SCSI addresses are shown below. In full bus mode, the SCSI address 7 is reserved for the host bus adapter. If more than one HBA connects to the disk system then a disk module must be removed from the slot that corresponds to the SCSI address of the additional host bus adapter. In split bus mode, slots 1 through 7 are on one bus and slots 8 through 14 are on the other bus.

Some idea?

The error that SAM utility send me is :
SAM was unable to determine the disk drive model of the disk drive attached to your system at hardware path 0/5/0/0.11.0. This device will be ignored.

If this unit is CD-ROM drive, check to see if there is any media (a CD-ROM disk) in the drive. If there currently is nomedia in the drive, you can correct this problem by inserting the desired media and choosing the "Refresh List"; from the "option" men

[Steven E. Protter · Accepted solution]

SAM was unable to determine the disk drive model of the disk drive attached to your system at hardware path 0/5/0/0.11.0. This device will be ignored.

This usually happens when a disk array is detected on a Fiber card with no LUN0 attached. The system detects the actual disk array and thinks its a disk.

Since it is not, the error message.

Solution:
Have the disk admin(you in this case) assign some disk to LUN0. This will stop the eerror.

Ignore it. Its not serious. It does trigger EMS alerts and that makes my management a lil jumpy.

SEP

[WilliamSmith11]

I have not a fiber card in this system, all are scsi card.

WS

[Steven E. Protter]

I've never seen this problem with SCSI, but that doesn't mean it can't happen.

ioscan -fnC ext_bus

Lets look for trouble.

Also recommend a visual check of the system. Make sure cables are secure, undamaged and devices are properly powered up.

SEP

[Gerhard Roets]

Hi William

SCSI-ID 7 is ussually used for the "initiator" which is your SCSI card. With SCSI jumped ID's is not a problem. Here is the SCSI ID priority list for your information from
HIGHEST ------------------->>>>LOWEST
7,6,5,4,3,2,1,0,15,14,13,12,11,10,9,8

With a cluster and shared storage you ussually have a second scsi card connected to the same bus(not always in the case of a DS2300). In that case you might get a SCSI ID conflict if the second adaptors id is set to 11 which is the same as a drive you just plugged in.

The simplest rememedy is just to remove the drive from that slot, and label it as having an ID conflict and putting the drive in the next available slot.

You have to look logically at your SCSI busses to see if this is the case.

If the above is not the case. Swap to of the new drives if they are unused still and see if the problem follows the change. If it does follow the change you might have a DUD drive.

HTH
Gerhard