In the events entries on one of my 3 hosts I am seeing numerous messages as shown below. Any ideas on what could be going on? I have ESXi installed on a 4GB SD card.
The ramdisk 'root' is full. As a result, the file /var
/run/sfcb/2ece905d-78cf-4300-9e5f-daa4fc2525-
97 could not be written.
error
4/1/2013 8:18:42 AM
corp-esxi1
Hi Sean.
Proabably Scratch partition is not configured.
Go through below articles and let me know how it goes.
http://blogs.vmware.com/vsphere/2011/04/scratch-partition-best-practices-for-usbsd-booted-esxi.html
http://blogs.vmware.com/vsphere/2011/09/booting-esxi-off-usbsd.html
All the best.
I actually did change the Advanced Settings Scatch to use my SAN instead of the SD card. Any other ideas?
But is it using the SAN actually ? you can check by running " ls -lrths / ".This will give info if it is using tmp or SAN for Scratch.
You should be seeing like below example, else it is using SD card.
~ # ls -lrths /
4 lrwxrwxrwx 1 root root 49 Mar 14 20:13 scratch -> /vmfs/volumes/5132af98-347c11c6-0cf1-000c29428399
4 lrwxrwxrwx 1 root root 23 Mar 14 20:13 productLocker -> /locker/packages/5.0.0/
4 lrwxrwxrwx 1 root root 6 Mar 14 20:13 locker -> /store
4 lrwxrwxrwx 1 root root 49 Mar 14 20:13 store -> /vmfs/volumes/5132af92-8b9dc5c4-37ae-000c29428399
4 lrwxrwxrwx 1 root root 49 Mar 14 20:13 bootbank -> /vmfs/volumes/f3ae687d-80b294fb-d2e9-075d260901ff
4 lrwxrwxrwx 1 root root 49 Mar 14 20:13 altbootbank -> /vmfs/volumes/3977b374-86d33850-6200-87f0c9546645
4 drwxr-xr-x 1 root root 512 Mar 14 20:47 etc
Yes, looks like it's pointing to the SAN,
296 -r--r--r-- 1 root root 293.0K Feb 18 06:32 bootpart.gz
24 -r-x------ 1 root root 23.0K Apr 1 15:15 local.tgz
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 vmimages
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 vmfs
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 usr
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 tardisks.noauto
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 tardisks
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 opt
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 mbr
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 lib64
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 lib
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 VIB
4 drwxr-xr-x 1 root root 512 Apr 1 15:19 bin
4 drwxr-xr-x 1 root root 512 Apr 1 15:22 var
4 lrwxrwxrwx 1 root root 63 Apr 1 15:22 scratch -> /vmfs/volumes/51154cdb-ae557cac-8262-ac162d74e71c/.locker-esxi1
4 lrwxrwxrwx 1 root root 22 Apr 1 15:22 productLocker -> /locker/packages/5.1.0
4 lrwxrwxrwx 1 root root 6 Apr 1 15:22 locker -> /store
4 drwxr-xr-x 1 root root 512 Apr 1 15:22 sbin
4 lrwxrwxrwx 1 root root 49 Apr 1 15:22 store -> /vmfs/volumes/504d3092-5b96339c-ea54-ac162d74e71c
4 lrwxrwxrwx 1 root root 49 Apr 1 15:22 bootbank -> /vmfs/volumes/014287e3-5f793d96-d1e9-7d7d6ee06f99
4 lrwxrwxrwx 1 root root 49 Apr 1 15:22 altbootbank -> /vmfs/volumes/c5b60fef-9199dbe1-7440-29d3a14b2d5d
4 drwxrwxrwt 1 root root 512 Apr 1 16:08 tmp
4 drwxr-xr-x 1 root root 512 Apr 1 16:30 etc
128 drwxr-xr-x 1 root root 128.0K Apr 1 16:41 proc
0 drwxr-xr-x 1 root root 512 Apr 1 16:41 dev
/vmfs/volumes/51154cdb-ae557cac-8262-ac162d74e71c/.locker-esxi1/core #
Hi Sean,
Sorry for the late reply, Can you follow below steps and post the results?
~ # stat -f /
File: "/"
ID: 100000000 Namelen: 127 Type: visorfs
Block size: 4096
Blocks: Total: 284128 Free: 169437 Available: 169437
Inodes: Total: 524288 Free: 521396
If you observe the Free Inodes are less then follow KB: http://kb.vmware.com/kb/2037798
Thank you for taking the time to respond!
I ended up speaking with support and they directed me to download an update for HP gen8 servers to address log rotation issues. http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=...
This did resolve the problems I was having.
Thanks very muh for sharing the resolution information. It is very useful.!!!!!
Mohammed
Hi Sean,
Glad to hear your issue is resolved. can you share the SR# for my reference ? Have a nice day.