LinuxQuestions.org - Boot problem with the kernel 2.6.32-5 after the upgrade from Lenny to Squeeze (32bit)

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Boot problem with the kernel 2.6.32-5 after the upgrade from Lenny to Squeeze (32bit) (https://www.linuxquestions.org/questions/debian-26/boot-problem-with-the-kernel-2-6-32-5-after-the-upgrade-from-lenny-to-squeeze-32bit-865342/)

Boot problem with the kernel 2.6.32-5 after the upgrade from Lenny to Squeeze (32bit)

I can't boot using the new default kernel present on debian squeeze:

Quote:

begin running /script/init-bottom must mounting /dev on /root/dev failed: No such file or directory
mount: mounting /sys on /root/sys failed:No such file or directory
mount: mounting /proc on /root/proc failed:No such file or directory
Target filesystem doesn,t have /sbin/init
No init found. Try passing init=bootarg
Busybox v1.17.1 (Debian ...) built-in shell (ash)
ENTER "help" for a list of built-in commands
/bin/sh: can't access TTY; job control turned off

While if i use the old kernel:
2.6.26-2-686
i haven't issue.
I have tried even this method:
sudo dpkg-reconfigure linux-image-2.6.32-5-686
the output was a file of 9.2 mb against the 8.2mb from before (and i think was strange), however the message are the same and i can't boot using this "new" kernel.

Note:
It's the default kernel of debian, it isn't a custom kernel.

try

Code:

sudo update-initramfs -u -k all

and see if that works

Unfortunately don't work. :/
The error remain the same.

Does your fstab have references to /dev/hdX as opposed to /dev/sdX ?

When i'm on the other pc i take a look.
For the moment i removed that release of the kernel and i was think to jump directly on 2.6.38 (that will be ready presumably during april) with a custom kernel.
I tried another installation of debian squeeze using the kernel 2.6.37.2 on a different pc and despite the /etc/fstab have only reference on /dev/hdX, work (a part a message during the start about /dev that i'm should write on the paper because i don't known if i can see it on some logs).