Your message dated Thu, 14 Dec 2006 11:23:57 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fwd: Bug#398957: lilo uses wrong root= parameter
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 ---
Package: lilo
Version: 22.6.1-7.1
Severity: important
I found that the «root=» parameter used by lilo was wrong: in may case
it had to be fd01 while it was fd00. I traced the problem until I found
that my root file system is mapped in two different ways to major/minor
codes:
sh-3.1$ sudo ls -l /dev/.static/dev/mapper/mirrorvg-newrootlv
/dev/mapper/mirrorvg-newrootlv
brw-rw---- 1 root disk 253, 1 2006-11-16 19:29 /dev/mapper/mirrorvg-newrootlv
brw-rw---- 1 root disk 253, 0 2006-10-11 18:01
/dev/.static/dev/mapper/mirrorvg-newrootlv
sh-3.1$
I am not sure about what package creates all nodes
in /dev/.static/dev/mapper/, but I think it is lilo.
Bye,
Giuseppe
--- End Message ---
--- Begin Message ---
On Wed, Dec 13, 2006 at 11:29:48AM +0100, Giuseppe Sacco wrote:
> I think that the problem is that vgscan creates devices with different
> minor than the one used in the previous boot (with a different kernel).
This is no bug. The devmapper devices are assigned dynamicaly.
> 1. deleted all device files in /dev/.static/dev/mapper/
/dev/mapper is to be created by libdevmapper, don't mess with it.
> In order to boot this machine, I had to specify root=fd01 at the lilo
> prompt. This is shown by /proc/cmdline
No, you have to use the correct device name, not a number.
Bastian
--
You're dead, Jim.
-- McCoy, "The Tholian Web", stardate unknown
--- End Message ---