On Tue, Sep 2, 2008 at 4:18 PM, Joseph L. Casale <JCasale@xxxxxxxxxxxxxxxxx> wrote:
>WHat do you mean?
Do you boot from one of the NICS, or a CD, or what?
If you boot from a NIC via a TFTP server, you may be encountering the issue
I describe which simply needs a kernel arg to fix you up.
jlc
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
Hi Joseph
I boot via NIC0 and my configurations are as follows:
pxe (for node3):
default ks
prompt 0
label ks
kernel vmlinuz
append initrd=initrd.img ramdisk_size=9216 ksdevice=bootif noapic acpi=off ks=http://192.168.11.1/kickstart/n03.ks
ipappend 2
kickstart file (for node3):
# Kickstart file automatically generated by anaconda.
install
lang en_US.UTF-8
keyboard us
network --device eth0 --bootproto dhcp --hostname n003.example.com
network --device eth1 --onboot no --bootproto dhcp --hostname n003.example.com
network --device eth2 --onboot no --bootproto dhcp --hostname n003.example.com
network --device eth3 --onboot no --bootproto dhcp --hostname n003.example.com
url --url http://192.168.11.1/source
rootpw --iscrypted ?????????????????????????????????
firewall --disabled
authconfig --enableshadow --enablemd5
selinux --disabled
timezone --utc Asia/Jerusalem
bootloader --location=mbr --driveorder=sda --append="noapic acpi=off"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
zerombr
clearpart --all --drives=sda
part /boot --fstype ext3 --size=100 --> part pv.2 --size=0 --grow -->volgroup VolGroup00 --pesize=32768 pv.2
.
.
.
If you made it all the way down here ... I did try to put ksdevice=eth0 in the PXE configuration file, but it only made things worse :-(
--
TIA
Paolo
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
