ich habe das Problem, dass ich weder mit dem Host Update Utility noch manuell die Firmware eines Standalone ESXi 4U1 aktualisieren kann. Der Grund ist wohl folgender:
Code: Alles auswählen
Command: update
Args: ['update']
Options: {'nodeps': None, 'all': None, 'retry': 5, 'vibview': None, 'nocache': None, 'compliant': None, 'loglevel': 'DEBUG', 'cleancache': None, 'bundles': ['vmware-esx-firmware-4.0.0-1.10.219382.i386.vib'], 'nosigcheck': None, 'bundlezips': None, 'olderversion': None, 'proxyurl': None, 'meta': None, 'timeout': 30.0, 'cachesize': None, 'HA': None, 'maintenancemode': None}
[2010-03-06 12:28:49] DEBUG: cmdline: update/stage: bundlespec = ['vmware-esx-firmware-4.0.0-1.10.219382.i386.vib']
[2010-03-06 12:28:49] DEBUG: cmdline: Combined metadata: []
[2010-03-06 12:28:49] DEBUG: cmdline: Adding VIB at vmware-esx-firmware-4.0.0-1.10.219382.i386.vib...
[2010-03-06 12:28:49] DEBUG: vibcache: vib with remoteLocation=vmware-esx-firmware-4.0.0-1.10.219382.i386.vib maps to DB entry deb_vmware-esx-firmware_4.0.0-1.10.219382
[2010-03-06 12:28:49] DEBUG: vibcache: Applying state staged from the database for VIB ID deb_vmware-esx-firmware_4.0.0-1.10.219382
[2010-03-06 12:28:49] DEBUG: vibcache: Loading repomd/apt metadata...
[2010-03-06 12:28:49] INFO: vibcache: BIOS reports Vendor Intel , Model
[2010-03-06 12:28:49] DEBUG: vibcache: Computing rpm/dpkg dependencies...
[2010-03-06 12:28:49] DEBUG: _visor: Closing tag file /tmp/stage/firmware/usr/lib/ipkg/status
[2010-03-06 12:28:49] DEBUG: _visor: Closing tag file /tmp/stage/oemstage/usr/lib/ipkg/status
[2010-03-06 12:28:49] DEBUG: _visor: Closing tag file /tmp/stage/customstage/usr/lib/ipkg/status
[2010-03-06 12:28:49] DEBUG: _visor: Closing tag file /locker/packages/usr/lib/ipkg/status
[2010-03-06 12:28:49] DEBUG: _visor: Closing tag file /usr/lib/ipkg/status
[2010-03-06 12:28:49] DEBUG: cmdline: Initial selection: [deb_vmware-esx-firmware_4.0.0-1.10.219382:uninstalled, staged]
[2010-03-06 12:28:49] DEBUG: cmdline: Vibs from bulletins: set([])
[2010-03-06 12:28:49] DEBUG: vibcache: Applying state staged from the database for VIB ID deb_vmware-esx-firmware_4.0.0-1.10.219382
[2010-03-06 12:28:49] DEBUG: cmdline: Final selected set: [deb_vmware-esx-firmware_4.0.0-1.10.219382:uninstalled, staged]
[2010-03-06 12:28:49] INFO: _visor: Running [tar -czvf /bootbank/pkgdb.tmp -C /tmp/stage/firmware/usr/lib/ipkg . > /dev/null] to repack pkgdb.tgz
[2010-03-06 12:28:50] DEBUG: _visor: Total size of oem/mod VIBs is 0
[2010-03-06 12:28:50] INFO: _visor: The following packages are obsoleted by new version: set([('vmware-esx-firmware', '4.0.0-1.9.208167')])
They will be added to the remove list.
[2010-03-06 12:28:50] INFO: _visor: The following packages cannot be removed: vmware-esx-firmware. They will be pruned from the remove list.
[2010-03-06 12:28:50] DEBUG: _visor: removes=set([])
obsnames=set(['vmware-esx-firmware'])
pkgsToRemove=set([])
[2010-03-06 12:28:50] DEBUG: _visor: Number of oem/custom vibs: 0/0
[2010-03-06 12:28:50] INFO: _visor: Running [/sbin/bootbankstage-install.sh -v prep]...
[2010-03-06 12:28:51] INFO: _visor: cp: write error: No space left on device
[2010-03-06 12:28:51] INFO: _visor: cp: cannot close '/tmp/stage/firmware/bank/cim.vgz': No space left on device
[2010-03-06 12:28:52] INFO: _visor: Error: Copy of /bootbank/cim.vgz to /tmp/stage/firmware/bank/cim.vgz failed md5sum validation
[2010-03-06 12:28:52] DEBUG: _visor: Closing tag file /tmp/stage/firmware/usr/lib/ipkg/status
[2010-03-06 12:28:52] DEBUG: _visor: Closing tag file /tmp/stage/oemstage/usr/lib/ipkg/status
[2010-03-06 12:28:52] DEBUG: _visor: Closing tag file /tmp/stage/customstage/usr/lib/ipkg/status
[2010-03-06 12:28:52] DEBUG: _visor: Closing tag file /locker/packages/usr/lib/ipkg/status
[2010-03-06 12:28:52] DEBUG: _visor: Closing tag file /usr/lib/ipkg/status
[2010-03-06 12:28:52] ERROR: esxupdate: An esxupdate error exception was caught:
Traceback (most recent call last):
File "/sbin/esxupdate", line 242, in <module>
cmd.Run()
File "/lib/python25-visor.zip/pythonroot/vmware/esx4update/cmdline.py", line 382, in Run
installer.Install(self.iface)
File "/lib/python25-visor.zip/pythonroot/vmware/esx4update/VibCache.py", line 945, in Install
raise transactionerror
VisorSetupError: Bootbank preparation failed: /sbin/bootbankstage-install.sh -v prep returned (1)
[2010-03-06 12:28:52] INFO: _visor: Umounting /tmp/stage...
[2010-03-06 12:28:52] INFO: _visor: Umount done.Wie es aussieht ist die Root-Partition zu klein um den Käse zu entpacken:
Code: Alles auswählen
~ # df -h
Filesystem Size Used Available Use% Mounted on
visorfs 218.3M 182.6M 35.7M 84% /
vmfs3 1.8T 1.8T 61.2G 97% /vmfs/volumes/4b44bbe1-3b4f67b0-741c-000e0c3ce521
vmfs3 131.8G 76.6G 55.2G 58% /vmfs/volumes/4b44aefc-a76d5bc0-7717-000e0c3ce521
vfat 249.7M 4.0k 249.7M 0% /vmfs/volumes/ca684b7e-0602fbba-8b1e-677ecb132244
vfat 4.0G 121.8M 3.9G 3% /vmfs/volumes/4b44aef6-3299a3a0-6e60-000e0c3ce521
vfat 249.7M 60.3M 189.4M 24% /vmfs/volumes/c6b8777c-573b62dd-c185-86ee1aaa8b3e
vfat 285.9M 243.2M 42.7M 85% /vmfs/volumes/e00f98e1-2bcc0c91-e7a2-3487611c1557Jetzt ist die Frage, was kann ich einfach so löschen um wieder Platz zu bekommen? Ich hab schon gesucht, aber ich bin mir unsicher was ich löschen kann ohne mir die Maschine zu zerschießen.
Wäre echt super, wenn mir jemand sagen kann, was man in die Tonne hauen kann, damit das Update wieder durchläuft.
Vielen Dank schon mal im Voraus!
Grüße aus München
Arma