Red Hat Bugzilla – Bug 161394
Diskless client panics on boot
Last modified: 2007-11-30 17:07:18 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2 Description of problem: The initrd.img created by system-config-netboot is missing libraries needed to boot the client system. Version-Release number of selected component (if applicable): system-config-netboot-0.1.8-1 How reproducible: Always Steps to Reproduce: 1. rsync the root directory ("/") of an RHEL 4 system to an RHEL 4 server and configured a diskless service using system-config-netboot as described at the manual URL below: http://www.redhat.com/docs/manuals/enterprise/RHEL- 4-Manual/sysadmin-guide/ch-diskless.html 2. Boot client system. 3. Actual Results: Diskless systems do not start due to kernel panic. "Kernel Panic - not syncing : No init found. Try passing init = option to kernel. " Expected Results: Client should boot successfully. Additional info: RH support has verified that system-config-netboot-0.1.20-1 fixes problem.
I am having the same problem on Fedora Core 4. Fedora Core 4 ships with system-config-netboot-0.1.14-1 Parameters *are* being passed to the kernel. I verified this by modifying the 'append' arguments in pxelinux.cfg/<client_ip_address> I then found this bug report and upgraded to system-config-netboot-0.1.20-1 Unfortunately, that did not resolve my problem ... I still see the same behavior on FC4. Q: What can I do to help get this issue resolved? Q: Any workarounds? Michael
On FC4 ... I read other/previous bugs related to system-config-netboot. I deleted from the previous system-config-netboot installation and started from scratch. Now initrd seems to be OK. Kernel starts the boot process. Dies in NFS, but that is probably my problem. Will advise.
Yes, the initrd.img bad libraries issue is definitely fixed with system-config-netboot-0.1.16+ . The latest s-c-nb version can be downloaded from: http://people.redhat.com/~jvdias/system-config-netboot/ . The system-config-netboot-0.1.20-1.noarch.rpm package should work fine on FC-3, FC-4, and RHEL-4 - I'll be issuing FC-3 and FC-4 updates for it shortly. How does the boot process "die in NFS"? I use these /etc/exports statements with no problems: " /client_root_dir/root *(ro,sync,no_root_squash,no_subtree_check) /client_root_dir/snapshot *(rw,sync,no_root_squash,no_subtree_check) " Is the problem reproducable with these options on your NFS server ? What does the /tftpboot/linux-install/pxelinux.cfg/* configuration file for your subnet say ? If you cannot determine the cause of your nfs boot problem, please attach the output of a serial console boot to this bug report - 1. edit the /tftpboot/.../pxelinux.cfg/${subnet} configuration file to say: "label ... kernel ... append ... console=/dev/ttyS0,9600 console=/dev/console " 2. Attach a null modem cable to the client and another machine; on the other machine, do: # tee /tmp/netboot.log < /dev/ttyS0 and then boot the client. When the problem has been reproduced, press CTRL-C and attach the /tmp/netboot.log file to this bug report. Thank you!
Sorry I did not follow up. I am up and running fine now. As I recall, some of my NFS problems were related to confusion caused by bugs in the system-config-netboot UI. I filed a separate bug report which is also assigned to Jason Vas Dias ... # 161904
From User-Agent: XML-RPC HOTFIX Request has been released http://seg.rdu.redhat.com/scripts/hotfix/edit.pl?id=387
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-484.html