From: "Max Booker" <max.booker@ntlworld.com>
To: Raid <linux-raid@vger.kernel.org>
Subject: Raid1 and mdadm
Date: Sat, 29 Mar 2003 20:28:34 -0000 [thread overview]
Message-ID: <005e01c2f631$c5de3620$6b7ba8c0@max> (raw)
Hello
I am a Linux newbie, using Redhat Linux 7.3 Kernel 2.4.18-17.7.x on an Asus
7V333 with Promise Raid Controller (disabled).
I would like to understand more about Raid in a Linux environment, except
that all the documentation I have read seems not to apply to my case.
I understand that mdadm is better than raidtools, but I still cannot get my
head around the concept of how Linux Raid works.
Neil Brown gave a reply to splee in April, which seems to be relatively
straightforward - however, when I try this method, I get a kernel panic.
My setup is as follows:
GRUB boot loader
hda1 /boot
hda2 /
hda3 swap
hdd1 (intended) mirror partition of /
I can create the (degraded) array on hdd1, mkfs on /dev/md0, mount /dev/md0
as /mnt, copy / to /mnt, and edit /mnt/etc/fstab.
Everything works well up to the point where I reboot, with kernel parameters
(md=0,/dev/hdd1 root=/dev/md0). This is where the kernel panics.
I think that I have not edited fstab properly, or GRUB is getting in the
way, or maybe it is not possible to add hda2 to the array because it already
has a filesystem on it.... How do I get hda2 to be part of the Raid array?
Nothing attempted so far has made any impression on the fact that mdadm
insists that /dev/hda2 is not an md component.
I hope that this is enough info.
Best regards
Max Booker
next reply other threads:[~2003-03-29 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 20:28 Max Booker [this message]
2003-03-29 21:54 ` Raid1 and mdadm Mads Peter Bach
2003-03-31 11:34 ` Friedrich Lobenstock
-- strict thread matches above, loose matches on Subject: below --
2003-03-31 13:33 Sarcar, Shourya C (MED)
2003-03-31 17:22 Cress, Andrew R
2003-04-01 16:07 ` Paul Clements
2003-04-01 23:08 ` Neil Brown
2003-04-02 20:22 ` Paul Clements
2003-04-02 20:34 ` Paul Clements
2003-04-01 16:43 Cress, Andrew R
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='005e01c2f631$c5de3620$6b7ba8c0@max' \
--to=max.booker@ntlworld.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 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).