VMware Cloud Community
iamphane
Enthusiast
Enthusiast

do not have enough space on esx boot partition

Hello

      when i upgrading ESX 4.1 to ESXi 5.0 getting an error that  do not have enough space on esx boot partitiont o store the upgrade image"

how to resolve this issue .

Reply
0 Kudos
10 Replies
nielse
Expert
Expert

Have you tried freeing some space on the specific server?

More information can be found in this kb.

@nielsengelen - http://foonet.be - VCP4/5
keiooz
Enthusiast
Enthusiast

What about try removing some files that hold no more value to your system?

Reply
0 Kudos
iw123
Commander
Commander

How much space to you have? Could you log onto the server through tech support mode and type 'df -h' to show disk usage. 

*Please, don't forget the awarding points for "helpful" and/or "correct" answers
iamphane
Enthusiast
Enthusiast

its having only 25 MB space

Reply
0 Kudos
patrickds
Expert
Expert

How are you upgrading?

With Update Manager, you require 300MB on the boot partition to temporarily store the upgrade image;

If you use the CD, this is not necessary, and you can upgrade with a smaller boot partition.

Check the installation and upgrade guide for exact space requirement.

25MB is really very little, is that the complete boot partition, or only the remaining space?

Reply
0 Kudos
iw123
Commander
Commander

What are you booting off? local disk? usb? san ? 

*Please, don't forget the awarding points for "helpful" and/or "correct" answers
Reply
0 Kudos
iamphane
Enthusiast
Enthusiast

25 MB is remaining free space,

so shall i proceed for CD migration is that space is enough but i read in upgrade guide saying that migration requires 50MB /boot space but its total or free no idea.

if i do with CD installation all my server configurations like netwok ,vLan will be there or it will become like fresh installation

as per upgrade document esx i has a fecility that we can migrate from esx 4.1 to esxi 5.0 without changing our old configuration(NW,vLan,etc)

Reply
0 Kudos
iamphane
Enthusiast
Enthusiast

Local disk

Reply
0 Kudos
MauroBonder
VMware Employee
VMware Employee

read this kb, will help with your problem http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100356...

*Please, don't forget the awarding points for "helpful" and/or "correct" answers. *Por favor, não esqueça de atribuir os pontos se a resposta foi útil ou resolveu o problema.* Thank you/Obrigado
Reply
0 Kudos
patrickds
Expert
Expert

The 50MB space requirement is on the local vmfs partition, not /boot.

Upgrading with update manager requires about 350MB free space on /boot, because it will copy the entire installation image into it.

Upgrading from CD will first backup the current /boot (which is probably why you need the 50MB space on vmfs)

I performed an upgrade on hosts that had already been upgraded from 3.5 to 4.0 before, and that only had 250MB /boot partitions.

Default /boot on a clean installation is also about 250MB.

The actual boot image isn't that big, i think less than 50MB, so i'm not sure how much is actually required for /boot.

I would just try the upgrade, and if your /boot isn't big enough the installer will tell you.

In that case you will have to do a new installation, and redo the configuration.

If you have several hosts, you could install and configure the first, create a host profile, and then install the others and apply the profile to them.

This saves you from having to reconfigure all your hosts from scratch.

Upgrading from ESX to ESXi 5 with the CD will keep your configuration (unlike with the vi3 to vSphere 4 upgrade), only some custom firewall and service settings will be lost.

Service console is converted into vmkernel management port.

Watch out if you currently have vmkernel port groups in the same subnet as your Service Console, having multiple vmkernels in the same subnet will cause issues, and is not supported. (you could end up with NFS storage traffic going over your management port, for example)

Reply
0 Kudos