Your message dated Sat, 10 May 2008 00:23:45 +0200 with message-id <20080509222345.GT16453@stro.at> and subject line Re: system unbootable after update to linux-image-2.6.21-2 has caused the Debian Bug report #433127, regarding system unbootable after update to linux-image-2.6.21-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 433127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433127 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: system unbootable after update to linux-image-2.6.21-2
- From: Stefan Schöttke <schoeddie@gmx.net>
- Date: Sat, 14 Jul 2007 18:40:45 +0200
- Message-id: <4698FC8D.7040807@gmx.net>
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
--- End Message ---
--- Begin Message ---
- To: 433127-done@bugs.debian.org
- Subject: Re: system unbootable after update to linux-image-2.6.21-2
- From: maximilian attems <max@stro.at>
- Date: Sat, 10 May 2008 00:23:45 +0200
- Message-id: <20080509222345.GT16453@stro.at>
the kernel never guaranteed stable device names. use rootdelay if your box needs to settle a bit on start before lvm/md. use UUID if you want stable device names. closing -- maks
--- End Message ---