hp proliant dl140 g2 pci-x 64/133 external scsi:  "expansion rom not initialized" in bios post, can't find windows driver

reverendalc
reverendalc used Ask the Experts™
on
i have an HP dl140 g2 1u rackmount server.  it's an excellent machine, but i'm having this issue:  upon boot, it states
expansion rom not initialized - pci mass storage controller on bla bla bla...
press f1 to continue or f10 to setup

if i press f10, the bios clearly states that all (both) pci-x slots are enable and whatnot
if i press f1 to continue, the server boots just fine, but i can't determine a windows driver to suit the device.  windows home server 2011 identifies the device as a mass storage controller, but auto update immediately declines providing a driver.  i've tried downloading several drivers and architectural variations of those drivers listed as cards compatible with the dl140 g2.  device manager reads PCI\VEN_0E11&DEV_AE10&SUBSYS_40320E11&REV_03
 on the hardwareID.  a google of that only yields one result of an event log from somebody's server.

the card itself reads COMPAQ 2CH LVD/SE SCSI ARRAY CNTRLLR or something to that effect.  i've traced that back to a few different LSI drivers, none of which worked.  one reported installing correctly, but upon reboot threw a "device could not start" error.

i previously had an escalade 9800s sata raid controller for an 8 drive JBOD export, but now i'm attaching an HP storageworks MSA20, which requires the external scsi port.  this pci-x dual channel vhdci scsi controller was included with the server, and is full size.  most HP documentation refers to a single channel low profile in slot 2.

at any rate, i recently switched up from a DL380 G3, and between server downtime and SEVERAL drives not being hosted, any help resolving this issue is greatly appreciated!

connor
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2014
Commented:
>HP storageworks MSA20, which requires the external scsi port

MSA20 requires a Smart Array controller 641/642 or 6402/6404 to act as the HBA. Although it uses its internal RAID engine when connected to anything but an MSA1500 it still won't work on anything else. It uses high logical unit numbers that other cards can't deal with if I remember correctly.

Author

Commented:
The msa20 spec sheet states otherwise. In fact, in my online research I've encountered people using a variety of interfaces, including adaptec scsi controllers.  The underlying issue however, is that my server can't or won't initialize this card.
Top Expert 2014

Commented:
Quickspecs say this "NOTE: The MSA20 in only supported with the Smart Array 642, 6402 and 6404" so where do you get "the spec sheet says otherwise"? Also please point out one single URL with someone using a MSA20 on an Adaptec card; I can list dozens where people have failed to get it working.
11/26 Forrester Webinar: Savings for Enterprise

How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.

Top Expert 2014

Commented:
Drivers for your card are at the following URL (ignore the photo, it's wrong). Still don't think it'll be able to support a MSA20 even though it is a Smart Array controller.

 http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?lang=en&cc=us&prodNameId=348789&taskId=135&prodTypeId=329290&prodSeriesId=374785&lang=en&cc=us

Author

Commented:
I'll have to recheck the URL bookmarks when I get home, but I found (before purchasing the msa20) a picture tutorial of somebody connecting an msa20 to a dell poweredge with an adaptec scsi controller.  I have a compatibility matrix which indicates out of the box compatibility with over a dozen different hp servers equipped with various controllers outside of the aforementioned sets.

The wealth of vague and sometimes contradictory information available across the hp servers and web is what's causing me the most confusion.  I have in fact been using the stock image of the card to decide whether it was the appropriate driver or not, so I truly appreciate that link and look forward to installing the proper driver, as that's the very first piece of the puzzle.

I will report with the other resources I've found when I return from work. In the mean time, thanks for all of your input!

Connor
Top Expert 2014

Commented:
They probably typo'd - connecting a MSA30 to an Adaptec controller is as easy as pie, not so a MSA20 though.

Author

Commented:
Well that certainly is a depressing likelihood it seems. Although, MSA20 aside, I'll be thrilled to get this scsi controller working nonetheless. It'll at least give me the opportunity to TRY and make it work, as well as shave 30 seconds off of my boot time.

The "expansion rom not initialized" error I receive during POST, how can I rectify that?  I read that the DL1xx series do not support smartstart, and I don't see an option in the bios to specify a driver or rom for it.

Thanks

Connor
Top Expert 2014

Commented:
Not sure about the "expansion rom not initialized" message, the SA 3200 controller you've got ought to work in most servers if it was connected to a SCSI JBOD such as the MSA30 rather than an MSA20. Have to sleep on that one, g'night.

Author

Commented:
i doublechecked the resources i had cited earlier, and...  he started with an adaptec scsi controller, and then somewhere in the middle, mentioned switching to an HP controller 6400 series.  d'oh.

that being said, $36 and a few days later, i've installed my SA6404 and have established a link with my MSA20.

i'm still getting that PCI expansion ROM not initialized error during post, and there are some virtual LUNs showing errors in device manager, but it's working despite.

thanks for everything!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial