VMware Cloud Community
bvanarse
Contributor
Contributor

bootbank cannot be found at path /bootbank

Hi

In vCenter for one of the ESXi server I am getting  error as "bootbank cannot be found at path /bootbank"

Reboot is temporary solution for this.

Out of two devices there is none USB device at boot time

vmhba32 usb-storage link-n/a usb.vmhba32 () USB

And below is the error details :-

SCSI Level: 2 Is Pseudo: false Status: dead timeout

Is RDM Capable: false Is Removable: true

Can some one please suggest permanent solution if any.

Thanks &  Regards

27 Replies
darth_cisco
Enthusiast
Enthusiast

Yep im running into the exact same issue now. I was getting error 30 when trying to remediate hosts and taking a look at the esxupdate.log I can see stuff like "HostImage: INFO: Installer <class 'vmware.esximage.Installer.BootBankInstaller.BootBankInstaller'> was not initiated - reason: bootbank is invalid: /bootbank is not a directory!" so taking a look then at the vmkernel.log I saw a lot of " Bootbank cannot be found at path '/bootbank'" I am still messing around trying to see if I can clear this up somehow, or if there is a way to see what is causing it.

Hosts:

Apple MacPro 6,1 64GB

ESXi 6.5U1 Build 5969303

Reply
0 Kudos
darth_cisco
Enthusiast
Enthusiast

Running "vmkfstools -P /altbootbank" on a host that was failing to remediate and I get "Could not open /altbootbank Error: Unable to access device, please check your connection to the device." and all the ones that had no issues come up with:

vfat-0.04 (Raw Major Version: 0) file system spanning 1 partitions.

File system label (if any):

Mode: private

Capacity 261853184 (63929 file blocks * 4096), 107085824 (26144 blocks) avail, max supported file size 0

UUID: 60bb93e2-bae9cfea-08ce-a7ad0878d60f

Partitions spanned (on "disks"):

  t10.SanDisk00Ultra_Fit000000000000004C530001240407120381:5

Is Native Snapshot Capable: NO

Reply
0 Kudos
TEST1981
Contributor
Contributor

Got same issue - all redirects and folders on these bootbank werenot accesible.

So I was not able even to upgrade/install VM tools,which were stored there.

Resolution were only to make shortcut to another folder on datastore like workaround or reinstall hypervisor on new sd card

000.JPG

RainGigel
Contributor
Contributor

Hi Everyone,

I have the same issue, I'm using:

BladeSystem c7000

ProLiant BL460c Gen9

Firmware - 2.54 Jun 15 2017

Event details:

Issue detected on 10.10.57.3 in Chassis-1: Bootbank cannot be found at path '/bootbank'

(2018-02-21T09:02:16.646Z cpu55:7946611)

I didn't do anything yet, I check the Blade and everything seems to work fine.

How worried should I be?

Thanks.

Reply
0 Kudos
TEST1981
Contributor
Contributor

Can you check in sphere client if your SD card are live or dead ?

484.JPG

Reply
0 Kudos
GervandeKolk
Contributor
Contributor

Hello there,

We are getting the same error in a ESXI 6.5 environment.

Server is a HP DL380 Gen9 with a 32 Gb SD card HP brand.

pastedImage_1.png

pastedImage_0.png

This morning our VM Terminal server decides to reboot suddenly.

I am going to check the hardware through iLo.

Regards,

Ger

Reply
0 Kudos
rdugaue
Contributor
Contributor

It's been awhile since a post to this thread, but I can't find any further information. Has anyone found exactly what this error is about? I have several Dell R610s (Esxi 6.0 U2) and this just started on one dell about 3 months ago (Only reported ONCE) and then another reported last night.

Going into vSphere though shows the USB (8gb sandisks) as attached, while a previous post above showed it as "dead". So the drive is still attached. What further diags can I run to check this out. Is there an easy procedure to backup an existing config and restore it to an offline spare to have ready? Besides this error, there are no hardware problems reported in ilo or vsphere on any of my hosts.

Capture.PNG

Reply
0 Kudos
Misha1975
Contributor
Contributor

I've got the same issue on some Dell R630 servers, after updating them to esxi 6.5 build 10884925.

Opened a case with VMware support, they've suggested to disable the vmkusb driver described in VMware Knowledge Base​ but this didn't solve the problem.

Going to contact them again and will reply when having more answers.

Reply
0 Kudos