From: Michael Tokarev <mjt@tls.msk.ru>
Cc: linux-raid@vger.kernel.org, debian-testing@lists.debian.org
Subject: Re: lilo fails on root raid 1 on 2.6.4
Date: Thu, 08 Apr 2004 19:10:25 +0400 [thread overview]
Message-ID: <40756B61.1060505@tls.msk.ru> (raw)
In-Reply-To: <0C8098CA7F09CE419F0C2B68EB8358761EB885@exchange.fasttrack.net.au>
Lewis Shobbrook wrote:
> Thanks for the reply Neil,
>
>
>>>Hi All,
>>>
>>>I've struck an issue attempting to run lilo when booting to a raid 1
>>>system using a stock Debain 2.6.4-1-686 unstable release kernel image.
>>>After sucecssfully booting into the raid filesystem, attempts to run
>>>lilo give me the error...
>>>
>>>Fatal: Trying to map files from unnamed device 0x0000
>>(NFS/RAID mirror down ?)
>>
>>You probably need a "raid-extra-boot=" option in lilo.conf
>>Just list the partition(s) that are currently active and it
>>might work.
>
> I've been able to apply the "raid-extra-boot=" option on an alternate
> system and did a bit of toying around with the syntax to see what was
> required and possible. All was well on the test machine, running the
> same 2.6.4-1 kernel, however the problems persist....
[snip]
Quite some time ago I discovered the "ultimate solution" for this
lilo/raid stuff (even back when LILO wasn't aware of raid), and I
mentioned it on this (linux-raid) list several times.
Instead of using LILO to install to raid devices, use standard MBR
(comes in `mbr' debian package, install-mbr /dev/sda etc, and LILO
itself may ), mark your
boot raid partitions active and use "boot=/dev/md.." in lilo.conf.
For this to work, you should have your boot partitions at exactly
the same place on all disks, but this isn't a problem in most cases
(after all, boot partition shouldn't be large and it's easy to place
it somewhere at the beginning of the disk, on the same partition).
> With raid-extra-boot=/dev/hdc,hda (hda being marked as failed)...
>
> Fatal: Unable to open dev/hda
>
> With raid-extra-boot=/dev/hdc ...
> Fatal: Trying to map files from unnamed device 0x0000 (NFS/RAID mirror
> down ?)
Hmm... this is a bug somewhere in lilo it seems...
/mjt
next prev parent reply other threads:[~2004-04-08 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 7:32 lilo fails on root raid 1 on 2.6.4 Lewis Shobbrook
2004-04-08 15:10 ` Michael Tokarev [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-13 0:56 Lewis Shobbrook
2004-04-08 3:09 Lewis Shobbrook
2004-04-08 4:48 ` Neil Brown
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=40756B61.1060505@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=debian-testing@lists.debian.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).