vSAN Component Metadata Invalid state

I had to resolve issue where vSAN after crash was complaining that few of disks were indicating Component metadata Invalid state

From vcenter rvc console vsan.health.health_summary was showing following errors

Physical disk - Component metadata health: red
  +--------------+--------------------------------------+--------+---------------+
  | Host         | Component                            | Health | Notes         |
  +--------------+--------------------------------------+--------+---------------+
  | 172.30.91.22 | 77d46e60-7941-acf3-1e3b-48df37176888 | Error  | Invalid state |
  | 172.30.91.22 | 90969b5f-3a4f-10f4-4b17-48df37176ad4 | Error  | Invalid state |
  | 172.30.91.22 | 824b7262-01dd-9b27-844d-48df37176888 | Error  | Invalid state |
  | 172.30.91.22 | 824b7262-2449-9d27-b928-48df37176888 | Error  | Invalid state |
  +--------------+--------------------------------------+--------+---------------+

using vsan.cmmds_find, search on the component UUID as reported in the health check (components with errors) to get the disk UUID. In my case nothing was found

/127.0.0.1/Datacenter1/computers> vsan.cmmds_find 0 -u 77d46e60-7941-acf3-1e3b-48df37176888
+---+------+------+-------+--------+---------+
| # | Type | UUID | Owner | Health | Content |
+---+------+------+-------+--------+---------+
+---+------+------+-------+--------+---------+

/127.0.0.1/Datacenter1/computers>  vsan.cmmds_find 0 -u 90969b5f-3a4f-10f4-4b17-48df37176ad4
+---+------+------+-------+--------+---------+
| # | Type | UUID | Owner | Health | Content |
+---+------+------+-------+--------+---------+
+---+------+------+-------+--------+---------+

/127.0.0.1/Datacenter1/computers>  vsan.cmmds_find 0 -u 824b7262-01dd-9b27-844d-48df37176888
+---+------+------+-------+--------+---------+
| # | Type | UUID | Owner | Health | Content |
+---+------+------+-------+--------+---------+
+---+------+------+-------+--------+---------+

/127.0.0.1/Datacenter1/computers> vsan.cmmds_find 0 -u 824b7262-2449-9d27-b928-48df37176888
+---+------+------+-------+--------+---------+
| # | Type | UUID | Owner | Health | Content |
+---+------+------+-------+--------+---------+
+---+------+------+-------+--------+---------+

In case you have the diskUuid, you can use that in the next command to find disk device name

vsan.cmmds_find 0 -t DISK -u xxx

In my case, I had to use esxcli vsan debug disk list to determine disk with Metadata Health in Invalid status .
Once you determine disk we need to Evacuate data , remove and readd disk to disk group.

Process for removing a disk:
Cluster > Configure > vSAN > Disk Management > Select the Disk-Group > Select the disk in the lower-pane > Click ‘Remove’ button > Select Full data migration option > OK
Once this task has been completed the disk should be available for adding back to the Disk-Group:
Cluster > Configure > vSAN > Disk Management > Select the Disk-Group > Click ‘Add disk’ button and select the correct disk