Login or Register to Ask a Question and Join Our Community


UNIX for Advanced & Expert Users

PXE diskless boot fails

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users PXE diskless boot fails
# 8  
Old 06-04-2010
Why would it not receiving DHCP have anything to do with NFS? It shouldn't be trying to receive DHCP at all. That it fails suggests a general network problem -- there's no good reason I can think of it shouldn't be able to receive DHCP again after booting, even if that's pointless after booting off DHCP.
# 9  
Old 06-05-2010
I agree with you but have no clue. DHCP server definitely works as it receives configuration at first (and also - other computers that do not boot from network receive IP addresses).
I tried to change the APPEND line in /tftpboot/pxelinux.cfg/default from:
Code:
APPEND root=/dev/nfs initrd=initrd.img-2.6.32-22-generic nfsroot=192.168.1.115:/nfsroot ip=dhcp rw

to:
Code:
APPEND root=/dev/nfs initrd=initrd.img-2.6.32-22-generic  nfsroot=192.168.1.115:/nfsroot ip=none rw

and then it just did not show the IP-Config lines at all and immediately showed these lines:
Code:
/init: .: line 3: can't open /tmp/net-eth0.conf
Kernel panic- not syncing" Attempted to kill init!

I also tried to remove the IP address and colon in this APPEND line (saw an old bug on that) but it did not help either.

Thanks again

---------- Post updated at 02:38 AM ---------- Previous update was at 02:02 AM ----------

I think that the problem is that the DHCP server is not answering the later DHCP requests - I ran tcpdump for broadcasts and can clearly see that for the initial request that is sent during boot there is a reply and the later sequence of requests remain unanswered.

This is my /etc/dhcp3/dhcpd.conf file:
Code:
allow booting;
allow bootp;

subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.2 192.168.1.99;
  option broadcast-address 192.168.1.255;
  option routers 192.168.1.1;
  option domain-name-servers 192.168.1.1;

  filename "/pxelinux.0";
  next-server 192.168.1.115;
}

host pxe_client {
  hardware ethernet 00:0C:29:79:86:C1;
  fixed-address 192.168.2.3;
}

I also tried to remove the last fixed-ip part but it does not change anything.
Maybe it's something with the "allow" directives? (I took this file from the manual)

---------- Post updated at 02:47 AM ---------- Previous update was at 02:38 AM ----------

Addition:
The difference between DHCP requests is their lengths: while the initial ones (that are answered) are of length 548, the latter ones are only 271. Though, all other details (mainly MAC) are the same

---------- Post updated at 03:39 AM ---------- Previous update was at 02:47 AM ----------

Now I found how to get some more info:

First (answered) request and its response:
Code:
03:32:00.255217 IP (tos 0x0, ttl 20, id 1, offset 0, flags [none], proto UDP (17), length 576)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:79:86:c1 (oui Unknown), length 548, xid 0x2a7986c1, secs 4, Flags [Broadcast] (0x8000)
      Client-Ethernet-Address 00:0c:29:79:86:c1 (oui Unknown) [|bootp]
03:32:00.317616 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    yotam-server.local.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300, xid 0x2a7986c1, secs 4, Flags [Broadcast] (0x8000)
      Your-IP 192.168.1.3
      Server-IP yotam-server.local
      Client-Ethernet-Address 00:0c:29:79:86:c1 (oui Unknown) [|bootp]

Latter (unanswered) request:
Code:
03:32:19.957269 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 299)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [no cksum] BOOTP/DHCP, Request from 00:0c:29:79:86:c1 (oui Unknown), length 271, xid 0xb4b70b15, secs 1, Flags [none] (0x0000)
      Client-Ethernet-Address 00:0c:29:79:86:c1 (oui Unknown) [|bootp]



---------- Post updated at 01:39 PM ---------- Previous update was at 03:39 AM ----------

I managed to partially overcome the problem: I made a dedicated PXE configuration file for the machine (name after its MAC) and in it I changed the APPEND line to:
Code:
APPEND root=/dev/nfs initrd=initrd.img-2.6.32-22-generic nfsroot=192.168.1.115:/nfsroot ip=192.168.1.3:192.168.1.115:192.168.1.1:255.255.255.0:::none rw

Now I am able to boot the machine and load X. The problem is that it is annoying to do that and should work without this workaround...
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Linux

Problem in displaying message on RHEL6 on EFI during PXE boot

Hi, I am doing PXE boot for RHEL6.4 on EFI and want to display custom messsage before loading vmlinuz and initrd.img, which is not working. boot server side (In case of BIOS client): In /var/lib/tftpboot/default file I am putting the message in below format: SAY hello world boot... (0 Replies)
Discussion started by: indus123
0 Replies

2. Red Hat

RHEL6 Diskless Remote boot fail

Hi guys, I've been trying to set up a server for disk-less booting of remote machines on a network. The server host OS is RHEL6 and I have configured dhcp, tftp and nfs services which are proven to be working since I am able to install RHEL6 through pxe boot. Now I want it to serve for disk-less... (0 Replies)
Discussion started by: aninmuk
0 Replies

3. Solaris

T5220 fails to boot

One of our T5220 servers fail to boot due to following error: ERROR: The following devices are disabled: XAUI1 XAUI0 I can't see any disabled components in SP console, any idea what is the problem? (1 Reply)
Discussion started by: belalr
1 Replies

4. Red Hat

pxe boot server

Hi Hoping someone can help ove setup a pxe/dhcp boot server for auto installs on centos My server seems to be providing dhcp fine but the installation fails to progress when it reaches the pxe boot menu. I make my selection and nothing happens. I am serving the media via http from the same... (3 Replies)
Discussion started by: duckeggs01
3 Replies

5. Red Hat

Interactive PXE Boot Menu

I have been asked to modify our PXE server such that there will be only one entry in the pxelinux.cfg/default file, where the same kernel and initrd.img will be used regardless of what operating system is to be installed, and the user will type in the path to the kickstart file that will be used. ... (7 Replies)
Discussion started by: ceb
7 Replies

6. Solaris

PXE boot problems in Solaris 10

Hi folks, I was trying to setup Network based NFS installation with PXE. I'm using virtual box for this purpose. I have one redhat (DHCP) server and Solaris 10 (Install server - Source) and on the other one am trying to install solaris using PXE. As in, dhcp address and boot file can be fetched... (2 Replies)
Discussion started by: vijaytrendz
2 Replies

7. Boot Loaders

PXE boot not taking the init= option

Hi Experts, I am doing PXE boot for my GNU/Linux device and pxelinux.0 loads the kernel as well as initrd images I have mentioned in the config file but it looks like it is not considering the init= option. Instead it starts the default INIT program. I wanted my customized init program to be... (3 Replies)
Discussion started by: learn more
3 Replies

8. UNIX for Advanced & Expert Users

Setting up a PXE Boot Server

I've set up a PXE boot server and I'm having a slight snag in the booting process. On the client machine, DHCP renders fine and TFTP seems to begin but then the system hangs. On the server, the error message "Client does not accept options" occurs -- which from reading online is a common message... (2 Replies)
Discussion started by: Colton
2 Replies

9. UNIX for Dummies Questions & Answers

what is PXE boot bare-metal

hi members i am reading RHEL and i am unable to under stand about PXE boot and bare metal (1 Reply)
Discussion started by: wagmare
1 Replies

10. HP-UX

PXE boot port issue

Hi,all: I want to boot an IA unix box from network, I am sure I set the DHCP and boot server, but it still failed ! It says : Client MAC Address: 00 18 FE 28 91 82 .....- PXE-E16: Valid PXE offer not received. Load of Core LAN Gb A failed: Not Found I use the nettl command to trace the UDP... (0 Replies)
Discussion started by: bluepluto
0 Replies
Login or Register to Ask a Question