• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 830
  • Last Modified:

New ESX 3i Install - Connect to Existing MSA 500 Storage

In a test environment, I created a CentOS / VMWare server system that had VMs running off a mount on HP MSA 500 storage.

I deleted the CentOS server and installed VMWare ESX 3i.

I want to connect to the VMs on the HP MSA 500 storage but cannot. I see an option in the Infrastructure Management Client to add storage but will delete everything on the existing MSA 500 storage.

When I SSH to the ESX server, I can see the storage (vmhba2 is the MSA 500 storage):

#### Begin ####
~ # esxcfg-mpath -l
IDE CDROM vmhba0:0:0 /vmfs/devices/genide/vmhba0:0:0 (0MB) has 1 paths and policy of Fixed
 Local 0:31.1 vmhba0:0:0 On active preferred

Disk vmhba1:0:0 /vmfs/devices/disks/vmhba1:0:0:0 (69455MB) has 1 paths and policy of Fixed
 Local 2:1.0 vmhba1:0:0 On active preferred

Disk vmhba2:0:0 /vmfs/devices/disks/vmhba2:0:0:0 (173658MB) has 1 paths and policy of Fixed
 Local 10:1.0 vmhba2:0:0 On active preferred

~ # esxcfg-vmhbadevs
vmhba1:0:0     /vmfs/devices/disks/vmhba1:0:0:0
vmhba2:0:0     /vmfs/devices/disks/vmhba2:0:0:0
~ # fdisk -l

Disk /dev/disks/vmhba2:0:0:0: 182.0 GB, 182094643200 bytes
255 heads, 32 sectors/track, 43585 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes

                 Device Boot    Start       End    Blocks   Id  System
/dev/disks/vmhba2:0:0:1             1     43585 177826784   fb  VMFS

Disk /dev/disks/vmhba1:0:0:0: 72.8 GB, 72829501440 bytes
64 heads, 32 sectors/track, 69455 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

                 Device Boot    Start       End    Blocks   Id  System
/dev/disks/vmhba1:0:0:1             5       750    763904    5  Extended
/dev/disks/vmhba1:0:0:2           751      4845   4193280    6  FAT16
/dev/disks/vmhba1:0:0:3          4846     69456  66161280   fb  VMFS
/dev/disks/vmhba1:0:0:4   *         1         4      4080    4  FAT16 <32M
/dev/disks/vmhba1:0:0:5             5        52     49136    6  FAT16
/dev/disks/vmhba1:0:0:6            53       100     49136    6  FAT16
/dev/disks/vmhba1:0:0:7           101       210    112624   fc  VMKcore
/dev/disks/vmhba1:0:0:8           211       750    552944    6  FAT16
#### End ####

Please see the attached screenshots.

Is there a way to open the VMs located on the MSA 500 storage?

  • 3
2 Solutions

The only way you can open these servers is if you install CentOS to another server and then give the storage to this CentOS. Then you have to configure NFS under ESXi and mount the storage over NFS from the freshly installer CentOS. You maybe must run also the VMWare converter to convert these machines to ESX format.
If you want to use VMFS3 then you have to manually copy these servers to another location and format you storage to VMFS3 and then use VMWare converter to convert VM-s from Vmware Server format to ESX format
When you used the VMware Server to bring your VMs, the file system they used were native File System and not VMFS3 File System which the ESX/ESXi Hosts use.

As Mesik2pp has suggested, if you want your ESXi to power on your VMs, then check whether this works

1.Add a VMKernel Port Group and use NFS option to create a new vSwitch and make sure that the HP MSA 500 Storage Device is accessible from the ESXi Host.

2.Rescan your Storage Arrays

3.Check whether you are able to look up your VMs after the rescan.
Jeremy_in_JapanAuthor Commented:
Thank you for your advice. I will give it a try.

What I was trying to do was copy-a-copy of a VM from production into our test environment to test a database restore. The VM was running under ESX and had snapshots applied so that is why I zapped the CentOS and installed ESX, thinking that I could just open the VM.

I am not familiary with configuring VMKernel Ports but I found this document which has pointed me into the right direction:

Jeremy_in_JapanAuthor Commented:
kumarnirmal - Unfortunately, I was not able to see the VMs.

Since this is a test environment, I will just zap the array and copy the VM again. Thanks to the both of your for your advice and pointing me in the right direction.
Jeremy_in_JapanAuthor Commented:
Thank you again for your help.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now