On 4/8/06, Mike Garey <[EMAIL PROTECTED]> wrote:
> I have one last question though.. When I update /boot/grub/menu.lst
> while booted from /dev/md0 with both disks available, does this file
> get written to the MBR on both disks, or do I have to do this
> manually?
>
Grub's configuration lives on
> On 4/5/06, Jim Klimov <[EMAIL PROTECTED]> wrote:
> > I'm afraid I haven't seen your first messages in detail. Sorry, if I
> > repeat the lines you already know by heart ;)
> >
> > Nevertheless, do you by chance have the ability to rebuild your
> > kernel, or are you keen on making MD work from in
> but wouldn't I need to have /dev/md0 available before doing mdadm
> --assemble? When booting from an initrd image, /dev/md0 is never
> created for some reason..
>
Sorry, I didn't realize initrd adds to the mix.
> > Note, you should never do any read/write access to the component disks
> > afte
On 4/5/06, Paul Clements <[EMAIL PROTECTED]> wrote:
> Mike Garey wrote:
>
> > I seem to be getting closer.. If I try booting from a kernel without
> > raid1 and md support, but using an initrd with raid1/md modules, then
> > I get the "ALERT! /dev/md0 does not exist. Dropping to a shell!"
> > mess
Mike Garey wrote:
I seem to be getting closer.. If I try booting from a kernel without
raid1 and md support, but using an initrd with raid1/md modules, then
I get the "ALERT! /dev/md0 does not exist. Dropping to a shell!"
message. I can't understand why there would be any difference between
us
On 4/5/06, Tuomas Leikola <[EMAIL PROTECTED]> wrote:
> On 4/5/06, Mike Garey <[EMAIL PROTECTED]> wrote:
> > I tried booting from /dev/hdc1 (as /dev/md0 in grub) using a 2.6.15
> > kernel with md and raid1 support built in and this is what I now get:
> >
> > md: autodetecting raid arrays
> > md: aut
On 4/5/06, Mike Garey <[EMAIL PROTECTED]> wrote:
> I tried booting from /dev/hdc1 (as /dev/md0 in grub) using a 2.6.15
> kernel with md and raid1 support built in and this is what I now get:
>
> md: autodetecting raid arrays
> md: autorun ...
> md: considering hdc1 ...
> md: adding hdc1 ...
> md: c
On 4/5/06, Troels Bang Jensen <[EMAIL PROTECTED]> wrote:
> This isn't quite what you asked about, but the rootraiddoc97 document is
> kinda obsolete by now
>
> -Debian Sarge has a new partitioner which can set up pretty advanced
> RAID configurations when installing. Just create RAID auto partition
This isn't quite what you asked about, but the rootraiddoc97 document is
kinda obsolete by now
-Debian Sarge has a new partitioner which can set up pretty advanced
RAID configurations when installing. Just create RAID auto partitions on
the disks and then create the arrays afterwards in the pa
Just wanted to add a few more details/questions to my previous post..
In case I provided too much information in my previous email, here's a
condensed version:
1) got to "step 6.2 Add the first-disk to our existing RAID device" of
the rootraiddoc walkthrough
2) issued command "mdadm --add /dev/md
I'm in the process of setting up a software RAID level 1 on debian
testing with two 160 gig drives on an Asus P4P800 motherboard with
Intel Pentium 4 CPU 3.00GHz and 512 megs of RAM. I've been following
the instructions in /usr/share/doc/mdadm/rootraiddoc97.html, but after
rebooting to /dev/hdc1 (
11 matches
Mail list logo
