All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zeno R.R. Davatz" <zdavatz@ywesee.com>
To: RAID Linux <linux-raid@vger.kernel.org>
Cc: Bernd Fischer <bernd@begu.net>
Subject: Re: mbr-install for Raid 1, mdadm -a /dev/md0 /dev/sda1
Date: Wed, 6 Oct 2004 18:34:11 +0200	[thread overview]
Message-ID: <20041006183411.10578ab7@zrr.local> (raw)
In-Reply-To: <41641A79.6030709@begu.net>

Hi Bernd

Thanks for your prompt reply.

On Wed, 06 Oct 2004 18:16:57 +0200
Bernd Fischer wrote:

> Zeno R.R. Davatz wrote:
> 
> >> No, you would have to use boot=/dev/md0 in your lilo.conf,
> 
> > Do I have to run 'lilo -v' so lilo gets this?
> 
> As usual, you have to run lilo everytime you install a new kernel or 
> edit lilo.conf
> 
> > Because whenever I run lilo -v (22.5.8) with 'boot=/dev/md0 I get the wonderful Error of:
> > Fatal: Trying to map files from unnamed device 0x0000 (NFS ?)
> 
> > Any hints?
> 
> I had the same problem some time ago. AFAIR it went away when I updated 
> to lilo 22.6
> As a workaround, create a symlink to /dev/md0 ( e.g. /dev/MD0 ) and use 
> this as your boot device in lilo.conf.
I managed to boot my /dev/md2 (using find . -xdev | cpio -pm /mnt/newroot instead of cp -ax / /mnt/newroot to copy my system to Raid). Now I am doing 'mdadam -a /dev/md2 /dev/sda3'

as next I would do 'mdadm -a /dev/md0 /dev/sda1'

Will the lilo problem then vanish?

Thanks for your Feedback.
Zeno

      reply	other threads:[~2004-10-06 16:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041005093440.2b639e71@zrr.local>
2004-10-05  9:08 ` mbr-install for Raid 1 Michael Tokarev
2004-10-05  9:39   ` Zeno R.R. Davatz
2004-10-05 13:47   ` Zeno R.R. Davatz
2004-10-05 18:25     ` Bernd Fischer
2004-10-06  5:59       ` mbr-install for Raid 1 with Root on Raid5 Zeno R.R. Davatz
2004-10-06  8:56   ` mbr-install for Raid 1, rerun Lilo necessary? Zeno R.R. Davatz
2004-10-06 16:16     ` Bernd Fischer
2004-10-06 16:34       ` Zeno R.R. Davatz [this message]

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=20041006183411.10578ab7@zrr.local \
    --to=zdavatz@ywesee.com \
    --cc=bernd@begu.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.