cawn
Enthusiast
Enthusiast

The ramdisk 'root' is full.

Hello

After en updragd from ESXi 4.0 to ESXi 5.0 we are getting an error on one of the host.

The error is: The ramdisk 'root' is full. As a result, the file /var/run/vmware/tickets/vmtck-5267e096-22ef-cf could not be written.

We get the error when we want to open a console to a guset.

We haved looked af the KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=200155... and that is not the problem.

What can this bee? and How can we fix is?

0 Kudos
9 Replies
VTsukanov
Virtuoso
Virtuoso

Hi

You need to clean up disk space.

Try to identify large directory

du -x / | sort -rn | more

and large files

find / -size +1024k -exec du -h {} \; | less

Take a look at vmware kb Investigating disk space on an ESX or ESXi host for information about deleting unnecessary files.

Usually it is sufficient to remove old log files and clear the tmp directory

0 Kudos
cawn
Enthusiast
Enthusiast

Hello

And thanks for the answer. the replay from Wmvare support was.

This is a know issue. Ther is a bug opened for this: root ramdisk full because wtmp file consumes all the space. Currently the workaround is to delete the /var/log/wtmp file. The fix for this is aimed for 5.0 U2

0 Kudos
AndreTheGiant
Immortal
Immortal

Interesting... the file /var/log/wtmp on my ESXi 5.0 U1... (as also does not exist the last command)

Are you sure of the name of file?

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

Hello, yes the name is correct. our ESXi 5.0 is a upgrade, maby there is at diffneters.

0 Kudos
AndreTheGiant
Immortal
Immortal

Upgrade from ESX?

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

nop, ESXi 4.0

0 Kudos
AndreTheGiant
Immortal
Immortal

Still strange... but maybe possible (I don't remember if was used).

If you can rebuild your host probably you fix this (and maybe more) un-needed files.

To backup and restore the config you can use:

http://www.vmware.com/support/developer/vcli/vcli41/doc/reference/vicfg-cfgbackup.html

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

Glad I came across your post, this is exactly what was causing my issue.  I had migrated a VM from one host to another then couldn't power it on.  If I moved it back to the original host it would.  Deleting the wtmp did the trick.

0 Kudos
gajuambi
Enthusiast
Enthusiast

If you are using hp servers then please have a look at his downloadable fix

http://ambitech.blogspot.com/2013/04/ram-disk-full-for-esxi-on-hp-servers.html

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15...

---------------------- Gajendra D Ambi [pardon my chat lingo]
0 Kudos