FATAL ERROR: 28 (CRC error) - ESXi Host not Booting

Products

• VMware vSphere ESXi

Issue/Introduction

ESXi Host comes up with Fatal Error: 28 (CRC error) when reboot is initiated 

Verified from Host DCUI from the below reference screenshot 

Error: 28 (CRC error) while loading module: /vmx.v00

Cause

The CRC error during decompression while booting VMware ESXi typically results from data corruption due to:

1. Bad bootable media (like a faulty USB stick or incorrectly burned DVD).
2. Network issues during the ISO download, leading to incomplete or corrupt files.

 

 

Resolution

Steps to Resolve Hardware-Related CRC Errors:

1. Diagnose the SD Card (or Storage Device) Health

Test the SD Card:

If you're using an SD card as the boot device for ESXi, it may have bad sectors or be nearing the end of its life. SD cards, especially those used in high-usage environments, can degrade over time and develop faulty blocks that cause data corruption. Use tools available with your Hardware Vendor to test the SD card for read/write errors and bad sectors.

If the tool reports issues, the SD card is likely faulty and should be replaced.

2. Replace the SD Card or USB Stick

If the diagnostic tests confirm that your SD card or USB stick has developed bad sectors or is corrupted, replacing the storage device is the best course of action.

Recommended Steps:

Use a high-quality SD card or USB drive designed for enterprise use if possible. For example, SLC (Single-Level Cell) flash memory cards are more reliable than standard consumer-grade SD cards, which typically use MLC (Multi-Level Cell) or TLC (Triple-Level Cell) memory, known to wear out faster.

Avoid reusing the faulty SD card, as even after formatting, it may still have bad sectors.

After replacing the Faulty SD card, Reinstall the ESXi host.