David I had a imition 1GB drive and it wouldn't boot either. I had to use a tool in the Syslinux download. I have a feeling you might need to do this to...
1. From your Windows PC download the syslinux tools from:
2. Extract the ZIP file to you Windows PC
3. Transfer this file to Linux or your Service Console
4. Make a directory and extract the syslinux files to that location with
unzip syslinux-3.36.zip d /root/syslinux
5. Plug-in your USB Stick into Linux or the Service Console
When you do this the system should recognize the device if you are at the physical console you would see the device being recognized and would tell you what the /dev/sdn name is of the USB stick. If you miss this message then you can use the command
dmesg | grep sd
This will list all the SCSI devices on the system like so and I can see the USB device has been given the identity of /dev/sdl
SCSI device sda: 2072576 512-byte hdwr sectors (1012 MB)
sda: Write Protect is off
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host = 0, driver = 08
Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready
sda: block size assumed to be 512 bytes, disk size 1GB.
sda: test WP failed, assume Write Enabled
sda: I/O error: dev 08:b0, sector 0
SCSI device sdl: 2072576 512-byte hdwr sectors (1012 MB)
sda: Write Protect is off
6. Next we will use Linux command fdisk to delete any existing partition table, and find out the number of cylinders, heads and sectors are on the disk with
Below is a print out from an Imation Mini Flash Drive
Disk /dev/sdl: 1061 MB, 1061158912 bytes
33 heads, 62 sectors/track, 1012 cylinders
Units = cylinders of 2046 * 512 = 1047552 bytes
9. Next transfer the mkdiskimage to the USB device by
perl mkdiskimage /dev/sdn -4 1012 33 62
This took about 15-20 minutes on my USB stick. The switch -4 indicates an image which is suitable for a zipdisks. The following numbers represent cylinders, heads and sectors. After this command completes you should be able to run fdisk /dev/sdn again to see a partition FAT16 has been created. In my case this reported:
I create my usb key to boot and install esx 3.0.1 automatically
I have following all the step. It was a bit difficulte to modify the .iso for include the file hdstg2.img but I succed
I explain if it can help somebody :
First put the Vmware esx 3.0.1 CD in your ESX CDROM
dd if=/dev/cdrom of=/folder/esx-3.0.1.iso bs=1024
that's create the Iso image of the ESX CDROM
Now we must mount the Iso
mount -o loop -t iso9660 /folder/esx-3.0.1.iso /mnt/iso
The iso file is mounted so we need to copye it in another folder /root/newiso by exemple
cp -r /mnt/iso/* /root/newiso/
Now you can replace the file hdstg2.img in /root/newiso/VMware/base/
For create the new iso you need to install mkisofs.
Take the mkisofs-1.10-11.asp.i386.rpm (the last)
Copy it on the ESX and start : rpm -hiv mkisofs-1.10-11.asp.i386.rpm
To create the iso run :
mkisofs -r -R -J -o /tmp/esx-3.0.1-v2.iso /root/newiso
Now you have the Iso with the new file
Be carful : I have done all and my server boot correctly on the USB Key, I select Hard-Drive and /dev/sda1 for the new image. BUT I have many anaconda error and the installation abort
That's all the errors :
File "/usr/bin/anaconda" , line 108, in ?
intf.run(id, dispach, configFileData)
File "/tmp/anaconda_build//usr/lib/anaconda/text.py" line 425 in run
File "/tmp/anaconda_build//usr/lib/anaconda/display.py" line 264 in currentStep
File "/tmp/anaconda_build//usr/lib/anaconda/display.py" line 159 in gotoNext
File "/tmp/anaconda_build//usr/lib/anaconda/display.py" line 227 in moveStep
File "/tmp/anaconda_build//usr/lib/anaconda/packages.py" line 147 in readPackages
File "/tmp/anaconda_build//usr/lib/anaconda/hardrive.py" line 208 in readHeaders
File "/tmp/anaconda_build//usr/lib/anaconda/hardrive.py" line 145 in mountMedia
If somebody able to help me to solve it I think I can publish a complet post to make the installation of ESX 3.0.1 just using an usb key ..
Message was edited by:
mmm, looks like the python error is still there...
I injected the IMG file using WinISO... and will give your method a try and see what I find...
Make sure the primary partition is marked as "active" otherwise it won't be bootable. Good ol' FDISK will do this, option (2).
Everything works for me other then the fact that I can not use the local USB iso image. I can use a local CD though. So close yet so far away.
Yep.. the USB sticks primary is marked as bootable... mkdiskimage.pl did all that for me...
My problems are further down the line with the customised version of the ESX3.0.1 ISO with the hdstg2.img...
Not had a chance to try the command-line method... to be honest I think the problem is with the hdstg2.img file...
Do you have this working without errors, Paul?
Yes, I installed ESX on two of my own servers this way. Let me go back and review your posts to see if I can find anything peculiar...
I've been documenting the process for the new book. It's part of a chapter about ESX on the command-line and includes:
ESX on a stick
Network & Storage esxcfg commands
User Management (su, sudo config, LDAP)
Can I send you the portion on "Esx on a stick" I've writen so far. Perhaps there's something I'm missing - and I'm too close to spot it...
To summarize an ordinary ISO works but gives the Python error... the customized ISO with the .img file throws up an error... I will sceen grab the error...
I don't know if I explain correctly my precedent post but with my method your are able to custumize the ISO to put the .img file giving by Paul.
You boot with USB ans select your correct /dev/sda.... and the key find well the Iso file.
But the python problem still...
I post here the anacdump.log from debug screen if can it help someone.
Traceback (most recent call last):
File "/usr/bin/anaconda", line 1087, in ?
intf.run(id, dispatch, configFileData)
File "/tmp/anaconda_build//usr/lib/anaconda/text.py", line 425, in run
File "/tmp/anaconda_build//usr/lib/anaconda/dispatch.py", line 264, in currentStep
File "/tmp/anaconda_build//usr/lib/anaconda/dispatch.py", line 159, in gotoNext
File "/tmp/anaconda_build//usr/lib/anaconda/dispatch.py", line 227, in moveStep
File "/tmp/anaconda_build//usr/lib/anaconda/packages.py", line 147, in readPackages
File "/tmp/anaconda_build//usr/lib/anaconda/harddrive.py", line 208, in readHeaders
File "/tmp/anaconda_build//usr/lib/anaconda/harddrive.py", line 145, in mountMedia
Local variables in innermost frame:
self: Mar 23 08:07:21 loader: Installer SCSI detection: adding LUN sda/'Kingston DataTraveler II+'
Wow... my error is much shorter than that!
I have "Device /dev/sdb4 does not appear to contain Red Hat CD-ROM images..."
Anyway, I'm gonna try making my ISO by the DD method and report back my findings later...
I could have sworn that error message (for me, in the past) is supposed to say "...does not appear to contain ESX Server 3.01 CD-ROM images." Any chance you're using files from a RH distribution?
(Just a shot in the dark...)
The version that I'm using is your patched version which I downloaded from:
Which was meant to fix the python error...???
Could be the wrong file is on the webserver???
I will check on it this weekend. PLEASE don't send me an invoice for all your billable time if this ends up being my bad!
Well, I've had some progress...
I used mkisof to create the ISO... so it looks like WinISO isn't so hot after all...
However, I still have an error... get past all the install questions... and then it fails. I think I have the same anaconda errors as others have:
I'm on a HP Proliant DL385 G1. I have two other servers but they don't support from USB key. So I can't test to see if this server specific...
I've attached my error message from the ILO to this post...
error.jpg 67.9 K
I will check on it this weekend. PLEASE don't send
me an invoice for all your billable time if this ends
up being my bad!
Paul, no worries mate... without your input we haven't got this far... so your efforts are appreciated... at some stage I would like understand the python error (in a rough way to explain to others) but that's for later...