Welcome to Communities.
A few questions:
- Is this PSOD recursive? (e.g. it occurs every time you reboot the ESXi host)
- If yes, is the data in the remaining nodes in the cluster currently healthy?
- If no, is this a production cluster or a homelab?
Nawals, this PSOD may be occurring for a completely different reason than in the kb you mentioned, but in the same problem area (SSD log is damaged and failing to be read correctly).
It's very similar but it's not this point,but thanks your help.
1.The problem occurred while the host was running normally and I need to restart the host to get back to normal
2.The data in the remaining nodes in the cluster is currently healthy and Everything was healthy when I ran the Cluster vSAN Skyline Healty check.
3.It's a Production cluster but can remove the error host
"1.The problem occurred while the host was running normally and I need to restart the host to get back to normal"
I understand, but I was specifically asking if it is recursive e.g. occurring every time you reboot the host - if it is (and all data is healthy) then it should just be a case of rebooting the host and then during ESXi preboot press shift+o, disable the vSAN modules and remove the currently problematic Disk-Group, then reboot the host normally:
Another temporary alternative to removing the Disk-Group is to detach the Cache-tier SSD in question (either physically, via Controller/BIOS settings or from the vSphere UI storage devices page after temporarily disabling vSAN modules).
Not all data is healthy when the host is rebooted, the machine needs to be started in 60 minutes, or components will be resynchronized
Did you mean there is something wrong with my SSD cache disk?