VmWare ESXi, Unable to Increase Volume with available storage.

chilemoore
chilemoore used Ask the Experts™
on
Quite a few months ago I added Storage to my shared storage device (HP MSA1000) from 558GB to 838GB.  The process on the MSA device went well.  My ESXi 4.0 (4.0.0, build 171294) host can see the additional capacity but I’m unable to Increase the volume capacity from the 558GB.  The Increase button on the SAN properties is always grayed out.  I’m tried stopping all the VMs and going into maintenance mode, rebooting the host but no luck.  Any suggestions?  

I have attached a screen shot of the SAN Prosperities as well as the path information.  Any suggestions are welcome.

Thanks.
 ESXi SAN Properties ESXi SAN Path
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2010

Commented:
If you notice in your 1st screen shot, a block size of 2MB, max file size 512GB. To increase your datastore, you need to change that to at least 4MB (which has a max of 1TB storage). But, to change your block size requires you to remove then re-add your datastore which, if you do that, removes/deletes your VMs. So, before doing so you'll have to move your VMs to some other storage temporarily until you've re-added your datastore, then you can move them back and re-add the VMs to Inventory.

Regards,
~coolsport00
Top Expert 2009

Commented:
coolsport00, fyi datastore size has nothing to do with vmfs block size but datastore size is limted to max vmfs volume size, block size only limit the max file size on the datastore, ever wonder how you can create >256GB datastore with 1MB block size?

chilemoore, did you upgrade the esxi4 from previous ver?

-vExpert 2010

Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
I don't think it's a block size issues.

Did you create another LUN or extended current LUN?

Do a screenshot of your datastore..go on onto the ESXi host and go to storage.  If you added an extent it's two differnt physical LUNs in a logical VMFS datastore using an extent.

Top Expert 2010

Commented:
Thanks Ryder/Paul...hmm...could it be permissions? I assume he's logging in with root though. And Paul...I guess I'm not understanding what you're suggesting? I think he added storage to the MSA from what he wrote in his orig post. If that is the case, are you suggesting that there is another datastore to be added and not a datastore extention? That sounds logical...

Regards,
~coolsport00

Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
From what I read it is already showing a 838GB VMFS partition so it looks like an extent has been added with a second LUN but until we see the storage screenshot we wont know for sure..that's my take.
Top Expert 2010
Commented:
I think the "Increase" button will only allow you to add additional extents to an existing volume (As opposed to utilizing more space on the same volume). To do what you wish, there are a couple solutiions>

1. Go back to your SAN and shrink the volume to its original size, then add the new space as an additional extent. At that point the "Increase" button should be functional and allow you to add space to your volume.

2. Move all of your data off the existing volume, then delete and re-add the volume utilizing all of the space.

Good Luck
chilemooreVP of Information Technology

Author

Commented:
I appreciate the quick response.  To answer your questions:

-       I original upgraded this ESXi host from 3.5 to 4.0.  I had added the storage and expanded the LUN in version 3.5 and per VMWare’s support I upgraded to version 4.0 which should have resolved the problem.  I also then went back to 3.5 per their request with no avail so I went back to 4.0.  Last I spoke to them I was told to make sure all activity on the LUN  (SAN) was stopped, but my support contract ran out before I could bet back to them, though I’m in the process of renewing, adding some more hosts so trying to see what the best deal is on licensing at the moment.
-      Paulsolov, as stated above I extended my current LUN.  
-      Coolsport00, I’m logged on as root, so it shouldn’t be permissions.  
-      Bgoering:  I have pondered that option but at the moment I do not have sufficient storage to move it all off and recreate the store.  If I was sure that the extend would work, I could reduce the size of the LUN, create new storage with the drives, move the data over and recreate the LUN, add the data back, expand the LUN and cross my fingers and hope the extend works now..  Hmm..  

DataStor-View.jpg
Top Expert 2010

Commented:
If you can afford the downtime you could use Veeam FastSCP to backup your VMs to a big USB drive on your workstation, then delete and readd the datastore, then FastSCP them back. It will be a bit slow though... And you do need to power down the VMs before you SCP them off.
Top Expert 2009
Commented:
As suspected, could be partition issue after you've upgraded the esxi3.5 as i've seen this problem before...but it rarely happens
Try to login to "unsupported mode" and observe the partition table with fdisk -l
Need to check if the free space is contigous or not

-vExpert 2010


chilemooreVP of Information Technology

Author

Commented:
Ryder0707, Sorry I haven’t updated this post.  Here is the screen shot of the Fdisk –I command.  The fiber channel storage device is disk naa.600143800008baa06e80b05ae0cf0003

Fiber-Attached-Disk--MSA1000-.jpg
chilemooreVP of Information Technology

Author

Commented:
Hey experts any other recomendations.  ESXi 4.1.0 is available.  I normally wait some time for any bugs to get worked out but if this may correct the issue I may give it a try.  At the moment I don't have sufficient storage to copy my VM servers off the host SAN and reformat but may need to do that.
Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
I have it in production, runs fine..joined my esx hosts to the domain..cool stuff.

Commented:
I am having the same issue. I am running ESXi 4.0.0 (build 261974) on an IBM S series Blade Center. I have a small volume on the fiber connected SAN that I extended from 150gbs to 215gb. I go into Disk Properties under the configuration tab to "increase..." the total capacity to take advantage of the additional 65gbs and no go. The "Increase..." button is grayed out.  I have tried rebooting the host, deleting the snap shots, restarting the management agents and entering maintenance mode and trying it all again. It doesn't seem to matter if the guests are powered on or off. I even unmounted and remounted the disk. So if anyone has any suggestions, that would be great.
chilemooreVP of Information Technology

Author

Commented:
delegats:  Have you reformated the entire drive?  I have scheduled some down time in 2 weeks, so I will know then.  I may try VMWare support again see if they can figure anything out.

Commented:
No I haven't. I did contemplate running up a whole new Datastore in an effort to resolve this issue.
Top Expert 2010

Commented:
I have been unable to replicate the issue in my virtualized ESX 4.1 testing environment. Never was able to get it to the point where the Increase button was greyed out.
chilemooreVP of Information Technology

Author

Commented:
I was on the phone yesterday with VMWare support and they were also perplexed.  I'm sending them a dump to see if they can determine what is causing the issue.  The only possibility is that the store was damaged back in version 3.5.  
Top Expert 2010

Commented:
Well I am glad I am not the only one perplexed :)

Let me know what they say.
chilemooreVP of Information Technology

Author

Commented:
VM support suggested I move the data off and delete the lun and recreate from scratch.  

Commented:
Wow that is helpful. Thanks VM Support!
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
That's because they don't like recommending the use of Extents. Only in extreme circumstances if you have no other options, like cannot turn on VM, because of space, or snapshot issue, and need a quick workaround and fix.

If you do not like the VMware Support Response you've got from VMware Support, I would suggest you escalate it to their Regional Escalation Manager, and have them Escalate the case to Level 3 - Engineers (unless they have already investigated the problem). Their Level 3 Escalation Engineer's are often kept in the dark away from phones/email and customers, unless requested.
Top Expert 2010

Commented:
"VM support suggested I move the data off and delete the lun and recreate from scratch."

I got to admit - that would PROBABLY work - wonder why I didn't think of that :)
chilemooreVP of Information Technology

Author

Commented:
Hey thanks for the response.  I did escalate a ways up, but I think the best solution is what I have planned, to move the data off and rebuild.  I will be doing this in a few weeks so I will update once the process has completed.  

Thanks.
chilemooreVP of Information Technology

Author

Commented:
Hey experts.  Well finally I was able to schedule a weekend for maintenance.  Shut down my VMs, backed them up and also copied the files off the server.  I then deleted the store and recreated it and now it recognizes all my storage space.

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