VMware ESXi 5.5 on HP DL380G5 server, help to expand datastore RAID 5 array on P400

We have an HP DL380G5 server with P400 RAID controller, running VMware ESXi v5.5 Hypervisor.  Originally it had (5) 146GB SAS drives connected, as a single RAID 5 array (with 541GB usable).  I plugged in 3 additional 146GB SAS drives.  The goal is to increase the size of the datastore (there is only 1 datastore, called "datastore1").  After doing some research, I increased the size of the array as follows:

     /opt/hp/hpssacli/bin/hpssacli controller slot=1 logicaldrive 1 modify size=max forced

and when displaying the "new" size:

     /opt/hp/hpssacli/bin/hpssacli controller slot=1 show config

it shows:

     logicaldrive 1 (956.9 GB, RAID 5, OK)

I believe this is all good......at least up to this point.  The problem is that (so I'm told) I now need to expand the actual datastore (as it is still showing as 541.75 GB), and I obviously don't know how to properly do it.  

When I look at the partition table:

     partedUtil getptbl /vmfs/devices/disks/vml.0000000000766d686261313a303a30

It returns the ending sector as 1146734896 (which it also shows the ending sector of the "vmfs" partition to be.  I believe this number is incorrect.  I believe it is the OLD ending sector.  I believe the number SHOULD be 1720099632, as I have another identical server (that has had 8 of the same drives.....from its original installation), and it shows 1720099632 as the ending sector.

I'm told that I need to use the following to resize the datastore partition, however, I don't want to type in this command until I know that the actual partition has the sectors that I'm pointing it to:

     /partedUtil resize "/vmfs/devices/disks/vml.0000000000766d686261313a303a30" 3 10229760 1720099632

Then, so I'm told, I need to also do the following:

     vmkfstools --growfs /vmfs/devices/disks/vml.0000000000766d686261313a303a30:3 /vmfs/devices/disks/vml.0000000000766d686261313a303a30:3

and I really don't understand that one, as it appears that the 2 items are actually the same.

Any suggestions?
Who is Participating?

Improve company productivity with a Business Account.Sign Up

adk001Connect With a Mentor Author Commented:
as it turns out.........the problem was resolved by rebooting the host (again).  after that, everything works fine!
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
the easiest way is to re-install, or install to USB/SD card, and you will not have this issue.

partedUtil can be tricky to use, and dangerous to use, if you ge the wrong command and syntax.
adk001Author Commented:
Please pardon my ignorance, however, I don't understand.  What am I supposed to install to a USB/SD card?  My problem is with the internal RAID array that is supposed to be approximately 956GB, but is only showing as approximately 541GB.  I need to add that additional storage space to the datastore.  Since the maximum number of sectors doesn't show the additional space, I have no way to add those (unseen) sectors to the datastore.
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

Paul SolovyovskySenior IT AdvisorCommented:
What hancoccka is referring to is blowing away the current datastore and installing a usb drive to install ESXi on.  Afterwards you can use the entire p400 array for the datastore.

Another way to do this is if you to load load the smart start disk in and use is to expand the raid set, typically I perfer have the BBWC installed just in case.  Afterwards you go to the datastore properties and choose to expand the datastore.
adk001Author Commented:
The thing is......the logical drive is already expanded (956.9GB).  It even shows as 956.9GB when looking at it via the HP offline RAID management utility (hpssacli) from within VMware (via SSH into the VMware host).  Unfortunately, when looking at VMware's native methods (either command line via partedUtil, or via the VMware Client), it shows up as 541.75GB.  I'm not sure exactly what's screwed up, however, I don't believe it's the P400 RAID.  I believe it properly expanded the RAID array (logical drive / logical volume).  I believe that something in VMware isn't "refreshing", and therefore isn't recognizing that it has expanded.  The idea of running the ESXi host from a USB stick is absurd.  Would it be to regain the storage used (in order for the datastore to have the entire drive)?  If so, it's meaningless, as we're talking about nearly 1TB here.  If a few (certainly a 1-digit number) of GB is "wasted" in the overhead of the host operating system.....it isn't enough to worry about.  By the way, the BBWC is installed & reporting as "OK" (in the hardware status on the client).
Paul SolovyovskySenior IT AdvisorCommented:
You can use this kb to do this.


 What happens when you click on properties of the datastore than manage? On the upper left you should see an option to expand the datastore.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
did you expand the RAID, and then Expand the Logical Disk (two operations)

do you have virtual machines on this datastore?

have you got complete backups before we proceed and mangle your partitions?

(this is not easy!).

This was an EE post, where I explained it's used before


(the asker gave up and went for a reinstall!)

So please let me know how you want to proceed, the issue for your information, is that ESXi has been installed on the same disk. e.g. the OS resides on the same disk as the datastore.

also run fdisk, what does it state the size is?
adk001Author Commented:
the reason for accepting my own comment as the solution is that it is the solution.  the other advise wasn't completely relevant as I had already tried what some suggested, and, didn't accept having to completely blow away the RAID array & create a new one.....as that obviously wasn't necessary (by the fact that it all works now, and I actually did NOTHING, other than reboot the host 1 more time).
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.