1 Reply Latest reply on Jul 7, 2019 11:14 AM by vmsysadmin201110141

    ESXi 6.7 PSOD in VSAN module - invalid cache data?

    vmsysadmin201110141 Novice

      Hi all,

       

      having a problem with a single node VSAN host (homelab setup). The host had a power outage and now boots all the way up until it PSODs at the very end of the boot process with:

       

      Failed at bora/modules/vmkernel/virsto/map/vs_map_cache.c:324 -- VMK_ASSERT(((mbh->state == MB_INVALID_DATA

       

      Is it possible to recover the data on VSAN partition or all data is lost? Thanks in advance!

       

      PSOD right after the Log Recovery...

        • 1. Re: ESXi 6.7 PSOD in VSAN module - invalid cache data?
          vmsysadmin201110141 Novice

          Some additional info: I was able to boot the host with VSAN disabled by adding to the boot parameters "jumpstart.disable=vsan,lsom,plog,virsto,cmmds".

           

          The disks and the vsan cluster appear to be intact.

           

          Would it help to delete the partitions on the NVME cache disk and re-add it to the VSAN cluster? Or there might be some other things to try before attempting to delete the cache partition?

           

          [root@esx03:~] esxcli vsan cluster get

          Cluster Information

             Enabled: true

             Current Local Time: 2019-07-07T17:59:14Z

             Local Node UUID:

             Local Node Type: NORMAL

             Local Node State: DISCOVERY

             Local Node Health State: HEALTHY

             Sub-Cluster Master UUID:

             Sub-Cluster Backup UUID:

             Sub-Cluster UUID: 52949dd0-8cb7-f3c4-3f5d-54461b2d65d3

             Sub-Cluster Membership Entry Revision: 0

             Sub-Cluster Member Count: 0

             Sub-Cluster Member UUIDs:

             Sub-Cluster Member HostNames:

             Sub-Cluster Membership UUID:

             Unicast Mode Enabled: false

             Maintenance Mode State: OFF

             Config Generation: 7d82f990-57d8-4bf6-965e-1df18c8d1ac5 12 2019-07-06T03:47:14.88

           

          [root@esx03:~] esxcli vsan storage list

          naa.6b8ca3a0ed773d0023abd26814ad2eeb

             Device: naa.6b8ca3a0ed773d0023abd26814ad2eeb

             Display Name: naa.6b8ca3a0ed773d0023abd26814ad2eeb

             Is SSD: true

             VSAN UUID: 5268e51a-a5ba-2a6c-5887-952e845fc964

             VSAN Disk Group UUID: 52b36e14-771e-6711-c074-88ab86b3ac9a

             VSAN Disk Group Name: t10.NVMe____Samsung_SSD_970_PRO_512GB_______________2E37B28159382500

             Used by this host: false

             In CMMDS: false

             On-disk format version: 7

             Deduplication: true

             Compression: true

             Checksum: 16614367127871676916

             Checksum OK: true

             Is Capacity Tier: true

             Encryption Metadata Checksum OK: true

             Encryption: false

             DiskKeyLoaded: false

             Is Mounted: true

             Creation Time: Fri Dec 21 17:22:58 2018

           

          naa.6b8ca3a0ed773d0023abd278159d8547

             Device: naa.6b8ca3a0ed773d0023abd278159d8547

             Display Name: naa.6b8ca3a0ed773d0023abd278159d8547

             Is SSD: true

             VSAN UUID: 5271c531-3fe7-dca2-097e-9cb6abb82cd3

             VSAN Disk Group UUID: 52b36e14-771e-6711-c074-88ab86b3ac9a

             VSAN Disk Group Name: t10.NVMe____Samsung_SSD_970_PRO_512GB_______________2E37B28159382500

             Used by this host: false

             In CMMDS: false

             On-disk format version: 7

             Deduplication: true

             Compression: true

             Checksum: 3856994230136079572

             Checksum OK: true

             Is Capacity Tier: true

             Encryption Metadata Checksum OK: true

             Encryption: false

             DiskKeyLoaded: false

             Is Mounted: true

             Creation Time: Fri Dec 21 17:22:58 2018

           

          t10.NVMe____Samsung_SSD_970_PRO_512GB_______________2E37B28159382500

             Device: t10.NVMe____Samsung_SSD_970_PRO_512GB_______________2E37B28159382500

             Display Name: t10.NVMe____Samsung_SSD_970_PRO_512GB_______________2E37B28159382500

             Is SSD: true

             VSAN UUID: 52b36e14-771e-6711-c074-88ab86b3ac9a

             VSAN Disk Group UUID: 52b36e14-771e-6711-c074-88ab86b3ac9a

             VSAN Disk Group Name: t10.NVMe____Samsung_SSD_970_PRO_512GB_______________2E37B28159382500

             Used by this host: false

             In CMMDS: false

             On-disk format version: 7

             Deduplication: true

             Compression: true

             Checksum: 12214449757955944003

             Checksum OK: true

             Is Capacity Tier: false

             Encryption Metadata Checksum OK: true

             Encryption: false

             DiskKeyLoaded: false

             Is Mounted: true

             Creation Time: Fri Dec 21 17:22:58 2018

           

           

          [root@esx03:~] partedUtil getptbl /dev/disks/t10.NVMe____Samsung_SSD_970_PRO_512GB_______________2E37B28159382500

          gpt

          62260 255 63 1000215216

          1 2048 6143 381CFCCC728811E092EE000C2911D0B2 vsan 0

          2 6144 1000215182 77719A0CA4A011E3A47E000C29745A24 virsto 0

           

          [root@esx03:~] partedUtil getptbl /dev/disks/naa.6b8ca3a0ed773d0023abd278159d8547

          gpt

          121534 255 63 1952448512

          1 2048 6143 381CFCCC728811E092EE000C2911D0B2 vsan 0

          2 6144 1952448478 77719A0CA4A011E3A47E000C29745A24 virsto 0

           

          [root@esx03:~] partedUtil getptbl /dev/disks/naa.6b8ca3a0ed773d0023abd26814ad2eeb

          gpt

          121534 255 63 1952448512

          1 2048 6143 381CFCCC728811E092EE000C2911D0B2 vsan 0

          2 6144 1952448478 77719A0CA4A011E3A47E000C29745A24 virsto 0