Esxi is installed on a 8GB USB stick, and when I try to upgrade it o 6.5 U1, the progress failed with some errors messages.
vmware -vl
VMware ESXi 6.5.0 build-5310538
VMware ESXi 6.5.0 GA
md5sum update-from-esxi6.5-6.5_update01.zip
12ffcaa19b62adf528471047c33748b5 update-from-esxi6.5-6.5_update01.zip
esxcli software vib update -d "/vmfs/volumes/5615fc0a-3d59bb11-05c2-001a64b2a728/update-from-esxi6.5-6.5_update01.zip"
[InstallationError]
Failed updating the bootloader: Execution of command /usr/lib/vmware/bootloader-installer/install-bootloader failed: non-zero code returned
return code: 1
output: ERROR: ld.so: object '/lib/libMallocArenaFix.so' from LD_PRELOAD cannot be preloaded: ignored.
Traceback (most recent call last):
File "/usr/lib/vmware/bootloader-installer/install-bootloader", line 238, in <module>
main()
File "/usr/lib/vmware/bootloader-installer/install-bootloader", line 223, in main
partType, diskGeom, parts = getDiskInfo(diskPath)
File "/usr/lib/vmware/bootloader-installer/install-bootloader", line 151, in getDiskInfo
rc, out, err = execCommand(command)
File "/usr/lib/vmware/bootloader-installer/install-bootloader", line 94, in execCommand
raise Exception("%s failed to execute: status(%d)" % (command, process.returncode))
Exception: /sbin/partedUtil getptbl /vmfs/devices/disks/naa.200049454505080f failed to execute: status(255)
vibs = VMware_bootbank_esx-base_6.5.0-1.26.5969303
Please refer to the log file for more details.
and there is a red line taking up in syslog:
2017-09-01T06:52:01.571Z cpu2:68085)ALERT: Failed to execute bootloader update script, bootloader might be out of date: /sbin/partedUtil getptbl /vmfs/devices/disks/naa.200049454505080f failed to execute: status(255)
when i execute /sbin/partedUtil getptbl /vmfs/devices/disks/naa.200049454505080f, i get this error:
Error: The device /dev/disks/naa.200049454505080f is so small that it cannot possibly store a file system or partition table. Perhaps you selected the wrong device?
Unable to get device /vmfs/devices/disks/naa.200049454505080f
it complains the size of my USB STICK is too small, but when I check the size from device list, it is another story.
naa.200049454505080f is the USB Stick.
esxcli storage core device list
......
naa.200049454505080f
Display Name: Local USB Direct-Access (naa.200049454505080f)
Has Settable Display Name: false
Size: 15393160691712
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/naa.200049454505080f
Vendor: Generic
Model: Mass Storage
Revision: 0102
SCSI Level: 2
Is Pseudo: false
Status: on
Is RDM Capable: false
Is Local: true
Is Removable: true
Is SSD: false
Is VVOL PE: false
Is Offline: false
Is Perennially Reserved: false
Queue Full Sample Size: 0
Queue Full Threshold: 0
Thin Provisioning Status: unknown
Attached Filters:
VAAI Status: unsupported
Other UIDs: vml.0200000000200049454505080f4d6173732053
Is Shared Clusterwide: false
Is Local SAS Device: false
Is SAS: false
Is USB: true
Is Boot USB Device: true
Is Boot Device: true
Device Max Queue Depth: 1
No of outstanding IOs with competing worlds: 32
Drive Type: unknown
RAID Level: unknown
Number of Physical Drives: unknown
Protection Enabled: false
PI Activated: false
PI Type: 0
PI Protection Mask: NO PROTECTION
Supported Guard Types: NO GUARD SUPPORT
DIX Enabled: false
DIX Guard Type: NO GUARD SUPPORT
Emulated DIX/DIF Enabled: false
the strange thing is the size, which is too big in my opinion.
ls -l /vmfs/devices/disks
total 33776997014859609
-rw------- 1 root root 16140898865472602624 Sep 1 07:00 naa.200049454505080f
-rw------- 1 root root 4161536 Sep 1 07:00 naa.200049454505080f:1
-rw------- 1 root root 262127616 Sep 1 07:00 naa.200049454505080f:5
-rw------- 1 root root 262127616 Sep 1 07:00 naa.200049454505080f:6
-rw------- 1 root root 115326976 Sep 1 07:00 naa.200049454505080f:7
-rw------- 1 root root 299876352 Sep 1 07:00 naa.200049454505080f:8
-rw------- 1 root root 2684354560 Sep 1 07:00 naa.200049454505080f:9
-rw------- 1 root root 1000204886016 Sep 1 07:00 naa.5000cca35dca27b4
-rw------- 1 root root 1000201224704 Sep 1 07:00 naa.5000cca35dca27b4:1
lrwxrwxrwx 1 root root 20 Sep 1 07:00 vml.01000000002020202020204a503239323148513052414a4a41486974616368 -> naa.5000cca35dca27b4
lrwxrwxrwx 1 root root 22 Sep 1 07:00 vml.01000000002020202020204a503239323148513052414a4a41486974616368:1 -> naa.5000cca35dca27b4:1
lrwxrwxrwx 1 root root 20 Sep 1 07:00 vml.0200000000200049454505080f4d6173732053 -> naa.200049454505080f
lrwxrwxrwx 1 root root 22 Sep 1 07:00 vml.0200000000200049454505080f4d6173732053:1 -> naa.200049454505080f:1
lrwxrwxrwx 1 root root 22 Sep 1 07:00 vml.0200000000200049454505080f4d6173732053:5 -> naa.200049454505080f:5
lrwxrwxrwx 1 root root 22 Sep 1 07:00 vml.0200000000200049454505080f4d6173732053:6 -> naa.200049454505080f:6
lrwxrwxrwx 1 root root 22 Sep 1 07:00 vml.0200000000200049454505080f4d6173732053:7 -> naa.200049454505080f:7
lrwxrwxrwx 1 root root 22 Sep 1 07:00 vml.0200000000200049454505080f4d6173732053:8 -> naa.200049454505080f:8
lrwxrwxrwx 1 root root 22 Sep 1 07:00 vml.0200000000200049454505080f4d6173732053:9 -> naa.200049454505080f:9
the size of the first line is too big.
is this the cause?