While running through a large vSAN cluster upgrade project recently i ran into the occasional issue where hosts would fail to exit maintenance mode following an upgrade from ESXi 6.7U3 to 7.0. The error seen was “A general system error occurred: end of header not found” This is caused by unused entries in the hostd
Occasionally you can run into the situation where you need to leave a host down for an extended period of time and the business is happy to sign off on a loss of storage redundancy while any work is completed. In a vSAN environment without further action this could lead to a significant number of
Useful commands you can run to gather vSAN & Storage related information for troubleshooting uptime vmware -vl esxcli vsan cluster get esxcli vsan health cluster list esxcli vsan health cluster get -t=”Overall disks health” esxcli vsan storage list esxcli storage core device list esxcli storage core device stats get Much of this is useful to
