Hello,
i tried to upgrade my vcenter appliance server from 5.0 to 5.5
during the upgrade process, i met an error due to the lack of room on the source appliance server (5.0) for migrating the embedded DB2 database
as askes by vmware, i applied KB 2018760 and started the process again
all is fine until pre-check which is OK but after it fails
in the target appliance server (5.5) the logfile says :
localhost:/var/log/vmware/vami # more upgrade.log
2014-07-14 14:35:56+00:00 *** Starting upgrade process ***
2014-07-14 14:35:56+00:00 Executing pre-upgrade hooks...
2014-07-14 14:35:56+00:00 Executing '/etc/va/upgrade/pre-scripts/00_collect_configuration.sh'...
VMware vCenter Server Appliance 5.0.0.3324 Build 472350
VMware vCenter Server Appliance 5.0.0.3324 Build 472350
Key not found: /config/vpxd/extensionsPath
2014-07-14 14:35:59+00:00 Executing '/etc/va/upgrade/pre-scripts/01_collect_ad.sh'...
VMware vCenter Server Appliance 5.0.0.3324 Build 472350
VMware vCenter Server Appliance 5.0.0.3324 Build 472350
2014-07-14 14:36:00+00:00 Executing '/etc/va/upgrade/pre-scripts/02_embedded_db.sh'...
VMware vCenter Server Appliance 5.0.0.3324 Build 472350
VMware vCenter Server Appliance 5.0.0.3324 Build 472350
rm: cannot remove directory `/storage/db/export': Device or resource busy
2014-07-14 14:36:02+00:00 *** ERROR: Failed to execute command '/etc/va/upgrade/pre-scripts/02_embedd
ed_db.sh' 1 ***
any idea ?
thanks a lot
Claude
sounds like the DB2 database can't be unmounted
i assume you already restarted your vcenter appliance?
is it possible to just deploy new vcenter appliance 5.5 and reconnect your esx hosts? or is your environment to complex?
did you look at this post?
Hi Vervoort,
thanks for your answer
i followed KB2058441. According to this post, i encountered ERROR 500 at step 6.g
then i applied KB2018760 at the source appliance (e.g v5.0) and started the process again
it worked fine until step 11 (according to KB2058441) and then failed with error
rm: cannot remove directory `/storage/db/export': Device or resource busy
Anyway, in your answer you talk about a fresh install of VCSA 5.5. What happens if i choose a deployement from scratch without upgrading the DB2 database ?
Can i reconnect my hosts (2 ESXi v5.0), SAN storage, VDS, etc. at no risk ?
Thanks again
Claude
you can reconnect your esx host and storage but the config of your VDS etc... will be need to be configured again and risking you lose network connectivity etc...
i would recommend the upgrade ofcourse but maybe better to do an upgrade to VCSA 5.1 first then upgrade to 5.5?
the procedure looks te same but maybe this one will work
also make sure you did kb2018760 correctly. maybe the old VCSA cant shut down cause of the new disk being busy.