[rhn-users] Kickstart Issue - Custom Bootdisk to Network Install
Warren_Crigger at navyfederal.org
Warren_Crigger at navyfederal.org
Fri Jul 14 17:10:58 UTC 2006
On 7/13/06, Warren_Crigger at navyfederal.org
<Warren_Crigger at navyfederal.org> wrote:
>>
>> Thanks in advance for any help! Sorry in advance too for such a long
mail,
>> but I hope I provided enough details.
>>
>> I have been tasked with setting up automated linux installs for our
company.
>> This was an easy task for SuSE (even though I like RH/Fedora/CentOS
better,
>> but I gotta do both =p), but I'm running into issues with RHEL4AS.
>>
>> I do not have the luxury of using DHCP and the normal method of
kickstart,
>> so I made a custom boot CD with the isolinux directory and TRANS.TBL
file on
>> it from the actual RHEL4AS disk (that's it!). I can boot normally and
from
>> there give it testing kickstart boot options which are:
>>
>> linux ks=http://<ip>/profiles/ks.cfg ip=<ip> netmask=<netmask>
>> gateway=<gateway> ksdevice=eth0
>>
>> It then loads the kernel, starts to grab files off the remote server
(see
>> logs below), fires up anaconda, detects the video/mouse/etc, and then
says:
>>
>> "you are trying to install on a machine which isn't supported by this
>> release of Red Hat Enterprise Linux ES"
>Odd that we switched from AS to ES here. What is in the remote tree?
>Can you install from the network installation tree interactively? I
>don't recall the error you get when trying to install from a tree that
>doesn't match the boot image used ... but make sure there isn't a
>mismatch there.
Good catch, I didn't notice that. I don't even have ES media, I'm not
sure where that's coming from. The repository holds RHEL4AS data laid out
per the documentation. I'll double check to make sure it wasn't just a
typo on my part, but that is very odd and I don't think that it is.
>> The test machine I'm installing on is a Dell PE1650 (tried it with and
>> without the Dell partition). You can install RHEL4AS on it fine with
the
>> CD's, but that's what I'm trying to avoid:
>>
>> Remote access logs:
>>
>> [13/Jul/2006:16:47:16 -0400] "GET /./profiles/ks.cfg HTTP/1.0" 200
1246 "-"
>> "-"
>> [13/Jul/2006:16:47:17 -0400] "GET
>> /media/rhel4/RedHat/base/updates.img HTTP/1.0" 404 1045 "-"
>> "-" <----missing file, but not on the CD either
>I'm pretty sure this is normal and of no consequence. I believe this
>was used in the past to allow older boot images to be used to perform
>installs/upgrades. Now it seems you must use the matching version.
After some research it looks like that file may be needed for customized
installs, which is not what I'm trying to accomplish (at least not yet).
>John
Warren Crigger
Sr. UNIX Network Engineer
ECommerce Engineering Support
Navy Federal Credit Union
_______________________________________________
rhn-users mailing list
rhn-users at redhat.com
https://www.redhat.com/mailman/listinfo/rhn-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rhn-users/attachments/20060714/4070a783/attachment.htm>
More information about the rhn-users
mailing list