HPE EVA Storage

MSA1000 with FCA2101 (LP950) on w2k3

New Member

MSA1000 with FCA2101 (LP950) on w2k3


We have migrate from windows 2000 server to windows 2003 server R2, and after the change we cant see part of data on ultra-scsi disks mounted on raid5.....

Our server is a proliant dl360 g2 (bought on 2000). This server has an emulex lp950 that when server boots appear lp950 and on widows appear lp952 and is denominated by HP FC2101....the drivers installed on server are the following:
Model: LP952
Description: emulex light pulse lp952 2 Gigabit PCI fibre channel adapter
Driver version:5-5.30A2;HBAAPI v.2.2b, 02-17-05
Firmware version: 3.93A0

This FCA2101 target communicates with MSA1000
Controller version:5.30
MSA20 Version:2.08
Fan Control Module Version: N/A
Driver windows:

The problem is that we can access data of a one logical unit, but the other appears like empty under windows 2003 server....

We´ve tried to update all the drivers and firmware but nothing of this fix it.

Can anyone help us?????

Bill Costigan
Honored Contributor

Re: MSA1000 with FCA2101 (LP950) on w2k3

An empty LUN (i.e., a disk of 0 bytes)is often a symptom of a non-accessible LUN. The server can see it but cannot access it.

I would first check the MPIO software to see if the LUN is trying to be accessed from the wrong controller. I don't know if the MSA 1000 has active/active controllers or not.

If they have active/passive controllers you might be successfully getting to one LUN through the active controller and you are trying to access the second LUN through the passive controller.
Uwe Zessin
Honored Contributor

Re: MSA1000 with FCA2101 (LP950) on w2k3

On the MSA1000 it is not possible to access a logical disk through the standby controller You can see the alternate paths, but cannot do I/O through them. As soon as you attempt to bring it online (START UNIT), a failover happens, this controller will become the active one and all logical disks will 'fail over' to it.
Phillip Thayer
Esteemed Contributor

Re: MSA1000 with FCA2101 (LP950) on w2k3


Make sure youy are running on Windows 2003 R2 x64 version.

Make sure you install the correct drivers for the MSA1000 (http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=377751&prodNameId=3302289&swEnvOID=1060&swLang=8&mode=2&taskId=135&swItem=MTX-4235abb9c27b43eb8a39a86648 ) Also make sure you have the correct driver for the HBA (http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=439556&prodNameId=315735&swEnvOID=1005&swLang=8&mode=2&taskId=135&swItem=co-38377-5 ).

Once these are installed you should be working. If not check back here and let us know.

Once it's in production it's all bugs after that.
Martin Smoral
Trusted Contributor

Re: MSA1000 with FCA2101 (LP950) on w2k3

If you can see one lun but not the other, then i would say maybe the drivers are ok. For a test, if you have extra disk space or a extra disk to put in the msa, how about create a new lun, present it to the server and see if it works. If it does, then it sounds like the empty lun might be corrupt.
New Member

Re: MSA1000 with FCA2101 (LP950) on w2k3

Hi to everybody,

After testing, we decided to change the Emulex lp950 target to another server with same features, as we believe that the operating system could be confuse with drivers....

We install the following driver on the emulex target:

SCSI Miniport Driver for Windows 2000 and Windows Server 2003 (32 bit) Version 5-5.20a10 (303756.exe).

Once this is done, through HP tools like ACU.... Now, we are able to see the msa100 and two logical drives mounted on raid5.

But the problem persits, that is to say, we can access one of them (F: \), but the drive (E: \) still appears as empty in the Disk Manager ....

After more tests, and observing the display of the MSA1000 controller (only have one) receive the following error in two Ultra3 SCSI disk (drive E:\ -mounted on raid5- is composed of Ultra320 SCSI and Ultra3 SCSI disks)

"Bad drive firmware 85 BOX # 1, BAY 2 and 9"

My question is, can it be that the firmware between disks and controller are incompatible and therefore the information is inaccessible?

Would it be enough to update the firmware of the disks?

Through a recovery software we see all the information contained on the disks, so that the information is not lost ....