This post is more than 5 years old
1 Rookie
•
88 Posts
0
16987
October 14th, 2017 04:00
Root partition full after ESXi 6.5 upgrade and MEM1.4 to 1.5 upgrade, ehcmd.log massive
Please can someone help?
24 hrs after a an ESXi6.5 upgrade and also upgrading MEM 1.4 to 1.5 we are receiving warnings about the root RAMdisk being full.
Further investigation reveals that the ECHMD.LOG is massive.
[root@esxi1:~] tail /var/log/vmkwarning.log
2017-10-14T08:51:20.082Z cpu31:65816)WARNING: VisorFSRam: 353: Cannot extend visorfs file /scratch/log/equallogic/ehcmd.log because its ramdisk (root) is full.
[root@esxi1:/scratch/log/equallogic] ls -lah
total 24400
d-wxrw--wt 1 root root 512 Oct 13 10:43 .
drwxr-xr-x 1 root root 512 Oct 14 08:42 ..
-rw-rw-rw- 1 root root 23.8M Oct 14 10:06 ehcmd.log
Other then deleting the log please can any suggest what might be causing this, is there a know bug in MEM1.5
Thanks in advance.
austin-t
1 Rookie
•
88 Posts
1
October 17th, 2017 06:00
The log file were examined by EqualLogic support and found to be clean.
I've blogged about this if anyone needs more details.
austintovey.blogspot.co.uk/.../ramdisk-full-after-esxi-65-upgrade-with.html
Origin3k
4 Operator
•
2.3K Posts
0
October 14th, 2017 04:00
1. Do have modified the location of scratch which is a requirement for certain installation (when esxi is not installed on "local" disks where disk not mean dual SD card or USB) . kb.vmware.com/.../1033696
2. If you have modfied the location of scratch can you check this because there is a known problem with ESXi right now about for not applying this configuration change.
Yes i have seen large ehcmd.logs earlier and it was never be a problem for us. Did you have take a look into the *.log (Maybe there is something wrong).
Regards,
Joerg
austin-t
1 Rookie
•
88 Posts
0
October 14th, 2017 04:00
Thanks for responding so fast.
I will raise a case with EQL support to check the log file over in the first instance.
Also in the MEM config file I noticed that the log doesn't roll until 50MBs which seems strange given the root RAMDisk is only 32MBs be default.
I'm happy to change the scratch location but wanted to make sure we didn't have a bigger problem first.
austin-t
1 Rookie
•
88 Posts
0
October 18th, 2017 04:00
It would appear that there is an issue with the /scratch partition with the Dell customized ESXi image.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2151209
We have applied the fix but now the /scratch/log/equallogic folder is missing!
austin-t
1 Rookie
•
88 Posts
1
October 19th, 2017 06:00
I wanted to share the fix that worked for us, and it looks like the Emulex driver in the image ISO was the problem.
1- Remove the Emulex drivers:
/etc/init.d/hostd stop
localcli software vib remove -n elxiscsi -n elx-esx-libelxima.so
2- Create a scratch folder on the desired datastore:
mkdir /vmfs/volumes/DatastoreName/DirectoryName
3- Configure scratch to point to that folder:
vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/DatastoreName/DirectoryName
4- Check if location was changed:
vim-cmd hostsvc/advopt/view ScratchConfig.ConfiguredScratchLocation
5- reboot ESXi host for changes to take effect