Hello
I’ve many ESX 4.1 already in production.
Now, due a new auditory request, I must create a new disk partition and mount the /home on it.
Currently the servers are partitioned as follows:
Mount point | Type | Size |
---|---|---|
swap | 1.60 GB | |
/ | ext3 | 15.0 GB |
/var | ext3 | 4.00 GB |
/tmp | ext3 | 4.00 GB |
Service console size: 29.61 GB
Local hard disk size: 70 GB
So, there is enough unused disk space available.
How can I accomplish this request, without reinstalling ESX?
Thanks and best regards.
Hi,
Maybe this site could be of help to you:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=930
Greetings,
Arjan
Hello Arjan, thank you for your timely response.
The KB that you pointed me seems to be exactly what I’m looking for.
But, it is intended for:
Product Versions:
VMware ESX 2.0.x
VMware ESX 2.1.x
VMware ESX 2.5.x
Since the SC in ESX 4.1 resides in its own virtual disk, do you think that I can use the same procedure than ESX 2.x?
Best regards.
Sorry you're totally right....
Thinks it's time for me to go to sleep 😉
Maybe before I go to bed something to make up for my mistake 😉
Hope this helps you more?
Best regards
you can create new partitions and asign more size for those, like you can have for /usr, /var etc.....but I dont think so you can utilize all the space using this because you have to create the partition and then copy the exhisting files to them.So, the last partition what you would do will be left with the sizes. check how you have created your ESX partitions, i dont think so you would have used ldm to do that. this is the only possible way to accomplish your problem.
Maybe this one can help also:
http://www.virtuallyghetto.com/2011/01/how-to-increase-capacity-of-varlog-on.html
Hope you'll be able to solve your problem 😉
Best regards,
Arjan
Hello Arjan.
I was verifying the link you sent me, but I’m not sure if it applies to my situation. As far I understand that procedure is for an ESXi host with a vMA running on it.
Although that configuration is pretty similar to an ESX 4.1 host, the procedure requires to shutdown the vMA and to work directly from the ESXi. I think that isn’t possible to be done within an ESX host.
But that article gave me some clues to find two possible solutions:
It seems to me that those are my only options, now. They are pretty ugly, so I’m not sure about them.
I’ll try to test them; I hope not to have to reinstall the ESX servers
Thanks and best regards.
I totally see your point, but I think you don't have another option 😞
Make sure you backup all possible data and hope for the best...
Hope all will be well.
Greets,
Arjan
shedule a stop and refresh installation. in my opinion is the best solution.
and check this link with best practices of partiotioning vsphere ESX. If you need, increase space when you need.
http://vmetc.com/2009/07/22/best-practices-for-vsphere-esx-4-service-console-partitions/
good luck
Other than a reinstall there isn't a supported method. A non supported host would probably fail that same auditing. If this is about users having local acces why not disable all local access and use the vMA appliance for maintenance. http://vmware.com/go/vma At some point you will need to start since ESX classic is gone as of the next version.
Hello.
Thank you for your all your interesting answers. I think I’ll try extending the virtual disk of the Service Console.
Even when that isn’t a supported procedure, if everything goes well I think the server will look exactly the same than a fresh installed server (so, auditors won’t know about the little trick ).
The other option (adding a new vmdk) will result in an unusual server configuration.
If I don’t have success, I’ll need to reinstall the servers .
Thank you again.
Best regards.
I would run this by the auditors so you don't compound the problem and need to do everything twice. If nothing else heavily document the procedure.