Sid unbootable after kernel upgrade

st1cky_rice · 12-12-2005, 09:53 AM

Hi everyone,

after "apt-get upgrade"ing my kernel (2.6.14) I got a message telling me I should immediately reboot (and that it's very important to do so) after the upgrade process is done. Which I did, and I can't boot my Debian anymore...this is what I got on my screen:

Quote:

/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 1 seconds for /sys/block/hda/dev to show up
...

it then waited another 2, 4, 8, 16 seconds before it said:

Quote:

Device /sys/block/hda/dev seems to be down.
Debugging opportunity, type ^D to continue

So I typed Control-D and I got

Quote:

/bin/dash: can't access tty; job control turned off

How should I proceed next? Thanks!

nx5000 · 12-12-2005, 10:17 AM

See this

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343042

I've not tested it yet.

st1cky_rice · 12-12-2005, 10:31 AM

Thanks nx5000! From the bug report I learned that one can still boot the 2.6.12 kernel...so at least I could log into my Debian and access my files...I'm sure the Debian Team will fix the bug soon!

Crushing Belial · 12-12-2005, 10:42 AM

Quote:

Originally Posted by st1cky_rice

Thanks nx5000! From the bug report I learned that one can still boot the 2.6.12 kernel...so at least I could log into my Debian and access my files...I'm sure the Debian Team will fix the bug soon!

That's why it's good to always leave the previous kernel installed, until you're sure there's no issues with booting the new kernel.

h2gofast · 12-12-2005, 10:54 AM

same thing happened here, and dittos on leaving the previous kernel installed.

btw, in the bug report there is a workaround.

Quote:

1. Added to /etc/yaird/Default.cfg:

MODULE ide-generic
MODULE ide-disk

2. Created new initrd image:

rm /boot/initrd.img-2.6.14-2-686
yaird -v -o /boot/initrd.img-2.6.14-2-686 2.6.14-2-686

3. Reboot.

hda now properly recognized and boot completes.

haven't tried it yet so go at your own risk

nx5000 · 12-12-2005, 11:28 AM

It works perfectly.

h2gofast · 12-12-2005, 11:34 AM

yeah me too, just remember to get the kernel number correct, e.g. If you're running amd then 686 would be k7

pinknick · 12-18-2005, 07:08 AM

I spent two days trying to make my debian works. Now I found your post and it worked perfectly.

Thanks!