I am currenty running on ESX 3.0.1 and wolud like to upgrade to v3.5.
when i run esxupdate update i get the below error message, what could be cause of the error and how can i sort it out?
root@server 3.5.0-64607# esxupdate update
INFO: No repository URL specified, going with file:/vmfs/volumes/209ea7c3-da11a473-d483-ede1f266fe2a/ESX-UPDATE/3.5.0-64607
INFO: Configuring...
INFO: Preparing to install VMware ESX Server 3.5.0-64607...
ERROR: Test RPM transaction failed: installing package kernel-source-2.4.21-47.0.1.EL.64607 needs 107MB on the / filesystem, installing package VMware-esx-drivers-scsi-mptscsi_2xx-2.6.48.11vmw-64607 needs 104MB on the / filesystem, installing package openssh-clients-3.6.1p2-33.30.14vmw needs 104MB on the / filesystem, installing package VMware-webCenter-esx-2.5.0-64191 needs 225MB on the / filesystem, installing package VMware-esx-drivers-scsi-ahci-1.2-64607 needs 225MB on the / filesystem, installing package kbd-1.08-10.6vmw needs 226MB on the / filesystem, installing package VMware-esx-drivers-scsi-vmkiscsi-3.6.3-64607 needs 222MB on the / filesystem, installing package VMware-esx-drivers-net-igb-1.0.0-64607 needs 223MB on the / filesystem, installing package glibc-devel-2.3.2-95.50 needs 223MB on the / filesystem, installing package cim-smwg-1.0-557926 needs 229MB on the / filesystem, installing package VMware-esx-drivers-net-bnx2-1.5.10b.1vmw-64607 needs 228MB on the / filesystem, installing package VMware-esx-drivers-scsi-ips-7.10.17.1vmw-64607 needs 227MB on the / filesystem, installing package VMware-esx-drivers-scsi-megaraid2-2.10.7.vm1-64607 needs 226MB on the / filesystem, installing package bind-utils-9.2.4-21.el3 needs 226MB on the / filesystem, installing package ypbind-1.12-5.21.10 needs 226MB on the / filesystem, installing package VMware-esx-drivers-net-forcedeth-1.25-64607 needs 226MB on the / filesystem, installing package VMware-esx-drivers-scsi-adp94xx-0.0.6-64607 needs 222MB on the / filesystem, installing package nfs-utils-1.0.6-45EL needs 222MB on the / filesystem, installing package VMware-esx-drivers-scsi-lpfc_elx_v740-7.4.0.13-64607 needs 223MB on the / filesystem, installing package man-pages-1.60-7.rhel3 needs 223MB on the / filesystem, installing package logrotate-3.6.9-2.RHEL3 needs 223MB on the / filesystem, installing package VMware-esx-backuptools-3.5.0-64607 needs 224MB on the / filesystem, installing package VMware-esx-drivers-scsi-sata_promise-1.03-64607 needs 225MB on the / filesystem, installing package VMware-esx-drivers-scsi-qla2300-v707_vmw-7.8.32-64607 needs 227MB on the / filesystem, installing package VMware-esx-drivers-scsi-qla4010-3.30-64607 needs 226MB on the / filesystem, installing package VMware-esx-drivers-scsi-aic7xxx-6.3.9-64607 needs 221MB on the / filesystem, installing package VMware-esx-drivers-ioat-7.0.33-64607 needs 221MB on the / filesystem, installing package VMware-esx-drivers-block-cciss-2.4.66.1vmw-64607 needs 220MB on the / filesystem, installing package VMware-cim-esx-3.5.0-64607 needs 221MB on the / filesystem, installing package VMware-esx-drivers-scsi-sata_svw-1.07-64607 needs 222MB on the / filesystem, installing package VMware-esx-drivers-scsi-sata_sil-0.9-64607 needs 222MB on the / filesystem, installing package VMware-esx-drivers-scsi-sata_nv-0.8-64607 needs 222MB on the / filesystem, installing package openssh-server-3.6.1p2-33.30.14vmw needs 222MB on the / filesystem, installing package VMware-esx-drivers-scsi-megaraid_sas-3.0.9-64607 needs 221MB on the / filesystem, installing package VMware-esx-drivers-net-3c90x-1.0.2-64607 needs 220MB on the / filesystem, installing package VMware-esx-drivers-scsi-aacraid_esx30-1.1.5.2vmw-64607 needs 214MB on the / filesystem, installing package ftp-0.17-17.2 needs 214MB on the / filesystem, installing package VMware-esx-drivers-scsi-ata_piix-1.05-64607 needs 214MB on the / filesystem, installing package VMware-esx-perftools-3.5.0-64607 needs 214MB on the / filesystem, installing package file-3.39-9.EL3.4 needs 214MB on the / filesystem, installing package ntp-4.1.2-5.el3 needs 216MB on the / filesystem, installing package VMware-esx-drivers-net-s2io-2.1.0.10458-64607 needs 215MB on the / filesystem, installing package kernel-utils-2.4-8.37.15 needs 215MB on the / filesystem, installing package man-1.5k-13.rhel3vmw needs 215MB on the / filesystem, installing package hotplug-2002_04_01-20.6 needs 215MB on the / filesystem
root@server 3.5.0-64607#
many thanks
alain
vdf -h (to show how much space you have left on the partitions)
what size is required to upgrade to 3.5 ??
-
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 2.4G 2.0G 298M 88% /
/dev/sda1 46M 17M 27M 38% /boot
none 391M 0 391M 0% /dev/shm
/vmfs/devices 1.3T 0 1.3T 0% /vmfs/devices
/vmfs/volumes/209ea7c3-da11a473-d483-ede1f266fe2a
268G 203G 65G 75% /vmfs/volumes/209ea7c3-da11a473-d483-ede1f266fe2a
/vmfs/volumes/45892882-c1d9ae6b-917c-00093d006f4d
817G 740G 76G 90% /vmfs/volumes/ds4700
dont know by heart. but your / partition is pretty packed with 300MB left ... free up until you have 1G or so free and give it another try.
By the way: if you have the option, do a vanilla installation and go to 3.5 Update 1 directly.
there is nothing extra or on the / partiton... or does ESX hase some larger files i can sefely remove to free up 700MB ?
3.5 Update 1 was my firts try and the problem was the same.
Just had a look add some vanilla 3.5 Update 1 ... / partition has 1.4G on it already ... so your 2.4G partition is a bit small I would say. Give it a reinstall and follow this best practices here http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/
reinstall is exactly why i tried not to do. But in the case i really want to do that what will happen with my current vm's on the disks??
/vmfs/volumes/ds4700 is FC attached and should be fine but i feat that the other one will be erased during the setup....
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 2.4G 2.0G 300M 88% /
/dev/sda1 46M 17M 27M 38% /boot
none 391M 0 391M 0% /dev/shm
/vmfs/devices 1.3T 0 1.3T 0% /vmfs/devices
/vmfs/volumes/209ea7c3-da11a473-d483-ede1f266fe2a
268G 203G 65G 75% /vmfs/volumes/209ea7c3-da11a473-d483-ede1f266fe2a
/vmfs/volumes/45892882-c1d9ae6b-917c-00093d006f4d
817G 740G 76G 90% /vmfs/volumes/ds4700
You have the option during setup to leave existing VMFS partions untouched or shift the VMs out to the SAN. Unplug the SAN links and make sure you have a proper backup in place before you start.
Try also when you boot from ISO/CD, to try the update option, and see if that works better for you.
-KjB