Bootbank cannot be found at path '/bootbank'" on ESXi, with inaccessible local datastore

Products

• VMware vSphere ESXi
• VMware vSphere ESX 8.x

Issue/Introduction

• The ESXi host reports the following alert in the vSphere Client:
  Issue detected on [HOSTNAME] in [CLUSTER]: Bootbank cannot be found at path '/bootbank'


• If the local boot device has a local VMFS partition the local datastore may also be seen as inaccessible in the vSphere client.
  
  
• The ESXi host may enter a Not Responding state in vCenter Server.

 

 

 

Environment

VMware vSphere ESXi 8.x

Cause

ESXi: /var/log/vmkernel.log:

• Shows SCSI sense data (H:0x0 D:0x2 P:0x0 Valid sense data: 0x4 0x44 0x0)
  
  
• This sense code is reported by the storage device indicating [0x4] HARDWARE ERROR with an additional sense code of 44/00 INTERNAL TARGET FAILURE. 
  
  
• The issue occurs due to a connectivity issues to the local device as a result of a hardware failure between the ESXi and the local boot device.

 

Resolution

To restore host functionality and address the underlying storage failure, the following actions are necessary:

1. Restore Management Access
   The host may require a cold boot (complete power cycle) via the hardware management console (e.g., iDRAC, ILO, or XClarity). Note: If a hardware issue is seen and the server is rebooted you may also loose complete access to the boot device.
   However, this action can also allow the hardware to reinitialise and it may come back to a connected state. 

2. Hardware Investigation 
   The system administrator must contact the hardware vendor to investigate the reported write failures and internal target errors. Detailed offline hardware diagnostics must be performed to verify the health of the boot device, the backplane, and the storage controller.

3. Remediation
   Faulty hardware components, such as the boot medium or Host Bus Adapter (HBA), may be replaced based on the findings from the hardware vendor's investigation.