VMware: vSAN Disk Group Cache Drive Dead or Error (VSAN Absent Disk)

Summary:
A cache disk failed in my host taking along with it the disk group.  This is expected behavior, but for some reason, the disk group also disappeared from GUI so I couldn't decommission the disk group to basically replace the cached drive.  So, had to do it through powercli/esxcli.  Wish I took a screenshot, cause it was kind of annoying.

PowerCLI Example:
<#
Author: K. Chris Nakagaki
Source: tech.zsoldier.com
Use at your own risk, simply listed here for demonstration purposes to use how you see fit.
#>
<# Get the host w/ problem disk group #>
$VMhost = Get-VMHost NameofHostwithProblemDiskGroup
<# ESXCLI Connection #>
$VMHostCLI = $VMHost | Get-ESXCLI -V2
<# Find your problem disk group UUID, in this case I'm looking for a disk group that doesn't exist (blank) #>
$BadDisks = $VMHostcli.vsan.storage.list.invoke() | Where-Object {$_.vsandiskgroupname -eq ""}
<# Your capacity disks should all have the same vSAN Disk Group UUID, we're just confirming it here. #>
$BadDiskGroup = $BadDisks | Select-Object -Unique -Property vsandiskgroupuuid
<# This should return only one assuming you only have one bad disk group, if more than one, then you might have more issues. #>
$BadDiskGroup
<# Below is destructive, only do it if you are ABSOLUTELY sure of what you are doing #>
$vmhostcli.vsan.storage.remove.invoke(@{"uuid"=$BadDiskGroup})

Once you've deleted the offending disk group, you can now create a new disk group utilizing the replaced cache disk and former capacity disks.

Comments

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

VMware | AVS: Content Library or Non vCenter objects on VSAN produces unassociated but valid objects

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.