godaba
Contributor
Contributor

error codes 30

have been expressing an error, while patching hosts an specific cluster "The host returns esxupdate error codes:30. Check the update Manager log files and esxupdate log files for more details". checked for all possibilities from the web but no luck. Please refer some stuff in fixing this.

0 Kudos
17 Replies
RajeevVCP4
Expert
Expert

reboot host then patch

Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
godaba
Contributor
Contributor

Hi Rajeev,

did the same thing still not working, disconnected and connected the host also not use.

0 Kudos
msripada
Virtuoso
Virtuoso

Update error 30 is related to bootbank not found

If you can go to vmkernel.log and check for bootbank keywords, it might help if you encounter same issue. You can also check if the bootbank is accessible by cd /bootbank

I have seen this with SD cards losing connectivity

If you are using local harddrive, try to update the BIOS/driver/firmware for your localdrive

thanks,

MS

0 Kudos
msripada
Virtuoso
Virtuoso

The host returns esxupdate error codes: 30  Similar issue reported here as well

0 Kudos
admin
Immortal
Immortal

you can also check below KB - VMware Knowledge Base

if problem will not resolve than share the log file for further investigation.

godaba
Contributor
Contributor

yes able to browse cd /bootbank its pointing to /tmp. seems USB drive is missing here.

0 Kudos
msripada
Virtuoso
Virtuoso

Yes, that is causing the issue... That explains

0 Kudos
godaba
Contributor
Contributor

will this article help me in fixing this

VMware Knowledge Base

other hosts fine in the vcenter only few from a cluster having this.

0 Kudos
msripada
Virtuoso
Virtuoso

That is only for boot from SAN and if you are using the USB, I am unsure if that takes effect but can try that.

Thanks,

MS

0 Kudos
godaba
Contributor
Contributor

we suspected the MTU values in the UCS (its set to 9000) others are 1500 (working hosts). after reset the value from 9000 to 1500 there no use. Also by changing the boot value also seems will not fix the issues.

Yes we are in boot from SAN., please provide suggestions for fix this issues.

0 Kudos
msripada
Virtuoso
Virtuoso

Can you try the first step in this KB and check if bootbank is pointing to the correct lun instead of temp

VMware Knowledge Base

Thanks,

MS

0 Kudos
godaba
Contributor
Contributor

for our reference.

0 Kudos
godaba
Contributor
Contributor

pastedImage_0.png

0 Kudos
godaba
Contributor
Contributor

pastedImage_0.png

0 Kudos
msripada
Virtuoso
Virtuoso

Can you check if the datastore is listed in /vmfs/volumes or can you verify if they have the mapping correctly..

Thanks,

MS

0 Kudos
godaba
Contributor
Contributor

Hi Sri,

with the first step in the kb the issue was partially resolved, we are observing state as the boot bank backups every hour, where the command flush the boot bank to correct LUN.

0 Kudos
msripada
Virtuoso
Virtuoso

Possbility of the storage latency or the pathing issues to the LUN leading to the missing bootbank. Can you check the pathing of the Lun from the esxi host?

Thanks,

MS

0 Kudos