Hi,
We have a Proliant ML350 G6 with two datastores on RAID1 volume. (One datastore on 300GB RAID1 volume, and the other on 146GB disks.)
One datastore has about no space left so we ordered two extra 600GB disks. We brought down the esxi server and then added the disks and created a logical volume (+/- 550GB) in tha raid controller.
Client told me that the server hung on restarting (tried three times). +/- 3/4 in the bootprocess (he did not write up the last message he saw)
I will be going onsite this weekend there but was wondering what went wrong.
Will upgrading to 5.1 fix the problem? Not sure why it hangs, any tips?
I do not know what that "3/4 of boot-process" means, but if your client added new logical drive, did he check in bios that this drive is now by chance not the one system wants to use for boot-up?
hi Jarry,
thank you for your answer. I ment 3 quarters into the esxi boot proces, so it passes all post messages somehow esxi hangs during bootup. hen we delete the logic drive in the raid controller esxi boots with no trouble.
Hi,
I have a query >It passes all post messages "somehow esxi hangs during bootup" .Do you know the exact step at which it got hung?If you have a screen shot,please do post the same.
i dont have one atm, will try to reproduce the problem this weekend and come back at this. If any1 else experienced such behaviour please share in the mean time.
okay here I am again, today i planned to go with that guy of that esxi hosts to go to a seminar. Offcourse disaster struck and het got a call all was down there, perfect I thought ![]()
So we drove there and the vm was stuck, when killing it and rebooting it we got a message that the datastore was full and the pagefile could not be enlarged. I checked the details of the VM and saw it was overcommit by about 150GB. Datastore had 16GB free at the moment. I brought the host down, we recreated the extra logical raid volume and booted up the server waiting for it to get stuck.. It didn't.
After that i just issued copy / paste from the datastore browser for the vmx and vmdk's. Then removed the old machine from inventory and added the copied vmx file. When bootting up i answered i moved it so that i didnt had to reactiviate windows (had no idea if it was oem licensed or not). And the vm seems to be running fine now.
So i have no idea what happened the first time when i wasn't there and everything was hanging when the new logical raid volume was created. So before closing this I'd like to see if i can get some more input.
