Installation of ESX 3.0.2 via USB fails

[Unix-Sysadmin]

Hi, we usually install our ESX-Servers (3.0.1) via USB.

On the Stick is an ISO-Image, the Patches, etc.

We´ve copied the new image on it and also changed our bootfiles. The entire installation should be "3.0.2 ready" now.

But the installation fails with the follwing message:

"Error -- The VMware ESX Server 3 installation tree in that directory does not seem to match your boot media."

Did anyone else have this problem and / or solution?

[virtech]

You said you updated your bootfiles, do you mean the boot.iso located in esx-3.0.2-52542\images ?

I had the same error as I forgot to update them! I use a custom CD to boot my servers.

I'm guessing thats ur issue as well, you need to use the boot.iso located in esx-3.0.2-52542\images with the new 3.0.2 installation media.

Message was edited by:

Mooihoek

[Unix-Sysadmin]

Well we use the boot.iso located in esx-3.0.2-52542\images with the new 3.0.2 installation media.

Any other suggestions?

[virtech]

I have just tested it and it works for me, perhaps go back through the same process and make sure you are only using files from the new boot.iso

Sounds like you are still using an old vmlinz, isolinux.bin, initrid.img etc

Message was edited by:

Mooihoek

[Unix-Sysadmin]

Hi,

thanks for your answer. But we still cant get it working.

For the installation of 3.0.1 we prepared the stick as described in the thread below including changing the file (hdstg2.img by Paul Lalonde):

http://www.vmware.com/community/thread.jspa?threadID=75792&start=0&tstart=0

For 3.0.2 we followd the same instructions with files only from the 3.0.2 image, including the changed hdstg2.img. Same errors.

First one: "The VMware ESX Server 3 installation does not seem to match your boot media".

Second: "An error occured reading the install from the ISO image. Please check your media and try again".

Third: "Device /dev/sdd1 does not appear to contain Red Hat CDROM images."

But the strange thing is that our iso passes the media test and the installation via Remote Management Card works perfectly.

System is a DELL 2950 as described in the HCL.

Could you please describe the way you got it working?

[Unix-Sysadmin]

push ...

Did anyone else have this problem and / or solution?

If not ... Could you please describe the way you got it working?

[virtech]

Hi I dont use the USB specifically, did you confirm that you are using the boot files from the new boot.iso ?

[Aughtly]

The "[b]...installation tree in that directory does not seem to match your boot media.[/b]" is actually an anaconda message that is occuring because the .buildstamp[/b] in the[b] initrd.img[/b] and .buildstamp[/b] in the hdstg2.img[/b] do not match.

The patched hdstg2.img from Paul Lalonde is actually made for the 3.0.1 image and you will need to modify the hdstg2.img that came with the new 3.0.2 to get the USB HD install to work properly.

To modify the hdstg2.img is pretty simple, just takes a few steps (ok - more then a few):

These instructions assume I already have a /new302 directory and have the esx-3.0.2-52542.iso and partitions.pyc files in it

Note: See Paul Ladonde post (http://www.vmware.com/community/thread.jspa?threadID=75792&start=0&tstart=0) to download[/b] the partitions.pyc[/b] file that has been patched.

mkdir /new302/oldiso

mkdir /new302/newiso

mkdir /new302/oldhdstg2

mkdir /new302/newhdstg2

mount /new302/esx-3.0.2-52542.iso /new302/oldiso -o loop

tar -C /new302/oldiso/ -cmf - . | tar -C /new302/newiso -xmf - .

(I used tar instead of cp to get the hidden files as well)

mount /new302/oldiso/VMware/base/hdstg2.img /new302/oldhdstg2 -o loop

tar -C /new302/oldhdstg2/ -cmf - . | tar -C /new302/newhdstg2 -xmf - .

umount /new302/oldhdstg2

umount /new302/oldiso

cp /new302/partitions.pyc /new302/newhdstg2/usr/lib/anaconda/partitions.pyc

(Answer yes to overwrite)

mkcramfs /new302/newhdstg2/ /new302/hdstg2.img

cp /new302/hdstg2.img /new302/newiso/VMware/base/hdstg2.img

(Answer yes to overwrite)

cd /new302/newiso

mkisofs -l -J -R -r -T -o /new302/esx-3.0.2-52542-new.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table /new302/newiso

Replace your old esx-3.0.2-52542.iso with this new one and follow Paul's steps to create the USB drive, you should now be set to go...

[dmismash]

I have tried SpiderMan's instructions and I am still getting the same error as before.... installation tree in that directory does not seem to match your boot media. I have used your method from an ESX host running 3.0.2 with Paul's .pyc file and a new iso of 3.0.2 and it still errors. Do you have a copy of your repaired hdstg2.img you can send me a link of? I would like to try it and see what I am doing wrong. Thanks.

dmismash@comcast.net

[dmismash]

Never mind my previous post. The original ISO I was using was bad. I made another ISO and then did all your steps and Paul's and I am all set. Thanks and please mark this as answered and reward some points to SpiderMon.

[Unix-Sysadmin]

Ahh, ok.

I got it working. I just recreated all images from scratch.

Maybe I will try the other suggetions later.

Thanks for all your help and support.

Message was edited by:

Unix-Sysadmin

[GuillaumeARRQ]

Thanks SpiderMon. I've wasted 2 DAYS (ok, it's not that much) trying to install from USB. Now it works thanks to you !

[info0012]

I'm looking for the file partitions.pyc fixed for ESX 3.5.0 booting with USB. I try the fix version for 3.0.2 but I still have the message The VMWare ESX Server 3 installation tree in that directory does not seem to match your boot media.

Thanks

[bk66md]

no luck loading 3.5 from usb for me yet - i'm having the issue "....tree in that directory does not seem to match you boot media", "an error occured reading the install form the iso images please check your iso images and try again", "device does not appear to contain red hat cd rom images"