Kernel panic

**sentmen** · 08-07-2011

Hi all,

I want to build and boot an own kernel (v.2.6.39.4). But i got an kernel panic while booting the new kernel:

Code:

Failed to execute /bin/bash. Attempting defaults
Kernel panic - not syncing: No init found. Try passing init= option to kernel. See linux documentation/init.txt for guidance
Pid: 1, comm: swapper Not tainted 3.0.0 #1

Can anyone help me out?

**Rubberman** · 08-08-2011

1. What was the old kernel?
2. How did you build and install the new kernel?

**sentmen** · 08-09-2011

Originally Posted by Rubberman

1. What was the old kernel?
2. How did you build and install the new kernel?

1. I want to make a own distribution. I used the last version of debian 6 (netinstall)
2. From an tutorial. Edited not much in make menuconfig

**Rubberman** · 08-09-2011

Originally Posted by sentmen

1. I want to make a own distribution. I used the last version of debian 6 (netinstall)
2. From an tutorial. Edited not much in make menuconfig

Please show the exact steps from "make menuconfig" to "make install". Also, did you get any error messages when installing the kernel?

**sentmen** · 08-09-2011

Sometimes if i look at the screen i get with some files errors (or warnings) but it don't stop with compiling. I tried it on more devices. And also in an virtual machine. I tried ubuntu and debian. The exact steps including what i used in the menuconfig?

**Rubberman** · 08-09-2011

Originally Posted by sentmen

Sometimes if i look at the screen i get with some files errors (or warnings) but it don't stop with compiling. I tried it on more devices. And also in an virtual machine. I tried ubuntu and debian. The exact steps including what i used in the menuconfig?

Your problem is not likely due to changes made with menuconfig, but how you built and installed the kernel. IE:

make menuconfig
make
make headers_install
make modules_install
make install

and any errors (warnings are not at issue at this point) you got while doing the above.

**rulingminds** · 08-09-2011

In your case the kernel is booted up normally, I think it is not able to mount the root file system correctly, where the init executable file is stored. Do one thing, boot up the system with the working kernel and use mount command to find out which is the root file system. The one which is mounted on /. Say, for example, that is /dev/sda2. While booting the system with new kernel specify /dev/sda2 as root file system partion, using the root option at grup menu.

**sentmen** · 08-09-2011

Originally Posted by rulingminds

In your case the kernel is booted up normally, I think it is not able to mount the root file system correctly, where the init executable file is stored. Do one thing, boot up the system with the working kernel and use mount command to find out which is the root file system. The one which is mounted on /. Say, for example, that is /dev/sda2. While booting the system with new kernel specify /dev/sda2 as root file system partion, using the root option at grup menu.

Yes. It is exactly what the problem is. Let me show my grub item.

Code:

menuentry 'sentmen' {
set root='(hd1,1)'
linux /boot/vmlinuz root=/dev/sdb1 ro
}

**yancek** · 08-10-2011

Your original post shows "No init found". Your grub menuentry has no initrd line. That's the problem. Do you have an initrd file on sdb1.
I don't really know the solution, maybe re-read the tutorial you used?

**sentmen** · 08-10-2011

Originally Posted by yancek

Your original post shows "No init found". Your grub menuentry has no initrd line. That's the problem. Do you have an initrd file on sdb1.
I don't really know the solution, maybe re-read the tutorial you used?

I don't have an initrd created. But if i do that it will be used for debian. And i don't want that.

Thread Tools

Display

Kernel panic

Posting Permissions