<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>esod on vNinja.net | VMware, VCF &amp; Homelab</title><link>https://vninja.net/authors/esod/</link><description>Recent content in esod on vNinja.net | VMware, VCF &amp; Homelab</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy; 2010 - 2026 &lt;b&gt;vNinja.net&lt;/b&gt; &lt;br/&gt; &lt;em&gt;There is a thin line between agile and fragile&lt;/em&gt;</copyright><lastBuildDate>Sat, 18 Jul 2026 14:11:50 +0200</lastBuildDate><atom:link href="https://vninja.net/authors/esod/index.xml" rel="self" type="application/rss+xml"/><item><title>Upgrading to ESXi 7.0 build 18426014 U2c. ESXi stuck in Not responding from vCenter</title><link>https://vninja.net/2021/08/24/upgrading-to-esxi-7.0-build-18426014-u2c-esxi-stuck-in-not-responding-from-vcenter/</link><pubDate>Tue, 24 Aug 2021 00:00:00 +0000</pubDate><guid>https://vninja.net/2021/08/24/upgrading-to-esxi-7.0-build-18426014-u2c-esxi-stuck-in-not-responding-from-vcenter/</guid><description>Well, not directly related to the new ESXi 7 U2c build, BUT if you're one of the lucky ones (like me), you've been experiencing big issues with SD/USB device since ESXi U1/U2, hence the vCenter &lt;&gt; ESXi (at least the configurations, tokens, etc.) has not been working for a while. I mean, last time vCenter talked successfully with my host was back in May 2021, when the USB dropped. That's like four (4!) months ago.
Today, VMware finally released the ESXi 7 U2c, which has included an updated module for the **vmkusb**. Hopefully this will fix the previous experienced SD/USB device issues, but before that - let's talk patching!</description></item><item><title>ESXi 7.0 SD Card/USB Drive Issue Temporary Workaround</title><link>https://vninja.net/2021/06/01/esxi-7.0-sd-card-issue-temporary-workaround/</link><pubDate>Tue, 01 Jun 2021 00:00:00 +0000</pubDate><guid>https://vninja.net/2021/06/01/esxi-7.0-sd-card-issue-temporary-workaround/</guid><description>&lt;b&gt;This is a guest post by Espen Ødegaard:&lt;/b&gt; As VMware has not released a fix yet (regarding issues with SD card and USB drive), I'm still experiencing issues with [ESXi 7.0 U2a Potentially Killing USB and SD drives](https://vninja.net/2021/05/18/esxi-7.0-u2a-killing-usb-and.sd-drives/), running from USB or SD card installs. As previous workaround (copying VMware Tools to RAMDISK with option `ToolsRamdisk`) only worked for 8 days (in my case), I needed something more permanent, to get the ESXi-hosts more stable (e.g. host being able to enter maintenance mode, move VMs around, snapshots/backup, doing CLI-stuff/commands, etc.).</description></item><item><title>Searching vCenter Tasks and Events via PowerShell and GridView</title><link>https://vninja.net/2021/05/19/searching-vcenter-tasks-and-events-via-powershell/</link><pubDate>Wed, 19 May 2021 00:00:00 +0000</pubDate><guid>https://vninja.net/2021/05/19/searching-vcenter-tasks-and-events-via-powershell/</guid><description>&lt;b&gt;This is a guest post by Espen Ødegaard:&lt;/b&gt; As searching and filtering for events in vCenter Server trough vSphere Client somewhat limited (OK, it really sucks, to be honest), it's usually much faster using PowerCLI, to retrieve, filter &amp; searching events.</description></item><item><title>ESXi 7.0 U2a Potentially Killing USB and SD drives!</title><link>https://vninja.net/2021/05/18/esxi-7.0-u2a-killing-usb-and.sd-drives/</link><pubDate>Tue, 18 May 2021 00:00:00 +0000</pubDate><guid>https://vninja.net/2021/05/18/esxi-7.0-u2a-killing-usb-and.sd-drives/</guid><description>&lt;b&gt;This is a guest post by Espen Ødegaard:&lt;/b&gt; After upgrading my 4-node vSAN-cluster (homelab) to ESXi 7.0 build 17867351 U2a, I detected that ESXi had issues talking to the USB device, where the ESXi was installed. I found a related KB from VMware, outlining issues with the new VMFS-L, which started my baseline for troubleshooting [VMFS-L Locker partition corruption on SD cards in ESXi 7.0 (83376)](https://kb.vmware.com/s/article/83376)
In short, it says that the VMFS-L partition may have become corrupt, and a re-install is needed. **There is no resolution for the SD card corruption as of the time this article was published**</description></item><item><title>ESXi: Error Occurred While Saving Snapshot Msg.changetracker</title><link>https://vninja.net/2021/05/18/error-occurred-while-saving-snapshot-msg.changetracker.mirrorcopystatus/</link><pubDate>Tue, 18 May 2021 00:00:00 +0000</pubDate><guid>https://vninja.net/2021/05/18/error-occurred-while-saving-snapshot-msg.changetracker.mirrorcopystatus/</guid><description>&lt;b&gt;This is a guest post by Espen Ødegaard:&lt;/b&gt; I recently ran into a strange issue in my home lab, **running ESXi 7.0.2, build 17867351** where Veeam Backup &amp; Replication v10 reported the following error: Failed to create VM snapshot. Error: CreateSnapshot failed, vmRef vm-4013, timeout 1800000, snName VEEAM BACKUP TEMPORARY SNAPSHOT, snDescription Please do not delete this snapshot. It is being used by Veeam Backup., memory False, quiesce False</description></item></channel></rss>