Bug#433127: system unbootable after update to linux-image-2.6.21-2
Hi, I am writing to say the same thing happens to me when I upgrade to 2.6.22-2-k7 and I didn't wnat to open a new bugreport. The workaround worked just fine for me. cheers, -- Gunther Furtado [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433127: system unbootable after update to linux-image-2.6.21-2
I have found an easy way to fix this problem on the following webpage : http://forums.debian.net/viewtopic.php?p=85884sid=253f85fa345866026fbf582e1c54e2b3 Basically you just need to change every 'sda' to 'hda' in your /etc/fstab file, and also in the entries for the new kernel in your /boot/grub/menu.lst (I just changed the root=hda1 into root=sda1 in mine and it works, I didn't change the 'root(hd0,0)' line). I have not changed the cdrom device as it is said on the forum, and I have no problem using it. Cheers! Matthieu
Bug#433127: system unbootable after update to linux-image-2.6.21-2
Hello, /dev/hda1 does not exist is a wide field but since I encountered the same symptoms and worked around them, I can hopefully narrow it down a bit. I encountered the problem on two machines out of eight after upgrading (2.6.18-4 worked fine on both). One is an old P2-300 box with soft RAID over two IDE drives, the other a newer Xeon server with soft RAID over two SCSI drives on a Fusion-MPT controller. Relevant packages (identical on both machines) are Package: linux-image-2.6.21-2-686 Version: 2.6.21-6 Package: initramfs-tools Version: 0.89 Ok, this is what can be seen on the console: The hardware drivers are loaded and report their findings (chipsets etc.). Then the md driver attempts to assemble its RAID, and fails because it cannot find disk devices. Then the root device (which should have been md0) is not found, and the rootfs mount fails. Then the disk drivers happily announce what disks and partitions they have found. Then the boot aborts and drops to a shell. Notice the order? What looks like a race condition is easily confirmed by using the rootdelay=nsecs parameter of initramfs-tools. Give the drivers a few seconds to finish their initialization, and the boot process continues just fine. Stefan, it might be helpful if you tried setting a rootdelay and reported if that works around the problem for you. Now why there is this race with .21 that was not there with .18, I leave for the kernel-knowledgable people to find out. I'm not even sure it's a bug after all but it is definitely a feature that needs to be addressed, or we will be seing a lot of non-booting machines (worst case, randomly non-booting). Greetings, Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433127: system unbootable after update to linux-image-2.6.21-2
Hello, I have the exact same bug on my system. I can't boot with the version .21 but I have no problem with the .18 However, before getting the error message written by Stefan Schöttke, I have that : BEGIN: Waiting for root file system... Done. The system stays for a few minutes on the BEGIN line before the Done. appears...and then after that, the message previously written by Stefan Schöttke appears. I have tried putting a 10 in the /usr/share/initramfs-tools/init file after the export ROOTDELAY= line (making it : export ROOTDELAY=10 without the ) and rebooting, but it didn't change anything on my system. Maybe I did something wrong though, I've never touched the initramfs/init configuration files before. I do not use RAID, have no SATA support, I just have an ATA HDD and an IDE CD-writer on the same ATA cable. Hope this helps (and gets corrected fast :D), Matthieu
Bug#433127: system unbootable after update to linux-image-2.6.21-2
package: linux-image-2.6-686 version: 2.6.21-2 severity: grave Hello, after upgrading to the current kernel package (2.6.21-2) the boot-process failed, reporting that the system was unable to find /dev/hda1. Then a shell (busybox) was started. The older 2.6.18-4 kernel works without any problems. The reported message was: ALERT! /dev/hda1 does not exist. Dropping to a shell! Check your root= boot argument (cat /proc/cmdline) Check for missing modules (cat /proc/modules), or device files (ls /dev) BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned off (initramfs) Greetings, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
