Morning everyone, I've been struggling to nail down this error 10 code that I'm getting on all of my hosts (3 ESXi in total). Everywhere i look it tells me that I'm running low on space but when I check the outputs on all the hosts there seems to be more than enough space available.
~ # df -h
Filesystem Size Used Available Use% Mounted on
visorfs 1.5G 324.2M 1.1G 22% /
vmfs3 499.8G 107.1G 392.6G 21% /vmfs/volumes/4ce1a8ee-814eb77e-1766-68b599e3df73
vfat 285.9M 140.7M 145.2M 49% /vmfs/volumes/3c3693e8-f77a642a-1910-5c6bdcb26d3a
vfat 249.7M 102.5M 147.3M 41% /vmfs/volumes/65092bef-de8a06b5-22db-2bbbc32dc3d2
vfat 249.7M 103.7M 146.1M 42% /vmfs/volumes/ff060de6-cecc88e5-4d14-8726d7ed0132
vmfs3 499.8G 100.2G 399.6G 20% /vmfs/volumes/4ce1a92e-6c624d34-2cf3-68b599e3df73
vmfs3 499.8G 6.1G 493.6G 1% /vmfs/volumes/4ce1a909-d6b31dea-450f-68b599e3df73
vmfs3 499.8G 281.6G 218.2G 56% /vmfs/volumes/4ce1a8cf-9914f00c-7975-68b599e3df73
vmfs3 409.8G 204.8G 205.0G 50% /vmfs/volumes/4d5006ba-5fdcef08-6003-68b599e3df73
~ # vdf -h
Tardisk Space Used
SYS1 201M 201M
SYS2 55M 55M
SYS3 1M 1M
SYS4 12K 12K
SYS5 12K 12K
SYS6 42M 42M
SYS7 12M 12M
-----
Ramdisk Size Used Available Use% Mounted on
MAINSYS 32M 4M 27M 14% --
tmp 192M 4K 191M 0% --
updatestg 750M 64K 749M 0% --
hostdstats 78M 3M 74M 5% --
AAMconfig 128M 3M 124M 2% --
~ #
When I was looking over the VUM logs the only thing I can see that is intresting is;
* The host certificate chain is not complete.
[2011-02-23 09:38:59.652 02884 warning 'Libs'] SSLVerifyIsEnabled: failed to read registry value. Falling back to default behavior: verification off. LastError = 0
[2011-02-23 09:38:59.652 02884 warning 'Libs'] SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
[2011-02-23 09:38:59.652 02884 warning 'Libs'] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
vC and ESXi hosts are all up to date with 4.1u1 and I've also updated VUM and wasn't ggetting any problems before these updates.
Thanks
Hmmm - I've struck this same issue with ESXi running from USB/Embedded.
So can all ESXi hosts utilise the same scratch location, or should seperate folders be set for each host?
eg. /vmfs/volumes/Volume1/scratch_hostname
Cheers
Each host must have their own scratch partition. What I did is just picked a datastore with plenty of free space then created the scratch directories for each esx host using the mkdir command to create scratch1 then scratch2 etc to match up with the numbers of the esx hosts. Then when I edited the scratch locations I could point it to the appropriate directory. VMware has released the KB that was mentioned above it is here:
http://kb.vmware.com/kb/1037190
I have also seen people have a problem with being able to collect data and it is due to the same problem so although VMware does not state that it is required to have a scratch partition in my experience with embedded hosts it should be.
Hope that helps
Hanna
Thanks, the "mkdir -p /tmp/scratch/var/tmp" method is fine and save the scratch setting needed reboot
I'm away on training until 5th May. Please contact afterhours on 0800 654 193 if your request is urgent.
We are experiencing this problem as well. We've installed ESXi on 1GB SD cards. The proposed solution does resolve the issue. Can this problem also be resolved by using a larger SD card?
Peter
Peter,
With a larger SD card you would be able to configure /store to a partition on the card. This may require manual configuration post-install. The answers & steps needed probably vary between Embedded ("installing" a dd image of ESXi onto the card) and Installable (booting the install CD and having it setup the card). It can probably be done with a "kickstart" install; I've never played with those so I don't know for sure.
The ESXi engineers are somewhat wary of putting /scratch on any sort of flash media. ESXi is designed to minimize writes to its boot medium, as it may be flash. Anything expected frequent writes is placed on /store, which by design is intended to be on a storage device with no write cycle limits.
Because the flash hardware industry has been working on improving write lifetimes, this caution may no longer be significant. The design was done at a time when 1GiB USB memory sticks were sort of high-end and expensive. Perhaps someone who has followed the flash industry closely can comment on then-vs-now write cycle sustainability.
(One thing that ESXi does not do is write balancing to the flash media. There are logical hotspots in the filesystems stored on flash; these addresses within the flash will eventually burn out unless the storage medium itself does transparent write balancing.)
>Bela<
Thanks for your reply. That does make a lot of sense. I can understand there would be concern about using an sd card as scratch storage.
I am hesistant to use the knowledge base fix because it seems I'd then need to manually manage that configuration across all our hosts. It doesn't seem to be something that would be manageable through host profiles since the folder needs to be manually created and the path needs to be unique to each host.
What are the implications disabling scratch completely?
Peter
Peat, I beleive i can remember that on ESXi 4+ without scratch, AAM agent reserve memory space for it’s own swap (to replace the uwswap file).
I guess you would have problem to generate vm-support too
Envoyé : jeudi 5 mai 2011 00:21
À : Raphaël SCHITZ
Objet : New message: "VUM Scan Host - The host returns esxupdate error codes: 10"
VMware Communities<http://communities.vmware.com/index.jspa>
VUM Scan Host - The host returns esxupdate error codes: 10
reply from Peat<http://communities.vmware.com/people/Peat> in VMware vCenter™ Server - View the full discussion<http://communities.vmware.com/message/1748749#1748749
The above mentioned kb article finally discusses a patch, released April 28th.
Looks like we can put this issue to bed by applying.