LinuxQuestions.org - Kernel Panic when network booting for diskless linux

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - Kernel Panic when network booting for diskless linux (https://www.linuxquestions.org/questions/linux-general-1/kernel-panic-when-network-booting-for-diskless-linux-922939/)

Kernel Panic when network booting for diskless linux

I have been trying to setup a diskless Linux cluster using Fedora 16. The boot server is working but I have run into a kernel error with my bzImage version 3.1.7. See the text below I get for kernel panic.

Code:

 md:  ...  autorun DONE.



RAMDISK: gzip image found at block 0



EXT4-fs  (ram0):  couldn't mount as ext3 due to feature incompatabilities



EXT4-fs  (ram0):  mounting ext2 file system using the ext4 subsystem



EXT4-fs  (ram0):  mounted filesystem without journal. Opts: (null)



VFS: mounted root (ext2 filesystem) on device 1:0.



devtmpfs:  mounted



Freeing unused kernel memory: 1376k freed



Write protecting the kernel text: 21908k



Write protecting the kerenel read-only data: 8816k



Kernel panic  - not syncing: No inti found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.



Pid: 1, comm: swapper Not tainted 3.1.4 #1



Call Trace:



[<c1939acc>]  ?  printk+0x2d/0x2f



[<c193997c>]  panic +0x5c/0x15f



[<c19375d5>]  init_post+0xae/0xae



[<c2404a06>]  kernel_inti+0x13b/0x13b



[<c24048cb>]  ?  do_one_initcall+0x13b/0x13b



[<c19630fe>]  kernel_thread_helper+0x6/0x10



panic occured, switched back to text console

Here are the parameters passed to the kernel during boot.

Code:

DEFAULT bzImage



APPEND initrd=rootfs2.gz root=/dev/ram rw ip=192.168.0.254:192.168.0.2:192.168.0.1:255.255.255.0:llama0:eth0:off

I'm not really sure how to solve this problem it is a bit beyond me. I have attached my kernel configuration file if that is the problem.

I think the error messages point to the solution

Code:

Kernel panic - not syncing: No inti found. Try passing init= option to kernel.

You have to tell the kernel what init process to use. Usually, this will be something like /sbin/init. You can add the setting 'init=/sbin/init' (use the appropriate filespec for your setup) to the kernel argument list in the bootloader 'APPEND' record.

--- rod.

Hey,

I have done a fair bit of diskless cluster building in my time. Not for a while thankfully. :) You should check DRBL out (http://drbl.sourceforge.net/). It makes the config much easier and then you can even set it up to use things like SGE etc. It might not be suitable for your application but worth looking at.

Cheers,
Phil