Your message dated Sat, 28 Jul 2007 13:27:09 +0200 with message-id <20070728112709.GA26851@stro.at> and subject line panic upon next boot because lilo was not run has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <maintonly@bugs.debian.org>
- Subject: panic upon next boot because lilo was not run
- From: Dan Jacobson <jidanni@jidanni.org>
- Date: Thu, 12 Jul 2007 19:45:11 +0800
- Message-id: <[🔎] 20070712114511.1913.56954.reportbug@jidanni2.jidanni.org>
Package: linux-image-2.6.21-2-686 Version: 2.6.21-6 Severity: wishlist Upon installation I was warned to reboot soon. So after installation was complete I rebooted, only to be met with "kernel panic, not syncing, VFS: unable to mount root fs in unknown block (3,1)" So I hit ALT Sysrq b, booted into a older kernel (21-1), ran lilo, and was then able to boot into 21-2. -- debconf information that had stars: * linux-image-2.6.21-2-686/preinst/already-running-this-2.6.21-2-686:
--- End Message ---
--- Begin Message ---
- To: 432846-done@bugs.debian.org
- Subject: Re:panic upon next boot because lilo was not run
- From: maximilian attems <max@stro.at>
- Date: Sat, 28 Jul 2007 13:27:09 +0200
- Message-id: <20070728112709.GA26851@stro.at>
most probably due to misconfiguration of /etc/kernel-img.conf you want a "do_bootloader = yes" there if you still insist using lilo closing -- maks
--- End Message ---