Hello list,
I try to do an automated network installation of centos 5.2, following the redat documentation at http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/p... However, when installing I get promptet for various things, like which network interface I would like to use for installation, or the location of the install medium. But thats not what I wanted, I want to start the boot process, and then leave the box untill it is installed.
What I did: First a manual install form DVD. I then used the kickstart file /root/anaconda-ks.cfg for a network installation. I changed the install line from cdrom to url:
install url --url http://9.0.0.1/all/repository/CentOS5.2
This url contains the whole DVD (and can be viewed in a webbrowser). Then I generated the following entry in my pxe control file (default):
LABEL centos5.2_cluto_cnode MENU LABEL CentOS 5.2 cluto ^node kernel distro/centos5.2/vmlinuz append initrd=distro/centos5.2/initrd.img ramdisk_size=7494 ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
This is part of a boot menue, therefor the MENU entry. The url of the kickstart file is also valid, I can wget it.
Now since I get asked all these questions at boot time, I suspect that the kickstart file is not there to answer these questions.
I would be greatful for any suggestions on how to further debug or solve this.
Isaac
_____________________________________________________________________ Vorstand: Ertu Uysal, Axel Queck Vorsitzender des Aufsichtsrats: Bernhard Bruscha Sitz der Gesellschaft: Tuebingen Amtsgericht Stuttgart HRB 381299
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf
Of
Isaac Hailperin Sent: Tuesday, February 03, 2009 2:46 PM To: centos@centos.org Subject: [CentOS] kickstart won't kick-off via network
What I did: First a manual install form DVD. I then used the kickstart file /root/anaconda-ks.cfg for a network installation.
Now since I get asked all these questions at boot time, I suspect that the kickstart file is not there to answer these questions.
It does use it, it just doesn't find the network-block in ks.cfg. Does your ks.cfg contain some lines for the networking? You didn't modify the ks.cfg you mention above, did you?
You can open the ks.cfg you already have and then tweak with the wizard.
I used the kickstart wizard just yesterday to make my own ks.cfg, I suggest you do the same to add the network part in ks.cfg as well as other stuff. Then redo what you did before. FWIW, I also did a netinstall, like you but slightly different, with the ks.cfg on a floppy. The gotcha' here is that the netinstall iso doesn't acknowledge the "linux ks=floppy"-line when I boot with the netinstall-iso. Booting from cd1 from the regular 6cd-package and then adding "linux ks=floppy" does. From there I chose http-install and added mirror.centos.org and the proper path to the v5.2 i386.
HTH.
Isaac Hailperin wrote on Tue, 03 Feb 2009 14:45:44 +0100:
append initrd=distro/centos5.2/initrd.img ramdisk_size=7494 ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
this is not enough, you have to tell PXE about the network, which nic to use etc. I think there is a tutorial about doing PXE instalaltions on the wiki.
Kai
On Tue, 2009-02-03 at 15:42 +0100, Kai Schaetzl wrote:
Isaac Hailperin wrote on Tue, 03 Feb 2009 14:45:44 +0100:
append initrd=distro/centos5.2/initrd.img ramdisk_size=7494 ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
this is not enough, you have to tell PXE about the network, which nic to use etc. I think there is a tutorial about doing PXE instalaltions on the wiki.
You are right: "ksdevice=eth1" did the trick. Found at http://wiki.centos.org/TipsAndTricks/KickStart
Thank you!
Isaac
_____________________________________________________________________ Vorstand: Ertu Uysal, Axel Queck Vorsitzender des Aufsichtsrats: Bernhard Bruscha Sitz der Gesellschaft: Tuebingen Amtsgericht Stuttgart HRB 381299
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Isaac Hailperin wrote:
On Tue, 2009-02-03 at 15:42 +0100, Kai Schaetzl wrote:
Isaac Hailperin wrote on Tue, 03 Feb 2009 14:45:44 +0100:
append initrd=distro/centos5.2/initrd.img ramdisk_size=7494 ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
this is not enough, you have to tell PXE about the network, which nic to use etc. I think there is a tutorial about doing PXE instalaltions on the wiki.
You are right: "ksdevice=eth1" did the trick. Found at http://wiki.centos.org/TipsAndTricks/KickStart
The order of NIC detection/naming at bootup seems to be more or less random as of Centos 5.x. How do you know which name to choose here?
On Tue, 2009-02-03 at 11:17 -0600, Les Mikesell wrote:
Isaac Hailperin wrote:
On Tue, 2009-02-03 at 15:42 +0100, Kai Schaetzl wrote:
Isaac Hailperin wrote on Tue, 03 Feb 2009 14:45:44 +0100:
append initrd=distro/centos5.2/initrd.img ramdisk_size=7494 ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
this is not enough, you have to tell PXE about the network, which nic to use etc. I think there is a tutorial about doing PXE instalaltions on the wiki.
You are right: "ksdevice=eth1" did the trick. Found at http://wiki.centos.org/TipsAndTricks/KickStart
The order of NIC detection/naming at bootup seems to be more or less random as of Centos 5.x. How do you know which name to choose here?
In order to avoid this, you can use the "ksdevice=bootif" to use the interface from which the system booted...
-I
Ian Forde wrote:
append initrd=distro/centos5.2/initrd.img ramdisk_size=7494 ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
this is not enough, you have to tell PXE about the network, which nic to use etc. I think there is a tutorial about doing PXE instalaltions on the wiki.
You are right: "ksdevice=eth1" did the trick. Found at http://wiki.centos.org/TipsAndTricks/KickStart
The order of NIC detection/naming at bootup seems to be more or less random as of Centos 5.x. How do you know which name to choose here?
In order to avoid this, you can use the "ksdevice=bootif" to use the interface from which the system booted...
I'd like to be able to boot from a CD or usb drive into a kickstart re-install in remote locations that don't have network booting infrastructure and just enough hands-on expertise to insert a CD or USB key - and have some way to get the several NICs re-assigned their corresponding IP addresses.
On Tue, 2009-02-03 at 18:39 +0100, Ian Forde wrote:
In order to avoid this, you can use the "ksdevice=bootif" to use the interface from which the system booted...
good to know, thank you.
Isaac
_____________________________________________________________________ Vorstand: Ertu Uysal, Axel Queck Vorsitzender des Aufsichtsrats: Bernhard Bruscha Sitz der Gesellschaft: Tuebingen Amtsgericht Stuttgart HRB 381299
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
On Tue, Feb 03, 2009, Les Mikesell wrote:
Isaac Hailperin wrote:
On Tue, 2009-02-03 at 15:42 +0100, Kai Schaetzl wrote:
Isaac Hailperin wrote on Tue, 03 Feb 2009 14:45:44 +0100:
append initrd=distro/centos5.2/initrd.img ramdisk_size=7494 ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
this is not enough, you have to tell PXE about the network, which nic to use etc. I think there is a tutorial about doing PXE instalaltions on the wiki.
You are right: "ksdevice=eth1" did the trick. Found at http://wiki.centos.org/TipsAndTricks/KickStart
The order of NIC detection/naming at bootup seems to be more or less random as of Centos 5.x. How do you know which name to choose here?
I cheat and plug both NICs into switch(es) that will provide DHCP during installation, then sort out which is which once the install is complete. It's easy here as our in-house install server is on a public network, accessible via NAT from the private NIC so looking at the IP address assigned (public or private block) eliminates the ping-and-pull-cable test to figure out which NIC is which.
Bill
Les Mikesell wrote on Tue, 03 Feb 2009 11:17:15 -0600:
The order of NIC detection/naming at bootup seems to be more or less random as of Centos 5.x. How do you know which name to choose here?
I find that I don't have any problems with this. I usually disable dhcp on eth1 and have no cable in it during installation. eth0 is always the port that is labelled eth0.
Kai
On Wed, 2009-02-04 at 11:31 +0100, Kai Schaetzl wrote:
Les Mikesell wrote on Tue, 03 Feb 2009 11:17:15 -0600:
The order of NIC detection/naming at bootup seems to be more or less random as of Centos 5.x. How do you know which name to choose here?
I find that I don't have any problems with this. I usually disable dhcp on eth1 and have no cable in it during installation. eth0 is always the port that is labelled eth0.
I don't have problems either. In fact, ksdevice=bootif does not work for me.
Isaac
_____________________________________________________________________ Vorstand: Ertu Uysal, Axel Queck Vorsitzender des Aufsichtsrats: Bernhard Bruscha Sitz der Gesellschaft: Tuebingen Amtsgericht Stuttgart HRB 381299
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
On Wed, Feb 04, 2009 at 11:48:29AM +0100, Isaac Hailperin wrote: ...
I don't have problems either. In fact, ksdevice=bootif does not work for me.
please trim your footer/disclaimer when sending to a public mailing list or send from another email adress.
Thanks,
Tru
Isaac Hailperin wrote:
The order of NIC detection/naming at bootup seems to be more or less random as of Centos 5.x. How do you know which name to choose here?
I find that I don't have any problems with this. I usually disable dhcp on eth1 and have no cable in it during installation. eth0 is always the port that is labelled eth0.
I don't have problems either. In fact, ksdevice=bootif does not work for me.
How many NICs and connections do you have? The bulk of my production servers have 4 or more NICs with 2 or 3 active connections and as of 5.x, until the install gets to the point where HWADDR= is set for each NIC in its /etc/sysconfig/network-scripts/ifcfg-eth? file the names are not predictable. In fact, I've even tried pre-configuring them on swappable drives built on similar machines and often the files with the correct HWADDR are renamed with a .bak extension at first boot in the real server and replaced with non-working defaults. Does anyone know how to avoid that? It has been very frustrating working with remote machines since device detection order was randomized.
Isaac Hailperin wrote:
I don't have problems either. In fact, ksdevice=bootif does not work for me.
How many NICs and connections do you have?
Two. Both are connected, but on one network there is nothing happening at that stage, meaning no servers offering any services.
Mine usually flip in pairs - that is, the pair on the motherboard will be either eth0/eth1 or eth2/eth3 (etc.) with the same one of the pair always picked as eth0 or eth2. You might not have much of a problem with only 2 NICs of the same type. We generally want to run on the Intel server-class add-in cards instead of the motherboard NICs that tend to be Broadcoms. It's a habit developed under Windows - I'm not sure if there is that much difference on Linux, but I have to identify the NIC one way or another and I'd like to find a reliable way to do it when swapping in pre-loaded drives.
Hi
On Wed, Feb 04, 2009 at 11:48:29AM +0100, Isaac Hailperin wrote:
I don't have problems either. In fact, ksdevice=bootif does not work for me.
try ksdevice=link if you only have one interface plugged
Tru
-
Bill Campbell -
Ian Forde -
Isaac Hailperin -
Isaac Hailperin -
Kai Schaetzl -
Les Mikesell -
Sorin Srbu -
Tru Huynh