Greetings friends, making several upgrades the other day I found the next error that breaks you in the morning if you are in a hurry and you are performing upgrades of ESXi, the error in question happened to me when I tried to update using an ESXi bundle:
[InstallationError]
There was an error checking file system on altbootbank, please see log for detail.
Please refer to the log file for more details.
Steps to troubleshoot the error easily
Fortunately the problem is solved in just a few seconds, the first thing we will have to do is check that the partition is OK and see the information of it:
vmkfstools -P /altbootbank/
This will return something similar to the following, be very attentive to the Partitions spanned part, as we will use this information later:
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), 87220224 (21294 blocks) avail, max supported file size 0
UUID: 2afcf7ef-53839aff-43f1-432714380654
Partitions spanned (on "disks"):
naa.200049454505080f:5
Is Native Snapshot Capable: NO
The next command will be launched against the partition that has shown us the vmkfstools command:
dosfsck -a -w /dev/disks/naa.200049454505080f:5
Which will show us something like the next:
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/disks/naa.200049454505080f:5: 212 files, 42635/63929 clusters
If we try to launch the ESXi update command again using the bundle, we won't have any more problems. I hope it serves you well.
Greetings friends, if we remember the introduction to this series on how to create a Disaster Recovery plan with Veeam in Microsoft Azure, we had the following diagram:
In the diagram we can see how between the two locations we are using Veeam PN for connectivity, in this article today we will see the step-by-step steps to deploy and configure VeeamPN in both locations.
