* x86_64 architecture
* boot from optical media
* an httpd server with full distro
* a kickstart file that's known to work from optical media (I'll copy it below)
* no dhcp/tftp available (at the moment)
I'm having trouble getting the install to work right--and I think the root of the problem is a lack of a network install boot image for x86_64 media. When I find CentOS/RHEL 4 boot media, it's 386/586--and that won't do, as it will then only load a 32-bit os (I tried this already).
Has anyone licked this for x86_64/CentOS 4.x?
In the hopes that my problem is something else, I'll babble on a little further about what I've attempted so far:
With CentOS 5, there's a network boot disk available for x86_64, and I've used it happily--but we're not ready to move to CentOS 5 yet, so any new builds for the forseeable future have to be CentOS 4.
Here are things that work:
* I can boot from optical media and tell it to install the OS from that media
* I can boot from optical media and give it ks=http://blah/blah/ks.cfg -- this eventually works once I can configure the network manually
* the kickstart file is copied over the network, read, and is very nearly used properly
What doesn't work:
* Early on in the process, the install program attempts to unmount...something. A loopback device, so it's a disk image from someplace. It's trying to unmount an image from the CD when it shouldn't be thinking "cd!" at all once the kickstart file is read.
The relevant parts of my kickstart file are below--thanks in advance for any help!
# Kickstart file
url --url http://correct/url/goes/here
langsupport --default=en_US.UTF-8 en_US.UTF-8
network --device eth0 --bootproto static --ip aaa.bbb.ccc.ddd --netmask 255.255.255.0 --gateway aaa.bbb.ccc.1 --nameserver aaa.bbb.eee.fff --hostname xxxx
rootpw --iscrypted elided-for-my-convenience
authconfig --enableshadow --enablemd5
timezone --utc America/New_York
bootloader --location=mbr --append="rhgb quiet"