I have successfully set up a very nice kickstart install with the i386 version of CentOS 4.3 and it works great. I am using a custom kickstart script and the kernel and initrd from disc1/images. But when I try to duplicate this for a 64 bit setup (changing paths in my tftp server, ks.cfg, etc to point to the 64 bit stuff) it successfully tftp's everything just as it should (tethereal output follows):
0.000000 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/pxelinux.0, Transfer type: octet 0.002503 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/pxelinux.0, Transfer type: octet 0.039763 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/pxelinux.cfg/01-00-0c-29-14-3a-c5, Transfer type: octet 0.045674 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/msgs/boot.msg, Transfer type: octet 0.522788 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/CentOS4.3/x86_64/vmlinuz, Transfer type: octet 2.487047 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/CentOS4.3/x86_64/initrd.img, Transfer type: octet
But then it never tries to get the ks.cfg. I am booting it with:
label centos kernel CentOS4.3/x86_64/vmlinuz append initrd=CentOS4.3/x86_64/initrd.img ramdisk_size=7000 ksdevice=eth0 ks=http://192.168.0.7/network-install/ks.cfg.x86_64
(that last line should be all one line)
in the /tftpboot/linux-install/pxelinux.cfg/01-00-0c-29-14-3a-c5 config file which it tftp's so it should know that it needs to get the ks.cfg.x86_64 file. I have this same setup working for i386 and it seems to work fine. I would guess there might be some difference in the initrd's but for some reason /linuxrc is a symlink to sbin/init which is a binary executable instead of a shell script. Anyone know why it isn't a shell? And why would my x86_64 kickstart be behaving different from my i386?
Any help is very much appreciated!
Hi,
On Fri, Aug 11, 2006 at 05:33:39PM -0700, Tracy R Reed wrote:
I have successfully set up a very nice kickstart install with the i386 version of CentOS 4.3 and it works great. I am using a custom kickstart
...
0.522788 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/CentOS4.3/x86_64/vmlinuz, Transfer type: octet 2.487047 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/CentOS4.3/x86_64/initrd.img, Transfer type: octet
But then it never tries to get the ks.cfg. I am booting it with:
label centos kernel CentOS4.3/x86_64/vmlinuz append initrd=CentOS4.3/x86_64/initrd.img ramdisk_size=7000 ksdevice=eth0 ks=http://192.168.0.7/network-install/ks.cfg.x86_64
(that last line should be all one line)
Are you sure your ksdevice is eth0? could it be i386->eth0 and x86_64->eth1
/usr/share/doc/anaconda-10.1.1.37 ... ksdevice Takes one of 4 types of argument which tells install what network device to use for kickstart from network: ... - An argument like 00:12:34:56:78:9a indicating the MAC address of a specific interface - The keyword `link' indicating that the first interface with link up ...
ksdevice=00:0c:29:14:3a:c5 or ksdevice=link ?
Cheers,
Tru
Tru Huynh wrote:
Hi,
On Fri, Aug 11, 2006 at 05:33:39PM -0700, Tracy R Reed wrote:
I have successfully set up a very nice kickstart install with the i386 version of CentOS 4.3 and it works great. I am using a custom kickstart
...
0.522788 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/CentOS4.3/x86_64/vmlinuz, Transfer type: octet 2.487047 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/CentOS4.3/x86_64/initrd.img, Transfer type: octet
But then it never tries to get the ks.cfg. I am booting it with:
label centos kernel CentOS4.3/x86_64/vmlinuz append initrd=CentOS4.3/x86_64/initrd.img ramdisk_size=7000 ksdevice=eth0 ks=http://192.168.0.7/network-install/ks.cfg.x86_64
(that last line should be all one line)
Are you sure your ksdevice is eth0? could it be i386->eth0 and x86_64->eth1
/usr/share/doc/anaconda-10.1.1.37 ... ksdevice Takes one of 4 types of argument which tells install what network device to use for kickstart from network: ... - An argument like 00:12:34:56:78:9a indicating the MAC address of a specific interface - The keyword `link' indicating that the first interface with link up ...
ksdevice=00:0c:29:14:3a:c5 or ksdevice=link ?
Cheers,
Tru
I have made a boot cdrom and in that one I use these switches for append (and it is working for both i386 and x86_64) : append initrd=initrd.img ramdisk_size=8192 ks=http://192.168.10.241/ks.cfg ksdevice=eth0 nofirewire nopcmcia skipddc noparport
I tried the ksdevice=link but that didn't work.
What is the output from the Alt+F3(or was it F4) when you boot your kickstart install ?
/Mats --- "Those that sacrifice essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Ben Franklin (1759)
Mats Karlsson wrote:
What is the output from the Alt+F3(or was it F4) when you boot your kickstart install ?
Unfortunately it seems the other consoles are not yet active (no getty or shell or anything running) at the point where the OS tries to mount the root fs. So I cannot switch over and see what it said. The last thing the kernel says is:
VFS: Cannot open root device "<NULL>" or unknown-block(8,2) Pleas append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)
Tracy R Reed wrote:
VFS: Cannot open root device "<NULL>" or unknown-block(8,2) Pleas append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)
Another datapoint:
My pxeboot config file (named with the mac address of the machine and downloaded by tftp) looks like this:
default centos timeout 5 prompt 1 display msgs/boot.msg
label centos kernel CentOS4.3/x86_64/vmlinuz append initrd=CentOS4.3/x86_64/initrd.img ramdisk_size=7000 ksdevice=eth0 ks=http://192.168.0.7/network-install/ks.cfg.x86_64
If I change the three instances of x86_64 to i386 everything works perfectly and it installs the i386 version. I thought maybe my x86_64 kernel and initrd that I copies from disc1/images/pxeboot were corrupt but I just downloaded them again from http://mirror.centos.org/centos/4/os/x86_64/images/pxeboot/ and they md5sum the same.
Tracy R Reed wrote:
append initrd=CentOS4.3/x86_64/initrd.img ramdisk_size=7000
Someone on IRC pointed out that ramdisk_size=7000 was not a good idea. I don't know why I originally put that there. But unlike the i386 initrd the x86_64 initrd is bigger than 7M!
Thanks for all your help.
Tru Huynh wrote:
Are you sure your ksdevice is eth0? could it be i386->eth0 and x86_64->eth1
I have other x86_64 boxes and they have always made the first ethernet device eth0. I have never heard of it being any other way. But just in case I tried it with ksdevice=link and it did not work any better.
-
Mats Karlsson -
Tracy R Reed -
Tru Huynh