Host rebooted after completing an ESXi upgrade.
Skyline vSAN object health alarm in vSAN cluster.
A disk group reports its unhealthy/unknown under Cluster -> "Configure" -> "vSAN" -> "Disk Management"
Skyline health also reports "Disks with issues" under "Physical disk" -> "Operation health"
Deduplication and compression enabled on the disk groups/unknown
vSAN 7.x
vSAN 8.x
In /var/run/log/vmkernel.log we see logging indicating an issue adding one dedup device when initializing the disk group.
####-##-##T##:##:##.###ZZ cpu##:2099731)WARNING: PLOG: DDPInitDev:7454: Skipping dedup formatting of device t10.NVMe____######_####_#############_______________###############:2
####-##-##T##:##:##.###ZZ cpu##:2099731)WARNING: PLOG: PLOGDedupInitDev:9976: Unable to add dedup device ########-####-####-####-############# :Failure
####-##-##T##:##:##.###ZZ cpu##:2099731)WARNING: PLOG: DDP_Init:7788: dedup init expected 4 devices got 3
####-##-##T##:##:##.###ZZ cpu##:2099731)WARNING: PLOG: PLOGDedupInit:10015: Init DG failed for SSD ########-####-####-####-############# :Not ready
When attempting to mount the disk group it fails to mount with the below message/Error:
"The mount attempt failed after some time with : unable to mount : Disk with vSAN UUID <vSAN Disk Group UUID> Failed to appear in LSOM"
Allow vSAN objects to rebuild on other disks groups in the cluster.
Recreate disk group to bring the disk group back online and bring the host back into the cluster.
-Put affected ESXi host in vSAN maintenance mode.
-Delete Disk groups on affected ESXi host.
-Re-create Disk group as a new Disk group.
-Take host out of maintenance mode.
If this does not resolve the issue, please open a Support Request with Broadcom Support.