2024-03-06T22:57:53.736Z Wa(180) vmkwarning: cpu124:2099922)WARNING: LSOM: LSOMOutOfLogical:12361: Throttled: cp 4194304 cu 0
ou.0:2024-08-12T05:13:06.039Z Wa(180) vmkwarning: cpu102:2101296)WARNING: Service: XLogAllocateVDisk:1111: no space left in XLog registry - 2097172 2097152
vmkernel.0:2024-08-12T05:16:47.204Z Wa(180) vmkwarning: cpu52:2109598)WARNING: Service: XLogAllocateVDisk:1111: no space left in XLog registry - 2097172 2097152
vmkernel.0:2024-08-12T05:13:06.039Z Wa(180) vmkwarning: cpu102:2101296)WARNING: Service: VirstoCreateVDiskV4:1528: Create failed, status=Limit exceeded
vmkernel.0:2024-08-12T05:16:47.204Z Wa(180) vmkwarning: cpu52:2109598)WARNING: Service: VirstoCreateVDiskV4:1528: Create failed, status=Limit exceeded
2024-08-22T21:51:29Z In(14) vsandevicemonitord[2101901]: Device eui.01000000000000005cd2e4db0a545551 state is DISKGROUP_UNDER_REPAIR
2024-08-22T21:51:29Z In(14) vsandevicemonitord[2101901]: Device 522215ac-e8ce-39c0-79c7-b51bb8120bb5 not found.
2024-08-22T21:51:29Z In(14) vsandevicemonitord[2101901]: Device eui.3656323054a065140025384500000003 state is DISKGROUP_UNDER_REPAIR
2024-08-22T21:51:29Z In(14) vsandevicemonitord[2101901]: Device eui.3656323054a043630025384500000002 state is DISKGROUP_UNDER_REPAIR
2024-08-22T21:51:29Z In(14) vsandevicemonitord[2101901]: Device eui.3656323054a028980025384500000002 state is DISKGROUP_UNDER_REPAIR
2024-08-22T21:51:29Z In(14) vsandevicemonitord[2101901]: Device eui.3656323054a029570025384500000002 state is DISK_UNDER_REPAIR
2024-08-22T21:51:29Z In(14) vsandevicemonitord[2101901]: Device 5230aae8-b72d-69d9-9662-0fb477253767 not found.
2024-08-22T22:05:49Z In(14) vsandevicemonitord[2101901]: Unmounting succeeded on VSAN diskgroup with Cache tier : eui.01000000000000005cd2e4db0a545551.
2024-08-22T22:05:49Z In(14) vsandevicemonitord[2101901]: Device eui.3656323054a043630025384500000002 was already unmounted.
2024-08-22T22:08:18Z In(14) vsandevicemonitord[2101901]: Mounting succeeded on VSAN diskgroup with Cache tier : eui.01000000000000005cd2e4db0a545551.
2024-08-22T22:08:18Z In(14) vsandevicemonitord[2101901]: Repair successful for device 52623fac-4134-926c-ca47-d68e3a5a92d3
2024-05-13T06:54:55.474Z Er(163) vsanesxcmd[13546550]: [Originator@6876 sub=Libs] VsanUtil: Disk with vSAN uuid 529773e4-cf50-0b45-71b3-46501b8cea6f failed to appear in LSOM
2024-05-13T06:54:55Z In(14) vsandevicemonitord[2102553]: stderr Errors:
2024-05-13T06:54:55Z In(14)[+] vsandevicemonitord[2102553]: Unable to mount: Disk with vSAN uuid 529773e4-cf50-0b45-71b3-46501b8cea6f failed to appear in LSOM
2024-05-13T06:54:55Z In(14)[+] vsandevicemonitord[2102553]: , stdout from command vsan storage diskgroup mount -s eui.01000000000000005cd2e4bda85e5551.
2024-05-13T06:54:55Z In(14) vsandevicemonitord[2102553]: Mounting failed on VSAN device eui.01000000000000005cd2e4bda85e5551.
2024-05-13T06:54:55Z In(14) vsandevicemonitord[2102553]: Repair attempt 1 for device 524207bd-e1e9-2046-3969-2c5f8a32e0b6
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This is a known issue affects ONLY vSAN OSA 8.0 U2 and vSAN OSA 8.0 U2b under very specific conditions explained above.
VMware recommends applying the configuration changes suggested in the "Workaround" section to mitigate the risk of encountering this issue proactively on vSAN OSA 8.0 U2 / vSAN OSA 8.0 U2b releases.
It is high recommended to apply the below workaround and upgrade to vSphere 8.0 U3b which contains the fixes.
Workaround:
Apply the below advanced configuration on all hosts in the cluster and run auto-backup.sh:
esxcfg-advcfg -s 0 /LSOM/lsomPlogZeropV2;/sbin/auto-backup.sh