My md boots into the pxelinux kernel, then as it loads it runs dhclient and gets the Ip address but seems to hang there. Then about two minutes later it will output the dhcp reply over and over again. I can go no further and have to restart. Has anybody experienced this before? Is there any logs saved when pxebooting?
Thanks,
Mark
Do you have 2 NICs in that MD by any chance?
well yes I do but the 2nd nic is not plugged in. I think I have tried it with just one though. I will try again.
I have got a little bit further now, I have only one card but it seems to get the IP ok but then says unable to connect to router. Restarting in 5 seconds.
Are there any logs anywhere to find out whats going on?
This is driving me mad, can nobody help? it seems during the pxe boot and loading of the pxekernel it does a DHCP request, gets an IP address then quickly bombs out with no meaningful output. I just don't know what to do next :(.
where is the image for pxe booting stored? what script is run after obtaining an IP address? Is there any logging or any in depth documentation on the pxe process?
Quote from: zug on April 03, 2008, 09:21:31 PM
This is driving me mad, can nobody help? it seems during the pxe boot and loading of the pxekernel it does a DHCP request, gets an IP address then quickly bombs out with no meaningful output. I just don't know what to do next :(.
where is the image for pxe booting stored? what script is run after obtaining an IP address? Is there any logging or any in depth documentation on the pxe process?
This is a good place to start
http://wiki.linuxmce.org/index.php/PXEAndrew
Hi,
Do you have this file on your core? /tftpboot/pxelinux.cfg/01-[mac address]. mac adress being your diskless MD's mac. I once had a simular problem and found the file had something like "#ernel vmlinuz". I deleted the # and replaced it with a k, after which my diskless MD booted up. Either way I'd start looking for the problem there or simply just try another nic.
l8r
I have looked there but no such look. There is just a default file.
Thanks for the link above but it does not really go into enough depth to help me diagnose the problem.
Can anybody else shed some light onto this? It is so annoying that the screen goes blank before saying "could not connect to router" so I cannot see any error messages. Is there a script that produces this error somewhere?
I have noticed my exports file seems to be missing the disklessmdroots section. Can anybody tell me what should be in this file?
## BEGIN : InternalStorageDevices
/mnt/device/38 192.168.80.0/255.255.255.0(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
/mnt/device/39 192.168.80.0/255.255.255.0(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
/mnt/device/40 192.168.80.0/255.255.255.0(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
/mnt/device/42 192.168.80.0/255.255.255.0(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
## END : InternalStorageDevices
## BEGIN : CommonDiskless
/home 192.168.80.0/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/orbiter 192.168.80.0/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/keys 192.168.80.0/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/deb-cache 192.168.80.0/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/var 192.168.80.0/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
## END : CommonDiskless
## BEGIN : DisklessMDRoots
## END : DisklessMDRoots