1 2 Previous Next 21 Replies Latest reply on Mar 5, 2020 5:57 AM by UCL

    Upgrading ESXi 6.5U2 to ESXi 6.7U1. Completes Upgrade.  Insufficient ramdisk space but ScratchConfig.CurrentScratchLocation is configured and persistent.

    UCL Novice



      Using HPE 6.7U1 image "VMware-ESXi-6.7.0-Update1-10302608-HPE-Gen9plus-670.U1." on a ESXi 6.5U2 Host with a "HPE-ESXi-6.5.0-Update2-iso-Gen9plus-650.U2." 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 ?




        1 2 Previous Next