Link to home
Create AccountLog in
Avatar of LoopTj
LoopTj

asked on

How do I move the ESXConsole to the SAN so I can format the local storage with a 4MB block

I have a running ESX4 vcenter with two ESX hosts using vMotion. The ESXConsoles are vmdk files on the local storage. One of my servers has 1TB of local storage but a 1MB block size which limits the file size to 256GB. Here is the info I got from VMWare using the vmkfstools command:
 For ex: vmkfstools -i /vmfs/esxpublic/testvm2.vmdk /vmimages/testvm2.vmdk. and the link to this  
http://pubs.vmware.com/vi35/server_config/wwhelp/wwhimpl/common/html/wwhelp.htm?context=server_config&file=sc_appb.21.1.html 

I tried that and got the Lock File Error, I think its because the ESXConsole is currently running. I don't know much about VM but I can follow directions. How can I get the virtual image of the console moved to the SAN so I can format the local datastore with a 4MB block to use the 1TB for other files?
Avatar of cjrmail2k
cjrmail2k
Flag of United Kingdom of Great Britain and Northern Ireland image

move all of your VM's to another datastore, right-click on the 1TB datastore and delete it. Then re-add it and format it using 4MB blocks. Do you have a VM that has a single VMDK bigger than 256GB?
Avatar of LoopTj
LoopTj

ASKER

All the VM's that were on this 1TB datastore have been moved to the SAN. I will have a VMDK that is larger than 256GB once I can virtualize it. The datastore cannot be deleted because the ESXConsole is running as a VM on that datastore. I didn't create the VM environment, and don't want to delete the ESX server than have to re-add it to the vCenter and the SAN and add all the VM's its hosting. Since all the current VM's are in the SAN (except the console) I can stop them on the console afterhours to hopefully find a way to move the ESXConsole.vmdk file to the SAN so I can right-click, re-format.
ASKER CERTIFIED SOLUTION
Avatar of Paul Solovyovsky
Paul Solovyovsky
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
sorry  didnt know your host was also on the partition, not a good idea mate! I agree with paulsolov if this is the case
Avatar of LoopTj

ASKER

Thank you both for your quick responses! If the vm's running on the problem host (esx1) are too much for esx2 to run, can I still move them in a not running state, so the resources don't get used? Also, is there documentation on removing a host from the cluster and than recreating the whole thing? Will the esx installer allow me to create the 20GB partition and leave the remainder as unused space? Or should I use the HP Bios tools to format the locale storage into two logical drives? Then esx will see something like drive1 20GB drive2 980GB, and I choose to install esx to the 20GB drive.
you should be able to move the vm's as long as you have enough storage on esx2. Removing esx1 and reloading it should be pretty straight forward.
Avatar of LoopTj

ASKER

The VM's are already on the SAN (except the service console). I am concerned about the VM's ram and processors taking more resources than the second host has to provide. Also, since esx1 is attached to the SAN, if I have to reinstall the esx server will I need to reconfigure the SAN to connect to the newly created server?
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
The KB Article from VMWare gives several methods for changing the block size. We used the reformat method using the installer CD and it went quite well.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013210