• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 563
  • Last Modified:

can't launch VirtualCenter 2.0.2

Hello,
This my first ESX host installtion.  Everything went well as far as the normal operation of the host.  I was able to create a new VM and have full connectivity.  But, here's my issue ..

I was trying to update ESX 3.0.2 to update 1
 - I downloaded the update
 - used winSPC to transfer the .tar.gz file to one of my datastores (i have 2 SAS drives)
 - extracted the file using the tar xvzf switch, and cd'ed to the new directory
 - used the command esxupdate update, and got the this error

"INFO: No repository URL specified, going with file:/vmfs/volumes/47488d72-e1fee918-4dac-001731f8fd82/esx-upgrade-from-esx2-3.0.2-61618
INFO: Configuring...
ERROR: Invalid repository at file:/vmfs/volumes/47488d72-e1fee918-4dac-001731f8fd82/esx-upgrade-from-esx2-3.0.2-61618/: Cannot find descriptor.xml
INFO: Make sure you have file: or http: prepended to the URL."

I tried using a different datastore, but got the same error.  Any help would be greatly appreciated.

hardware config:
Dual Xeons 2.2 Ghz
8GB FB-Dimms from wintec
Asus board with SAS support
2x sas drives (2 different vmfs data stores)
 
0
bloodywicked
Asked:
bloodywicked
  • 4
  • 4
1 Solution
 
WeHeCommented:
did you use it like this:
esxupdate -r file:/pathtoupdate/61681 install
it looks like you did not give the correct repository path.
0
 
bloodywickedAuthor Commented:
i didn't.  In fact i didn't use any switches at all.  i only made sure that I'm in the correct directory as the update files and typed the command:

esxupdate update

that's it.  I'll try your suggestion, and let you know.

BTW, thanks for your respond... :)
0
 
bloodywickedAuthor Commented:
see that's what i though too.  Once i extract the update 1 file.  i should get a folder called "61681", but i don't.  instead i get a folder called "esx-upgrade-from-esx2-3.0.2-61618",

WeHe, i tried your way, but didn't work .. :(
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
WeHeCommented:
I checked it on my installation.
when i extract my update file esx-upgrade-from-esx3-3.0.2-61618.tar.gz it creates the directory 61618.
this dir contains the needed descriptor.xml file and a lot more.
0
 
bloodywickedAuthor Commented:
that's exactally how it is on our Production server ... i just don't understand Y it extracted it the way it did .. i even deleted the .tar file, redownloaded it , and extracted on a different datastore ,, same thing
0
 
WeHeCommented:
i would try to download this file again, maybe you took a wrong one?
and to correct the usage syntax:
i use the following script to update my esx servers:
-------------------------------------------------------------------------------------------
echo .
echo "Updating to ESX 3.0.2 Update 1, 1002424, 1002425, 1002429"
echo .
cd /root/ESXupdate
esxupdate -n -r file:///root/ESXupdate/61618 update
esxupdate -n -r file:///root/ESXupdate/ESX-1002429 update
esxupdate -n -r file:///root/ESXupdate/ESX-1002425 update
esxupdate -r file:///root/ESXupdate/ESX-1002424 update
-------------------------------------------------------------------------------------------
0
 
WeHeCommented:
btw, "esx-upgrade-from-esx2-3.0.2-61618"
are you shure about the name?
if the name is correct, this is for updating esx2 to esx 3.
0
 
bloodywickedAuthor Commented:
that was HUGE mistake on my end .. i downloaded the wrong file (TWICE).  sorry to bug u, and thanks for help .. I'll give up a 1000 points if i could.  :)
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now