MSA 1000 Disk Numbering in Windows 2000

[Doug Darnell]

Depending on when I power my MSA1000 up, determines how the disks are numbered in Windows 2000. For example, I power one of my cluster nodes up into Windows 2000 with MSA1000 powered off. DISK 0 is the mirror drive on the node. I then power the MSA1000 up and go into Disk management of node 1. I initialize the disks, and the MSA1000 takes Disk 1, Disk 2 and so on....which is what I assume to be correct.
However, when I boot node 1, with MSA1000 still powered on, the disks flop. Meaning the the MSA1000 takes Disk 0 and 1, and the disks on node 1 take the next number in line...disk 3.

My question is this...is this a problem?? And is there anything I can do to keep this from happening? HBA drivers??? Anything???

[Doug Darnell]

I'll reply to my original message since no one else seems to know. You have to load the MSA1000 v.6.51 version of the HBA driver....this fixes the issue.

[Uwe Zessin]

What a strange error!

In the early days of Secure Path (DEC equipment, SCSI storage and Windows NT) one could see in Disk Administrator that it did put its disks 'in front' of the locally attached system disk, but I don't recall I have ever seen this on Windows 2000.

A minor nit-pick, if you allow: V6.51 - isn't that the version of the MSA1000 software CD-ROM rather than that of the adapter driver?

[Doug Darnell]

UWE,

Yea, v6.51 of the MSA1000 has the emulex driver on it. Load it in Windows.