Results 1 to 2 of 2
Hello, I have compilled my new kernel 2.6.20.5. My prevous kernel was 2.6.18.4-486.
I'm using Debian 4.0 r0.
My old kernel running ok, but when I want run Linux on ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 06-28-2007 #1Just Joined!
- Join Date
- Jun 2007
- Posts
- 1
Kernel panic - not syncing: Attempted to kill init!
Hello, I have compilled my new kernel 2.6.20.5. My prevous kernel was 2.6.18.4-486.
I'm using Debian 4.0 r0.
My old kernel running ok, but when I want run Linux on my new kernel I get this message:
I was compilling kernel my firt time on Debian. I used this tutorial.Code:....... md: md1 stopped. mdadm: cannot open devide /dev/sda3: No such device or adress mdadm: /dev/sda3 has wrong uuid. mdadm: cannot open devide /dev/sdb3: No such device or adress mdadm: /dev/sdb3 has wrong uuid. mdadm: no devices found dor /dev/md1 umount: devfs: not mounted mount: unknown filesyste type 'devfs' EXT3-fs: unable to read superblock EXT2-fs: unable to read superblock cramfs: wrong magic umount: devfs: not mounted pivot_root: No such file or directory /sbin/init: 432: cannot open /dev/console: No such file Kernel panic - not syncing: Attempted to kill init!
Debian-Kernel-Compile-Howto - FalkoTimme.com
Can somebody help me? Thank you
- 07-03-2007 #2
code turns out that its problem of file system, which is not mounted at the time of compilation of new kernel, also you need to check for the 'pivot_root' file in your system, pivot_root file is responsible for the mount the old root file system,which is necessary for your new kernel file system support.
Look at the line 7 and 12 in your code 'umount: devfs: not mounted', I think your system not able to mount the old_root file system, and its only reason for your problem.
first of all you need to check out for the pivot_root file existence in particular folder. then try to mount your old_root file system, with command
'mount /dev/hda1 /new-root'
'cd /new-root'
then put your old-root in this folder
'pivot_root . old-root'
then
'exec chroot . sh <dev/console >dev/console 2>&1'
exec chrroot change the running executable, which is necessary if the old root directory should be unmounted afterwards.
'umount old-root'
try this than compile your new kernel.
Let me know if you have any problem,
cheers
-s


Reply With Quote
