Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 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

1 comment
1
Facebook Twitter Google + Pinterest
previous post
How to Measure Storage Performance and IOPS on Windows?
next post
How to Deploy Printers to Users/Groups/Computers with GPO?

Related Reading

FAQ: Live Migration of Virtual Machines with VMWare...

November 19, 2020

VMWare Error: Unable to Access a File Since...

October 1, 2020

How to Enable and Configure SNMP on VMWare...

September 7, 2020

Selecting the Number of vCPUs and Cores for...

August 18, 2020

Configuring USB Devices Passthrough from VMWare ESXi to...

August 12, 2020

1 comment

Arris July 14, 2020 - 7:18 am

When i configure this i get ‘A general system error occurred: Internal error’, so it is not working for me.
We use ESXi 6.7 with vCenter.
I tried:
[Vol1] /systemlogs
[Vol1]systemlogs
[Vol1] systemlogs
nothing is accepted and everything it will put back the original values.

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • Preparing Windows for Adobe Flash End of Life on December 31, 2020

    January 22, 2021
  • Checking User Logon History in Active Directory Domain with PowerShell

    January 22, 2021
  • How to Disable/Remove Thumbs.db File on Network Folders in Windows?

    January 21, 2021
  • MS SQL Server 2019 Installation Guide: Basic Settings and Recommendations

    January 19, 2021
  • USB Device Passthrough (Redirect) to Hyper-V Virtual Machine

    January 15, 2021
  • Windows 10: No Internet Connection After Connecting to VPN Server

    January 13, 2021
  • Updating the PowerShell Version on Windows

    December 24, 2020
  • How to Enable and Configure User Disk Quotas in Windows?

    December 23, 2020
  • Restoring Deleted Active Directory Objects/Users

    December 21, 2020
  • Fix: Search Feature in Outlook is Not Working

    December 18, 2020

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • How to access VMFS Datastore from Linux, Windows and ESXi
  • Adding Third-Party Drivers into VMWare ESXi 6.7 ISO Image
  • Invalid State of a Virtual Machine on VMWare ESXi
  • Windows Server Licensing for Virtual Environments
  • ESXi: Slow Disk Performance on HPE Gen8
  • VMWare vSphere: Managing Password Expiration Settings
  • Match Windows Disks to VMWare VMDK Files
Footer Logo

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


Back To Top