Glad to hear it. Now try this:
esx boot text nofb usb ks=hd:sdb1:/ks.cfg
(where sdb1 is the device of the USB flash, replace as necessary)
with the ks.cfg file in the root directory of the USB flash drive.
What method do you use to update hdstg2.img within the ISO. I'm using WinImage which treats the ISO as closed/read-only. I'm trying to aviod reburning a CD with the new file with nero and creating an ISO from that...
I'm been doing some work on this over the weekend. This is what I have got so far:
I changed the syslinux.cfg to disable graphical installations (not supported with hard disk media installs - and added a menu option to install my server(s)
append initrd=initrd.img noapic nomediacheck debug usb
append initrd=initrd.img usb
append ks initrd=initrd.img text usb ks=hd:sda4:/kickstart/default.cfg
append expert initrd=initrd.img usb
append ks initrd=initrd.img usb
append initrd=initrd.img lowres usb
append ks initrd=initrd.img usb ks=hd:sda4:/kickstart/esx01.cfg
append ks initrd=initrd.img usb ks=hd:sda4:/kickstart/esx02.cfg
append ks initrd=initrd.img usb ks=hd:sda4:/kickstart/esx03.cfg
The kickstart/default.cfg stops the prompts to do with being asked what disk to use and how to find the ISO file
\# Auto-Generated Scripted Install Configuration file.
\# This file is used for VMware ESX Server Scripted Install Deployment
\# Installation Method
harddrive --partition=sda4 --dir=/
For a bit of fun I modified the boot.msg file to give friendly information
- To install or upgrade 03VMware ESX Server 07 in text mode, press 0f 07
- Note: Graphical Mode is not supported with ESX-on-a-Stick
One real problem I can see with this - is how much /dev/sd[i]NN[/i] varies from system to system. I see it change depending if the SAN is connected (I get /dev/sdk4) the USB stick always appears as the last drive. Alternatively, on my HP proliants - because the first LUN is /ccisso/c0d0, the USB stick appears without the SAN connected the USB drive is /dev/sda4.... I wish we could hard-code the usb device to always be /dev/sdz - that way I could move the key from system to system and 9/10 it would know which disk contained the kickstart files and the ISO...
I believe that you have to remove the U3 software to get rid of that darn virtual cd-rom drive that it tries to run. I just bought a cruzer and had the same issue until I removed the U3 software.
Yeah, I got the cruiser to work by using the boot disk image tool... was able to do that without need to get rid of the U3 partition...
ps I bought WinISO today to assist injecting the IMG file provide by Paul...
well, I'm not having any fun with this...
I bought WinISO today - and I was able to open the ESX iso and add the file that Paul modified... BUT now the Anaconda installer believes the ISO is not there...
I've checked and the ISO works fine as a normal CD...
The only thing that's different between my two ISOs - is the adding of the .IMG file and the fact that its been processed by WinISO... I've checked thier FAQ's and emailed support...
Has anyone got this working without error... not sure where I am going wrong... my only barrier is the python error and the img file...
Paul what are your thoughts?
I can confirm that this is the exact same issue as I am experiencing. Mike I am glad I read your email as I was loosing my mind.
LOL... know what you mean... I feel like I/we are on the cusp of cracking this one... I notice Paul's gone a bit quiet - lets hope he's looking at this one for us
Because I'm lost on issues to with IMG files... kickstart/syslinux.cfg I'm fine, but that's about it...
When you boot the usb drive then use the real cd-rom as install souce does your kicks file work? Mine isn't
If I uses a plan unmodified ESX ISO - it finds the ISO fine... and then I get the anaconda/python message...
if I use the IMG provided by Paul, and inject to the ISO... then it comes up message say that its not a valid redhat package something/something... I forget right now... I can grab it - but it sounds like you have the same error?
Yes same error.
Do you mind posting your esx01 kicks file? or PM me
If you read up above this post I cut & pasted my:
and a basic "default.cfg" kickstart script to answer where the hard-drive is...
If a server has /dev/sda/ /dev/sdb and then you plug a USB key in it will be /dev/sdc[i]N[/i]. Go to another server with sda, sdb, sdc then the USB key becomes /dev/sdd... Hope I'm not teaching grama to suck eggs here!
I would be great if the USB key was found before SAN/RAID LUNs and was always /dev/sda... I'm disconnecting the SAN before installation (which is a good practise for local installs) but pain-in-the-ass for boot-from-SAN installations where a USB key would be handy. I guess if you have the SAME number of LUNs presented to each blade your OK, but if not then it reduces the level of automation you can do...
So the long and short of it is that in ALL of my files you may need to find and replace the sda4 value...
I've a longer kickstart script that does post-configuration (vSwitches, Software iSCSI, Create Users, and so on) I will attach it here. It works with my PXE appliance - but obiviously never tested it with "ESX-on-a-Stick"
(that the sub-chapter heading in the book)
There's two files here:
esx01 - for servers that present /dev/sda /dev/sdb to the installer and
esx03 - for HP Smart Raid Array Controllers that present /cciss/c0d0
Just a SWAG, does your new ISO have the .discinfo file in it?
Yup... not changing the ISO... just the img file...
hmmm, I am having no luck with this at all..always get "Operating System Not Found" (i.e. never even tries to boot).
It's an Imation 2GB USB
Syslinux done etc
Can I just check... Anyone got this working without error yet. I mean done a basic manual installation from a key...
I'm just trying to work out if its something I've done or if we still have fundemental problems to resolve?