strange lilo error

strange lilo error

[Louis-David Mitterrand]

Hello,

I am trying to convert a raid1 partition from reiserfs to ext3 by
setting one drive faulty, removing it, creating a new degraded raid1
set, copying data from the reiserfs partition to the ext3 one.

Here is the /proc/mdstat output before starting the conversion:

Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6]
md1 : active raid1 hdb2[0] hda2[1]
      313152 blocks [2/2] [UU]

md0 : active raid1 hdb1[2] hda1[1]
      77834816 blocks [2/2] [UU]

Once /dev/hdb1 and /dev/hdb2 have been marked faulty and removed lilo
will fail with the following message:

Fatal: Trying to map files from unnamed device 0x0000 (NFS/RAID mirror down ?)

The lilo.conf has:

# boot=/dev/md0
boot=/dev/hda
root=/dev/md0
# raid-extra-boot=mbr
compact
install=/boot/boot-menu.b
map=/boot/map
delay=20
vga=normal
default=Linux
image=/vmlinuz
    label=Linux
    read-only
image= /boot/vmlinuz-2.4.22-madrid
    label=Linux-2.4.22
    read-only

I commented out "raid-extra-boot" and replaced "boot=/dev/md0" with
"boot=/dev/hda" but the error persists.

After running a few tests it appears lilo will only stop complaining
once the original raid1 set is restored _and_ synchronized.

This the first time we have this kind of error, having done the same
conversion on other machines. This is with debian unstable and a 2.6.6
kernel.

Any idea? Thanks in advance,


-- 
In linux-dominated parallel world, all children's names begin with g, k or x

Re: strange lilo error

[Mario 'BitKoenig' Holbe]

Louis-David Mitterrand <vindex@apartia.org> wrote:
> Once /dev/hdb1 and /dev/hdb2 have been marked faulty and removed lilo
> will fail with the following message:
> Fatal: Trying to map files from unnamed device 0x0000 (NFS/RAID mirror down ?)

Well, this is coherent, isn't it?

> After running a few tests it appears lilo will only stop complaining
> once the original raid1 set is restored _and_ synchronized.
[...]
> Any idea? Thanks in advance,

Well, a question at first :)
Why do you need to run lilo after you failed one of the mirrors?

Anyways - I'm running lilo on degraded arrays and it works
very well.
Thus, I presume, it works for you too, once you remove the
failed mirror from the array.


regards,
   Mario
-- 
Whenever you design a better fool-proof software,
the genetic pool will always design a better fool.

Re: strange lilo error

[Louis-David Mitterrand]

On Tue, Jun 15, 2004 at 10:25:42AM +0200, Mario 'BitKoenig' Holbe wrote:
> Louis-David Mitterrand <vindex@apartia.org> wrote:
> > Once /dev/hdb1 and /dev/hdb2 have been marked faulty and removed lilo
> > will fail with the following message:
> > Fatal: Trying to map files from unnamed device 0x0000 (NFS/RAID mirror down ?)
> 
> Well, this is coherent, isn't it?

No, this doesn't happen with a 2.4.26 kernel, only with a 2.6.6 (and
maybe others in the 2.6.x series).

> > After running a few tests it appears lilo will only stop complaining
> > once the original raid1 set is restored _and_ synchronized.
> [...]
> > Any idea? Thanks in advance,
> 
> Well, a question at first :)
> Why do you need to run lilo after you failed one of the mirrors?

I need to reboot to a degraded array to complete the filesystem
conversion.

> Anyways - I'm running lilo on degraded arrays and it works
> very well.

On which kernel?

-- 
 "When I give food to the poor I am called a saint, when I ask why
  they go hungry I am called a communist"
   --Bishop Helder Camara

Re: strange lilo error

[Mario 'BitKoenig' Holbe]

On Wed, Jun 16, 2004 at 09:53:53AM +0200, Louis-David Mitterrand wrote:
> No, this doesn't happen with a 2.4.26 kernel, only with a 2.6.6 (and

Ah, this is most likely important to know :)

> > Anyways - I'm running lilo on degraded arrays and it works
> On which kernel?

2.4 series - 2.4.20 to 2.4.25.


regards,
   Mario
-- 
The social dynamics of the net are a direct consequence of the fact that
nobody has yet developed a Remote Strangulation Protocol.  -- Larry Wall