Hello.
Using HPE 6.7U1 image "VMware-ESXi-6.7.0-Update1-10302608-HPE-Gen9plus-670.U1.10.3.5.12-Oct2018.iso" on a ESXi 6.5U2 Host with a "HPE-ESXi-6.5.0-Update2-iso-Gen9plus-650.U2.10.3.5.5" the Update Manager reports it as Non-Compliant which correct.
But after the upgrade I have a 6.7 Host which reports as "Incompatible" due to "Cannot create a ramdisk of size 359MB to store the upgrade image. Check if the host has sufficient memory."
But I have set ScratchConfig.CurrentScratchLocation and it persists after reboots.
When I reboot the host after 6.7 the host revert to 6.5.
A vdf -h shows:
Ramdisk Size Used Available Use% Mounted on
root 32M 2M 29M 7% --
etc 28M 364K 27M 1% --
opt 32M 532K 31M 1% --
var 48M 632K 47M 1% --
tmp 256M 728K 255M 0% --
iofilters 32M 0B 32M 0% --
shm 1024M 0B 1024M 0% --
hostdstats 1303M 12M 1290M 0% --
snmptraps 1M 0B 1M 0% --
Is it actually the SD-Card which lacks space or what ?
/Peter
I think the problem was that "User defined partition" or something "partition" regarding the SSD disk was activated in the Servers BIOS so that two partions were on one SSD. That creates trouble for which partition to copy the new ESXi OS to and which partition to run it from.
Disabling that "user something I think partiion" cleared the situation.
/Peter
Here. This was the solution:
"
Turned out to be a HPE Embedded User Partition. Disable it as a Boot source and delete it in the server BIOS. That solves the problem.
Enabling or disabling the Embedded User Partition
https://support.hpe.com/hpsc/doc/public/display?docId=c04398276 page 60 Delete Boot Option.
/Peter
"