Getting PSOD error while moving host online from MM (maintenance mode)

Products

• VMware vSAN

Issue/Introduction

After upgrading or patching a vSAN host when removing the host from maintenance mode it fails with a PSOD

PSOD will start with the following:

Failed at bora/modules/vmkernel/lsom/lsom_commit_flusher.c:2488 -- VMK_ASSERT(cfDisableAssert || LSNEntryLessThan(entry, cfParams _>gcpEntry))

Environment

vSAN (All) 

Cause

Review of vobd logs shows multiple messages for Components found with invalid metadata

2025-07-09T21:06:12.403Z: [vSANCorrelator] 1258767706us: [vob.vsan.lsom.foundInvalidMetadataComp] 133 Components found with invalid metadata on disk naa.################################ ########-####-####-####-############
2025-07-09T21:06:12.403Z: [vSANCorrelator] 1258777499us: [esx.audit.vob.vsan.lsom.foundInvalidMetadataComp] 133 Components found with invalid metadata on disk naa.################################ ########-####-####-####-############
2025-07-09T21:06:12.475Z: [vSANCorrelator] 1258840123us: [vob.vsan.lsom.foundInvalidMetadataComp] 144 Components found with invalid metadata on disk naa.################################ ########-####-####-####-############
2025-07-09T21:06:12.475Z: [vSANCorrelator] 1258849250us: [esx.audit.vob.vsan.lsom.foundInvalidMetadataComp] 144 Components found with invalid metadata on naa.################################ ########-####-####-####-############
2025-07-09T21:06:12.618Z: [vSANCorrelator] 1258983503us: [vob.vsan.lsom.foundInvalidMetadataComp] 127 Components found with invalid metadata on disk naa.################################ ########-####-####-####-############
2025-07-09T21:06:12.619Z: [vSANCorrelator] 1258992672us: [esx.audit.vob.vsan.lsom.foundInvalidMetadataComp] 127 Components found with invalid metadata on disk naa.################################ ########-####-####-####-############

Resolution

Confirm there are known good backups of all data
Reboot the host that is having PSODs and leave in maintenance mode
Check vSAN Object Health and confirm there are no inaccessible objects 
 

• Navigate to Monitor > vSAN > Skyline Health > vSAN object health 
• Reduced available objects are expected
  
  
• If there are inaccessible objects open a case with Broadcom support 

Once confirmed no objects are inaccessible,  re-create the disk groups on the host that is having a PSOD

1. Navigate to the vSAN cluster in the vSphere Client.
2. Click the Configure tab.
3. Under vSAN, click Disk Management.
4. Under Disk Groups, select the disk group to recreate.
5. Click …, then click the Recreate.
   The Recreate Disk Group dialog box appears.
6. Select no data migration mode, and click Recreate.
   
   
   

This will remove all data from the disk group and clear the metadate issue, The host can now be removed from maintenance mode and data rebuild

Additional Information

Recreate a Disk Group
Creating and managing Broadcom support cases