Your message dated Fri, 10 Sep 2010 17:49:11 +0000
with message-id <e1ou7ip-0004fj...@ravel.debian.org>
and subject line Closing oldbug report against debian-installer #492525
has caused the Debian Bug report #492525,
regarding debian-installer: wrong device number for root partition
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 ow...@bugs.debian.org
immediately.)
--
492525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Severity: important
I installed Debian testing using
debian-LennyBeta2-amd64-netinst.iso
using lvm2 over raid1.
On the first reboot after the install, the initrd failed to mount
the root partition and dumped me into a shell. I eventually figured
out that the kernel command line had root=fe00 (so it wanted the
root partition on device major=254,minor=0), but that my root was
actually on major=253,minor=0. (So I fixed it by booting with root=fd00;
then once I was inside Linux, I reran LILO, and that fixed the problem
permanently.)
I don't remember exactly what I did during the install process, but I
may have started to use an LVM partitioning before I decided to go for
LVM-over-RAID. So perhaps the LVM module got loaded first, and grabbed
major=254; but when I rebooted, RAID got major=254 and LVM got major=253.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (90, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
We are closing this bug report against debian-installer
for one of the following reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the bug report give the feeling that
the reported problem was lying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---