All of lore.kernel.org
 help / color / mirror / Atom feed
From: andy liebman <andyliebman@aol.com>
To: linux-raid@vger.kernel.org
Subject: Re: Making bootable SATA RAID1 array in Mandriva 2006
Date: Mon, 14 Aug 2006 06:50:30 -0400	[thread overview]
Message-ID: <44E05576.5050604@aol.com> (raw)

Thanks for the reply, Luca

> On Sun, Aug 13, 2006 at 07:51:42PM -0400, andy liebman wrote:
>>-- I copied the contents of /dev/sda1 (/ partition) and /dev/sda6 (/home 
>>partition) to /dev/sdb1 and /dev/sdb6 using rsync.
> this is not really important, but you should have used the raid devices
> as a target.

Sorry, I wrote this incorrectly. In my case, /dev/sdb1 = /dev/md1 and 
/dev/sdb6 = /dev/md2.  Remember, my md devices each have a drive missing 
at this point. I had the mdX devices started and mounted, and I rsynced 
from /dev/sda1 to /dev/md1, /dev/sda6 to /dev/md2.

> 
>>-- I edited fstab and lilo.conf on the the RAID1 "/" partition so that 
>>they would refer to /dev/md1
>>-- I ran chroot on the /dev/md1 partition
> did you mount /dev, /proc and /sys before chrooting?
> i.e
> mount --bind /dev /newroot/dev
> mount -t proc /proc /newroot/proc
> mount -t sysfs /sys /newroot/sys

Why do I have to do this? I haven't seen this in any "recipies". My 
Linux setup only has three partitions:   "/", swap, and "/home".

My experience with fixing bootloaders in the past is that I can boot up 
with a LIVE CD or rescue disk, chroot say into /dev/sda and run lilo 
right to fix the bootloader on /dev/sda. I do this when need to move my 
OS drive from an IDE to SATA or back again.

I'm not sure I understand what you're saying about mounting /dev, /proc 
and /sys.


Regards,
Andy Liebman
.


             reply	other threads:[~2006-08-14 10:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 10:50 andy liebman [this message]
2006-08-15 11:48 ` Making bootable SATA RAID1 array in Mandriva 2006 Luca Berra
  -- strict thread matches above, loose matches on Subject: below --
2006-08-16 13:12 andy liebman
2006-08-16 13:18 ` Mark Hahn
2006-08-16 14:35 ` Justin Piszcz
2006-08-16 23:49   ` Nix
2006-08-13 23:51 andy liebman
2006-08-14  8:17 ` Luca Berra
2006-08-14 10:34   ` Henrik Holst
2006-08-14 13:39 ` Laurent Lesage
2006-08-14 14:52   ` andy liebman
2006-08-14 15:13     ` Laurent Lesage
2006-08-15 11:57       ` Luca Berra

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=44E05576.5050604@aol.com \
    --to=andyliebman@aol.com \
    --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.