Windows OS Hub
  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu

 Windows OS Hub / Virtualization / VMWare / System Logs on ESXi Host are Stored On Non-Persistent Storage

November 1, 2019 VMWare

System Logs on ESXi Host are Stored On Non-Persistent Storage

When you install VMware ESXi to an SD card or USB stick (or when using Boot from SAN), the yellow exclamation mark icon is displayed next to the host name in the vCenter client console, and the following warning appears on the Summary tab:

System logs on host ny-esxi21.woshub.com are stored on non-persistent storage.

warning: System logs on vmware esxi host are stored on non-persistent storage

The esx.problem.syslog.nonpersistent warning means that the system writes logs (scratch) to the non-persistent USB device and if you restart your host, they won’t be saved. Thus, in case of any host issues, you won’t be able to examine its logs or provide any data to VMWare technical support team. To remove the warning, you must change the log storage path to a local disk or a VMFS datastore (or configure a syslog server) in the ESXi host settings.

This guide refers to the new HTML5 vSphere 6.7 client. In previous vSphere versions it is configured in the same way, however, the names of options or sections may differ.
  1. Open the vSphere client and select your ESXi host with the warning in the Hosts & Clusters;
  2. Go to the Configure tab and click Advanced System Settings; Advanced System Settings in ESXi
  3. In the list of advanced settings, click Edit and type Syslog.global.logDir in the Filter field. As you can see, [] /scratch/log folder is used to store the ESXi logs; Syslog.global.logDir /scratch/log
  4. Change the path in the Syslog.global.logDir variable to [youtVMFSdatastorename] /systemlogs. set Syslog.global.logDir path to vmfs datastore
    You must create /systemlogs folder on the VMFS datastore in advance. Otherwise, you will get this error: A general system error occurred: Internal error. systemlogs folder on persistent vmfs datastore
  5. If the Syslog.global.logDir field is empty, check the value of the ScratchConfig.CurrentScratchLocation parameter. It shows the path to the scratch partition containing logs.

You can also change the log path using the PowerCLI command prompt:

get-vmhost ny-esxi21 | Get-AdvancedSetting -Name "Syslog.global.logDir" | Set-AdvancedSetting -Value "[HQVMFSDatastore1] /system_log_folder_name"

You can also change the value of Syslog.global.logDir using the Host Profiles. You can apply this profile to all ESXi hosts in your datacenter.

set Syslog.global.logDir via ESXi Host profiles

4 comments
4
Facebook Twitter Google + Pinterest
previous post
How to Measure Storage Performance and IOPS on Windows?
next post
Managing Windows 10 Start Menu Layout and Taskbar Pin Apps With GPO

Related Reading

Unmounting an NFS Datastore from VMware ESXi

April 21, 2023

How to Increase Virtual Machine Disk Size in...

April 6, 2023

How to Install Free VMware Hypervisor (ESXi)?

January 24, 2023

Using VMware Converter for P2V Migration (Physical to...

October 19, 2022

Using iPerf to Test Network Speed and Bandwidth

September 29, 2022

Categories

  • Active Directory
  • Group Policies
  • Exchange Server
  • Microsoft 365
  • Azure
  • Windows 11
  • Windows 10
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • PowerShell
  • VMWare
  • Hyper-V
  • Linux
  • MS Office

Recent Posts

  • Configuring Event Viewer Log Size on Windows

    May 24, 2023
  • How to Detect Who Changed the File/Folder NTFS Permissions on Windows?

    May 24, 2023
  • Enable Single Sign-On (SSO) Authentication on RDS Windows Server

    May 23, 2023
  • Allow Non-admin Users RDP Access to Windows Server

    May 22, 2023
  • How to Create, Change, and Remove Local Users or Groups with PowerShell?

    May 17, 2023
  • Fix: BSOD Error 0x0000007B (INACCESSABLE_BOOT_DEVICE) on Windows

    May 16, 2023
  • View Success and Failed Local Logon Attempts on Windows

    May 2, 2023
  • Fix: “Something Went Wrong” Error When Installing Teams

    May 2, 2023
  • Querying Windows Event Logs with PowerShell

    May 2, 2023
  • Configure Windows LAPS (Local Administrator Passwords Solution) in AD

    April 25, 2023

Follow us

  • Facebook
  • Twitter
  • RSS
Popular Posts
  • ESXi: Slow Disk Performance on HPE Gen8
  • Windows Server Licensing for Virtual Environments
  • Invalid State of a Virtual Machine on VMWare ESXi
  • Match Windows Disks to VMWare VMDK Files
  • Configuring USB Devices Passthrough from VMWare ESXi to a Virtual Machine
  • Selecting the Number of vCPUs and Cores for a Virtual Machine
  • How to Enable and Configure SNMP on VMWare ESXi Host?
Footer Logo

@2014 - 2023 - Windows OS Hub. All about operating systems for sysadmins


Back To Top