From: Louis-David Mitterrand <vindex@apartia.org>
To: Linux-raid <linux-raid@vger.kernel.org>
Subject: strange lilo error
Date: Tue, 15 Jun 2004 09:39:53 +0200 [thread overview]
Message-ID: <20040615073953.GA25753@apartia.fr> (raw)
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
next reply other threads:[~2004-06-15 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 7:39 Louis-David Mitterrand [this message]
2004-06-15 8:25 ` strange lilo error Mario 'BitKoenig' Holbe
2004-06-16 7:53 ` Louis-David Mitterrand
2004-06-16 8:36 ` Mario 'BitKoenig' Holbe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040615073953.GA25753@apartia.fr \
--to=vindex@apartia.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).