{"id":305,"date":"2019-02-04T22:25:31","date_gmt":"2019-02-04T14:25:31","guid":{"rendered":"https:\/\/kylemcdonald.com.au\/?p=305"},"modified":"2019-05-23T22:44:00","modified_gmt":"2019-05-23T14:44:00","slug":"fatal-error-33-inconsistent-data","status":"publish","type":"post","link":"https:\/\/kylemcdonald.com.au\/2019\/02\/04\/fatal-error-33-inconsistent-data\/","title":{"rendered":"Fatal error: 33 (Inconsistent data)"},"content":{"rendered":"
After a recent power outage that lasted longer than my UPS runtime, I found that one of my ESXi hosts wasn’t online.<\/p>\n
A quick look at the console screen showed that ESXi had attempted to boot and failed with Fatal error: 33 (Inconsistent data) when validating the file s.v00<\/p>\n
<\/a><\/p>\n I’ve had various boot media fail before, especially when using cheap USB sticks, but until now I hadn’t run into a file corruption issue.<\/p>\n As I was working remotely to the server I decided to just boot the latest ESXi install ISO I had available and select the “upgrade” process so that the host would retain its configuration.<\/p>\n This was actually a downgrade as the host was running 6.5 build 13004031 (Express Patch 13) but my install media was only 6.5 build 10719125 (Express Patch 11).<\/p>\n After the install had finished, I was able to boot the host successfully and then install the EP13 update to bring it back to the same build as the other hosts in the cluster.<\/p>\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" After a recent power outage that lasted longer than my UPS runtime, I found that one of my ESXi hosts wasn’t online. A quick look at the console screen showed that ESXi had attempted to boot and failed with Fatal Continue reading Fatal error: 33 (Inconsistent data)<\/span>