Hi.

I have 4 node ( ftt=1 ) cluster. After damage vsan doesn't rebuild object. I had one of object ABSENT. After delete inaccessible object I can't power on VM. There is problem with vmdk. How to recover it? On power there is file not found

/localhost/dc1/computers/cls01/resourcePool/vms> vsan.vm_object_info Vmxxxxx

2023-10-29 23:59:52 +0000: Fetching vSAN disk info from 192.168.2.152 (may take a moment) ...

2023-10-29 23:59:52 +0000: Fetching vSAN disk info from 192.168.2.153 (may take a moment) ...

2023-10-29 23:59:52 +0000: Fetching vSAN disk info from 192.168.2.151 (may take a moment) ...

2023-10-29 23:59:52 +0000: Fetching vSAN disk info from 192.168.2.176 (may take a moment) ...

2023-10-29 23:59:52 +0000: Fetching vSAN disk info from 192.168.2.160 (may take a moment) ...

2023-10-29 23:59:53 +0000: Done fetching vSAN disk infos

VM VMxxxx:

  VM has a non-vSAN datastore

  Disk backing:

    [cls01-vsan01] 23381365-0851-f719-0c77-e43d1a2ad266/VMxxxx-000001.vmdk

      [cls01-vsan01] 23381365-0851-f719-0c77-e43d1a2ad266/VMxxxx.vmdk

  [cls01-vsan01] 23381365-0851-f719-0c77-e43d1a2ad266/VMxxxx.vmx

    DOM Object: 23381365-0851-f719-0c77-e43d1a2ad266 (v11, owner: 192.168.2.160, proxy owner: None, policy: stripeWidth = 1, cacheReservation = 0, proportionalCapacity = [0, 100], hostFailuresToTolerate = 1, forceProvisioning = 0, spbmProfileId = aa6d5a82-1c88-45da-85d3-3d74b91a5bad, spbmProfileGenerationNumber = 0, CSN = 269, SCSN = 263, spbmProfileName = vSAN Default Storage Policy)

      RAID_1

        Component: c6673e65-9ab4-a26c-bc5f-b8ca3a694c4c (state: ACTIVE (5), host: 192.168.2.151, capacity: naa.5002538f41a5b9f5, cache: t10.NVMe____Samsung_SSD_980_1TB_____________________2446B111D5382500,

                                                         votes: 1, usage: 0.6 GB, proxy component: false)

        Component: a6793e65-7c2c-bca7-25aa-e43d1a2ad266 (state: ACTIVE (5), host: 192.168.2.153, capacity: naa.600508b1001cc6658131bdaa6b99e85f, cache: naa.600508b1001cb55d75f95b40596da2ec,

                                                         votes: 1, usage: 0.6 GB, proxy component: false)

      Witness: e7e03e65-c625-919d-ec18-e43d1a2ad266 (state: ACTIVE (5), host: 192.168.2.160, capacity: naa.6d4ae520a53f52002b76d7671f806885, cache: t10.NVMe____Samsung_SSD_960_EVO_250GB_______________C80EB38153382500,

                                                     votes: 1, usage: 0.0 GB, proxy component: false)

  [cls01-vsan01] 23381365-0851-f719-0c77-e43d1a2ad266/VMxxxx-000001.vmdk

    DOM Object: 2b321b65-f40d-0c96-5313-e43d1a2ad266 (v11, owner: 192.168.2.153, proxy owner: None, policy: stripeWidth = 1, cacheReservation = 0, proportionalCapacity = [0, 100], hostFailuresToTolerate = 1, forceProvisioning = 0, spbmProfileId = aa6d5a82-1c88-45da-85d3-3d74b91a5bad, spbmProfileGenerationNumber = 0, CSN = 243, SCSN = 232, spbmProfileName = vSAN Default Storage Policy)

      RAID_1

        Component: 7ded3d65-febc-1ad0-b794-b8ca3a694c4c (state: ACTIVE (5), host: 192.168.2.153, capacity: naa.5002538a06cf4d60, cache: naa.600508b1001cb55d75f95b40596da2ec,

                                                         votes: 1, usage: 64.8 GB, proxy component: false)

        Component: b8793e65-d23c-01bb-4b87-90e2ba16a33c (state: ACTIVE (5), host: 192.168.2.151, capacity: naa.5002538f3364b839, cache: naa.5002538f41a5ba07,

                                                         votes: 1, usage: 64.8 GB, proxy component: false)

      Witness: fc983d65-f7b6-82b2-41a6-b8ca3a694c4c (state: ACTIVE (5), host: 192.168.2.152, capacity: naa.5002538e90b64be7, cache: t10.NVMe____Corsair_MP400___________________________E61B20C04BA77964,

                                                     votes: 1, usage: 0.0 GB, proxy component: false)

  [cls01-vsan01] 23381365-0851-f719-0c77-e43d1a2ad266/VMxxxx.vmdk

    Couldn't find info about DOM object '24381365-729a-538f-f3cf-e43d1a2ad266'

--> this is doesn't exists:  '24381365-729a-538f-f3cf-e43d1a2ad266'

files in folder of vm:

-rw-------    1 root     root             0 Oct 29 03:18 .2b321b65-f40d-0c96-5313-e43d1a2ad266.lck

drwxr-xr-x    1 root     root           560 Oct 29 23:57 .dvsData

-r--------    1 root     root       1441792 Sep 26 19:59 .fbb.sf

-r--------    1 root     root     267026432 Sep 26 19:59 .fdc.sf

-rw-------    1 root     root             0 Oct  2 21:12 .old.2b321b65-f40d-0c96-5313-e43d1a2ad266.lck.old

-r--------    1 root     root       1179648 Sep 26 19:59 .pb2.sf

-r--------    1 root     root     268435456 Sep 26 19:59 .pbc.sf

-r--------    1 root     root     262733824 Sep 26 19:59 .sbc.sf

drwx------    1 root     root           280 Sep 26 19:59 .sdd.sf

-r--------    1 root     root       4194304 Sep 26 19:59 .vh.sf

-rw-------    1 root     root           325 Oct 20 11:58 VMxxxxx-000001.vmdk

-rw-r--r--    1 root     root          1625 Oct 29 23:23 VMxxxxx-062a49d7.hlog

-rw-------    1 root     root        295336 Oct  2 21:12 VMxxxxx-Snapshot1.vmsn

-rw-------    1 root     root        270840 Oct 23 08:05 VMxxxxx.nvram

-rw-------    1 root     root           555 Sep 26 20:21 VMxxxxx.vmdk

-rw-r--r--    1 root     root           485 Oct  2 21:12 VMxxxxx.vmsd

-rwxr-xr-x    1 root     root          3808 Oct 29 23:57 VMxxxxx.vmx

-rw-------    1 root     root          3932 Sep 27 21:27 VMxxxxx.vmxf

-rw-------    1 root     root           555 Oct 30 00:03 old.vmdk

-rw-r--r--    1 root     root         37261 Oct 19 08:11 vmware-58.log

-rw-r--r--    1 root     root         37262 Oct 19 08:14 vmware-59.log

-rw-r--r--    1 root     root         37262 Oct 19 08:17 vmware-60.log

-rw-r--r--    1 root     root         37349 Oct 19 08:20 vmware-61.log

-rw-r--r--    1 root     root         37262 Oct 19 08:23 vmware-62.log

-rw-r--r--    1 root     root        328691 Oct 20 11:58 vmware-63.log

-rw-r--r--    1 root     root        242190 Oct 23 08:05 vmware.log