Hello,
I plan on doing an in place upgrade of ESX 2.5.3 and I'm concerned if I will have enough local storage space on the ESX server. The preupgrade script ran OK but I have been reading that I need to have 100MB for the /boot . I have the following:
size - Used - Avail - Use% - Mounted on
1.9G - 637M - 1.2G - 35% - /
45M - 18M - 25M - 41% - /boot
1.9G - 648M - 1.1G - 35% - /home
392M - 0 - 391M - 0% - /dev/shm
1.9G - 33M - 1.7G - 2% - /tmp
1.9G - 150M - 1.6G - 8% - /var
14G - 33M - 13G - 1% - /vmimages
Has anyone performed an upgrade from 2.5.3 to 3.0.1 with similar configuration?
Thanks
It has been my experience that the upgrade will fail with your /boot in it's current state.
The preupgrade script did not fail on this?
I don't think you're going to want to do the inplace upgrade with a 45M /boot partition. Plus the /vmimages partition isn't as necessary in 3.x so you might just have better luck with a reformat.
Sorry for the bad news.
The Upgrade script passed on three identical ESX 2.5.3 hosts with the same configuration. I think I better postpone my upgrade until I can figure out a safer way to get them upgraded. I have 26 VM's and 8 vmfs2 volumes. Some of my VM's have vmdk files on up to 4 different vmfs volumes... OS, Data Logs, Misc etc...
I don't have enough storage to Vmotion/Dmotion all my servers to another location. Anyone have a good idea how to get this thing upgraded?
Thanks
