VMware Cloud Community
phil210802
Contributor
Contributor
Jump to solution

Error Message

My ESX server keep's coming up with the following message when I am trying to make any configuration changes:

Error during the configuration of the host: Failed to lock: \etc\vmware\esx.conf: No space left on Device.

Any help would be appreciated.

Cheers

Phil210802

0 Kudos
1 Solution

Accepted Solutions
bertdb
Virtuoso
Virtuoso
Jump to solution

no, don't just delete anything. Everything that starts with /usr is important and system-related. Don't touch it.

Anything that starts with /root, /home, or /vmimages is usually not that important. You can search in those specific locations by running

find /root /home /vmimages -size +10000k

looking specifically for .iso files on that partition :

find / -xdev -iname "*.iso"

View solution in original post

0 Kudos
15 Replies
bertdb
Virtuoso
Virtuoso
Jump to solution

It looks like your root filesystem is full.

log on to the service console, run "df", and tell us if there are partitions showing 100% usage (or close).

Then run "find / -size +10000k"

which will give you a list of large (>10MB) files. If you give us that list, we might be able to give you a list of files to delete. If you have large files in /vmimages or /home, those are the first candidates.

bertdb
Virtuoso
Virtuoso
Jump to solution

by the way, you're talking about /etc/vmware/esx.conf, not \etc\vmware\esx.conf. The service console (and all other unix variants) use "/" as path separator, not "\" like windows does.

phil210802
Contributor
Contributor
Jump to solution

after running "df" the following file has come up showing its at 100%

/dev/cciss/c0d0p2

When I run the "find / -size +10000k" I get loads of files, can I try and sort out the above first to see if that fixes the issue??

Also thanks for pointing out the / mistake, i'm a Windows sys admin and not had hardley any experience with Unix (Sopose its about time I learnt).

Cheers

Phil210802

0 Kudos
fatih
Enthusiast
Enthusiast
Jump to solution

If you have done any patching or similar and have the source files left somewhere you can remove these first ...

Regards

0 Kudos
phil210802
Contributor
Contributor
Jump to solution

Haven't done any patching or similar.

Any other ideas?

Cheers

Phil210802

0 Kudos
bertdb
Virtuoso
Virtuoso
Jump to solution

no, don't just delete anything. Everything that starts with /usr is important and system-related. Don't touch it.

Anything that starts with /root, /home, or /vmimages is usually not that important. You can search in those specific locations by running

find /root /home /vmimages -size +10000k

looking specifically for .iso files on that partition :

find / -xdev -iname "*.iso"

0 Kudos
bertdb
Virtuoso
Virtuoso
Jump to solution

/dev/cciss/c0d0p2 is "/", I guess ?

0 Kudos
phil210802
Contributor
Contributor
Jump to solution

Yes

/dev/cciss/c0d0p2

is mounted on/in /

0 Kudos
phil210802
Contributor
Contributor
Jump to solution

When I run find /root /home /vmimages -size +10000k I get the following results:

/root/.vmware/HRPRO_C_Drive latest.vmdk (Which can be deleted)

/vmimages/tools-isoimages/linux.iso

/vmimages/tools-isoimages/windows.iso

When I run "find / -xdev -iname *.iso" I get the following results:

/vmimages/tools-isoimages/freebsd.iso

/vmimages/tools-isoimages/linux.iso

/vmimages/tools-isoimages/netware.iso

/vmimages/tools-isoimages/solaris.iso

/vmimages/tools-isoimages/windows.iso

0 Kudos
Rob_Bohmann1
Expert
Expert
Jump to solution

look in /temp

look for old log files that have rotated and can be safely deleted

what are your partition sizes? Did you accept the default partitions when you installed esx?

0 Kudos
phil210802
Contributor
Contributor
Jump to solution

Partition size is whatever the defaults for ESX are.

Is the easiest option just to re-install ESX server???

Cheers,

0 Kudos
bertdb
Virtuoso
Virtuoso
Jump to solution

ok, everything but /root/.vmware/... belongs to the system (it's how the vmware tools get installed in your VMs).

to delete that file

rm -f "/root/.vmware/HRPRO_C_Drive latest.vmdk"

0 Kudos
bertdb
Virtuoso
Virtuoso
Jump to solution

if you know how you filled up the root partition, it's much easier to undo that action. As you pointed out above, you backed up a large VM to the service console, which wasn't sized to hold such items. Get rid of those files....

0 Kudos
phil210802
Contributor
Contributor
Jump to solution

I have deleted HRPRO_C_Drive latest.vmdk

And it all seems to be fine now.

Points have been awarded to bertdb as he was the user who was the most helpful, although ALL of you did help.

Once again thanks for all your help.

0 Kudos
bertdb
Virtuoso
Virtuoso
Jump to solution

after you did this, you can investigate further:

cd /root/.vmware

ls -al

to see what else is in that directory, and what else you might want to remove.

0 Kudos