A vSphere administrator is performing maintenance on a group of ESXi 5.5 hosts when an error message displays indicating that the ramdisk is full. The two hosts reporting the problem were deployed wit

Auto Deploy hosts boot entirely from the network and store runtime data including log files in a volatile ramdisk with limited capacity. Redirecting host logs to an NFS store using the vSphere Syslog Collector or configuring the Syslog.global.logDir advanced setting offloads log writes from the ramdisk to persistent network storage, immediately relieving the space pressure and preventing recurrence.

Disabling System Logs through the DCUI would eliminate log data needed for diagnostics and troubleshooting; it is not a supported or recommended resolution and does not address the underlying storage design issue.

Decreasing the maximum log file size reduces future log growth but does not free the space already consumed on the full ramdisk, so it does not resolve the current full-ramdisk error condition.

The ramdisk on an Auto Deploy host is a virtual memory construct that cannot be physically moved to an SSD drive; Auto Deploy stateless hosts do not use local disk for the ramdisk.