KVTAYLOR
Contributor
Contributor

Patch stage fails lack of space

I'm trying to stage patches on an ESX that has been upgraded from 3.0 on. Now when I try to stage paches and upgrade it tells me I do not have enough space.

My /Boot is at 76 percent, and the rest are all low percents.

what files can I remove out of the /boot that will help.

I have no need to go back to 3.x so I know that I should be able to delete some .

any help would be appreciated.

0 Kudos
5 Replies
Jain
Hot Shot
Hot Shot

What about vSphere/vCenter server ? Does it have enough free space ?

Once I came accross similar kind of issue, It was caused due to low free space at vSphere/vCenter server

Cheers,

~ Jain

~ Do not forget about points,if you found answer useful

--------------------------------- *Jain* | VCP4 | +Please award points, if you found answer useful+
0 Kudos
DSTAVERT
Immortal
Immortal

ESX requires a minimum of 10GB to install. ESX 4 is different than earlier releases in that the COS is now a regular VM on a datestore.

-- David -- VMware Communities Moderator
0 Kudos
AndreTheGiant
Immortal
Immortal

As written before you need space on the / filesystem and then on a local VMFS datastore.

What's the output of vdf -h command?

See also the upgrade guide for more info:

http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_upgrade_guide.pdf

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
KVTAYLOR
Contributor
Contributor

There is plenty of space on the VCenter server, as both the C: and 😧 have over 50G of free space

here is the vdf -h on the esx

Filesystem Size Used Avail Use% Mounted on

/dev/sdg5 4.9G 1.7G 2.9G 37% /

/dev/sdg2 2.0G 63M 1.8G 4% /var/log

/dev/sdd1 99M 72M 23M 76% /boot

/dev/sdd3 7.7G 1.5G 5.9G 21% /esx3-installation

/dev/sdd1 99M 72M 23M 76% /esx3-installation/boot

/dev/sdd6 5.8G 102M 5.4G 2% /esx3-installation/var/log

/vmfs/devices 740G 0 740G 0% /vmfs/devices

/vmfs/volumes/2e9982c5-879f6307 1.1T 511G 571G 47% /vmfs/volumes/System Admin

/vmfs/volumes/4806ed25-f42372c4-0395-001aa00d1b7c 2.0T 1.5T 509G 74% /vmfs/volumes/Isan1

/vmfs/volumes/487dd6aa-04d4caf8-3cb9-00151724537a 2.0T 1.5T 413G 79% /vmfs/volumes/SAN1

/vmfs/volumes/48e1e41f-9d5b5560-6129-00221908552a 635G 8.5G 626G 1% /vmfs/volumes/vert4:storage1

/vmfs/volumes/4970a4fc-0c39e420-1f32-00151724537a 1.3T 815G 521G 61% /vmfs/volumes/SAN2

/vmfs/volumes/498cec8e-72b5ad2a 1.1T 511G 571G 47% /vmfs/volumes/Software

/vmfs/volumes/4a32a4aa-d46057ba-1ae2-00151724532a 2.0T 1.3T 713G 64% /vmfs/volumes/FCSan3-1

/vmfs/volumes/4a32a805-6eee8883-7959-00151724532a 1.3T 652G 722G 47% /vmfs/volumes/FDSan3-2

0 Kudos
AndreTheGiant
Immortal
Immortal

You partitions seems fine.

Sorry no other idea.

Try to do not stage the patches and simple remediate the hosts.

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos