Link to home
Create AccountLog in
Avatar of Darrell Kirby
Darrell KirbyFlag for United States of America

asked on

Vmware ESX - HP Storage - MSA 2100

I have added a Direct attached MSA 2100 Enclosure to my ESX 4.1 server. I can see the HBA but the Storage view states that the storage is 0. It does post at server bootup. I also configured it for RAID 5 in the Storage setup for the Storage Array P812 Adapter. Is there a way to format the disk on ESX so that the disk appear? Is this all I need to do?
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

If the click Add Storage, do you get a LUN to format?
Avatar of tiago_aviz
tiago_aviz

Basically the steps are:
1- Create an array (on HP ACU)
2- Create a logical drive (on HP ACU)
3- In vSphere Client, -> configuration -> storage, You need to create a datastore so ESXi can format it and use it.

When formatting, take care of the block size. The default 1MB block will allow you to create VMDK file only as big as 256gb. If you need bigger VMDKs, increate the block size to 8MB.
Also do not create a raid array larger than 2TB which is the Max for 4.1
Avatar of Darrell Kirby

ASKER

I do not get a LUN to format. The storage does not appear in order to create a Datastore. No Storage to choose from.
The attached is what I get.
Storage.docx
if you click Add Storage what do you get?

have you create the Array using the Smart Start CDROM?
This 0.00GB LUN is the management LUN that you use for in-band management.

Meaning that you haven't created a LUN on HP Array Configuration Utility, just the Array itself.
ASKER CERTIFIED SOLUTION
Avatar of Darrell Kirby
Darrell Kirby
Flag of United States of America image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
See if the following youtube video help you: http://www.youtube.com/watch?v=uLmP3akxCPk

Good Luck
The right version of Smartstart helped resolve this issue.