See my previous post, I discarded esx-custom.iso & replaced with the original ESX 3.5 ISO & have proceeded further
I tried that but the partitions.pyc file is still complaining.
Tried the 64607 Build of ESX (28th February Release) ISO on the USB, failed with the familiar error of ' The Tree not matching the media Type'
Sucess: Managed to install the 64607 build over SCSI (70GB U160 + Adaptec29320-R via auction) via HTTP...no other method including CD-ROM would worked
Almost Sucess: Installed over a existing Fedora 7 SATA Disk, but would not GRUB. Manually updated GRUB after mounting ESX's /boot, but Fedora's GRUB, didn't recognise VMFS , so reverting back to SCSI - ...
Good Luck All
Tried the VI 3.5 (64607 Build of ESX, 28th February Release) ISO on the USB, failed with the familiar error of ' The Tree not matching the media Type.
Used Paul's hdstg2.img file.
Have anybody managed to get a USB install of VI 3.5 working ?
Jan Erik Holo
I haven't gotten it to work. Paul's hdstg2.img file is for 3.01. if you loop mount the img you will see a lot of python files in the anaconda directory. They are not compatible with 3.5
Great post Gents.
I have been following the instructions in the post and have not had success.
Is it possible to store the "ks.cfg" file on the usb stick and build servers with the CD and usb key?
Currently try to create a standard build for ESX 3.5 (esx-3.5.0-64607).
Yeah can do. Boot to the ESX CD, at the grub prompt type (for USB key): esx ks=hd:sda1/ks.cfg method=cdrom (note path to you USB key may differ and not all keys seem to work).
Actually I have gotten 6 or 7 different vendors that make USB keys to work. It came down to 2 factors, the tool I used to format the key, and making sure I had the right reference to the USB drive, some systems it shows up as sda, or sdb, or even sdc, once in a while something odd. The easiest way I know to find the USB key is to do an OEM install of ESX, with the key plugged in and then during the RPM loading, jump to ALT-F2 and do cat /proc/partitions, looking for the USB device. The one thing I have never got to work, is booting from USB and building from USB, anaconda via the partition python script just gets confused between read-write media and what it expects as read-only media as the source for the ESX source files. Same basic issue that is noted in this thread. We go absolutely no where with VMware on this issue, and with ESXi released, VMware is not motivated to solve the issue. Which I can understand, although I do not agree with the perspective.
Has anyone had success with using this method for ESX 3.5? I've integrated the pyc script as per SpiderMon's instructions over here, but it's still throwing an unhandled exception at partitioning, similiar to fbedell's on page 2 of this thread. The only other thing that I'm doing different (aside from using 3.5) is using grub as bootloader, which shouldn't matter at this point in the process. Any advice would be very appreciated.
anybody have some luck installing 3.5 from usb?
I'm getting the error "...installation tree in that directory does not seem to match your boot media."
third bump's a charm...
Anyone have this working with 3.5 ISO yet?
My server CD-ROM drive is b0rked!
You're probably better off using Ultimate Deployment Appliance -> http://www.rtfm-ed.co.uk/?page_id=366
Or, if you are just doing an upgrade, use the tarball method or the VUM method.
If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside.
Robert X. Cringely, InfoWorld magazine
I ended up using the UDA and installing from pxe boot and ftp.
worked like a charm. I'd still love to know how to get a thumbdrive install to work
Hi, The link for partitions.pyc is dead. Does anyone have an alternative link?