I was troubleshooting storage related problems at a customer site for some time. We run into massive ESXi storage connection problems after installing a new array. Interestingly enough problems occurred on already existing storage a few hours after new array was installed. Because searching for root cause took some time, I thought it is worth to share.
I am in the middle of a troubleshooting scenario. It is about connection problems from ESXi hosts to their storage devices. Normally everything works fine but at from time to time, there are tons of errors on HBAs in hosts. Therefor I want to watch HBA errors in ESXi hosts with PowerCLI.
These days I had to troubleshoot a problem in a vCenter environment. A few VMs shown with absolute path to vmx file in vCenter inventory. Normally this occurs when a ESXi boots with no connection to its previous mounted storage volumes. VMs located on these volumes are shown like this in inventory. But this wasn’t the case here: VMs were running and no host was […]
These days I had to update a ESXi host using vCenter Update Manager (VUM). Environment is managed by a vCenter 6.7 appliance with embedded VUM. The host I got the error is managed by vCenter but not member of any cluster. After attaching a upgrade-baseline and running the compatibility check, I got the error that vCenter Update Manager cannot copy files to the host.
Most often installing PowerCLI is no problem. Sometimes there is a PowerShell error when accessing PowerShell gallery. Like now: Just wanted to install PowerCLI onto a new Windows 10. When running the command find-module vmware* I get this error(s): Fortunately I found a solution quickly here. Problem is related to security protocols used in PowerShell. Check current protocols by running: My Windows 10 showed this […]
I want to share the solution of flooding errors I had after an vSphere upgrade. Errors are probably not connected to upgrade. The problem I got flooded by errors for VMFS datastores in log files. Errors in /var/log/vmkernel.log: 2020-01-29T14:06:00.311Z cpu8:2099233)WARNING: Fil3: 8175: Found invalid object on 59c4eb22-52356382-42b5-5cb90195e9c0 expected 2020-01-29T14:06:00.311Z cpu8:2099233)Vol3: 3374: Failed to get object 28 type 3 uuid 59c4eb22-52356382-42b5-5cb90195e9c0 FD 8029c4 gen 3 :Not […]
It is not uncommon to get errors after a host update/upgrade you didn’t see before on the host. The following error could be seen as an example of errors with the same cause. The error I did an upgrade of a 6.5 host (installed with HPE ESXi image almost 2 years ago) to the latest HPE ESXi image of 6.7 U3. After final boot the […]
Recently a customer noticed that all his vCenter Server Appliances (VCSA) running 6.7 U3 (188.8.131.52000 respectively 6.7 build 14368073) do not send any data to syslog server any more. Rebooting VCSA or restarting service gets the system to send data again – for a few minutes. Changing syslog-settings in Appliance Management (VAMI, Port 5480) also brings VCSA to send logs for a few minutes. VMware […]
Normally when using a self-signed certificate you get a warning. It is also normal to accept the certificate to continue your task. These days I wanted to register a 3PAR system as storage provider in vCenter. Because of a certification error, this could not be accomplished. In this post I describe how to solve – at least my – problem.
In an environment I saw this error when backup creates VMware snapshots of three VMs: Warning message on VM on host in datacenter. The guest OS has reported an error during quiescing. The error code was: 5. The error message was: ‘VssSyncStart’ operation failed. IDispatch error #8723 (0x80042413) Facts about the environment: Versions: ESXi version: 6.7.0, 13981272. Guest: Windows Server 2019. VMware tools: 10346 (10.3.10). […]