From: Ninti Systems <office@ninti.com.au>
To: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: Please review: Slackware RAID How-To
Date: 12 May 2004 09:21:05 +0930 [thread overview]
Message-ID: <1084319464.1071.17.camel@localhost> (raw)
In-Reply-To: <1084290138.25942.30.camel@ws101.darkcore.net>
Thanks John, I've been wrestling with this for a while. I ended up
having to use a RedHat9 install to get RAID 1 working on one particular
box ... RAID is my last reason to use RedHat after discovering the joy
of simplicity, Slackware style. I was using mdadm in my Slackware RAID
experiments, and a different approach, but it only ever half worked
(almost certainly the problem was with me, not mdadm!).
Unfortunately, I don't have a spare box lying around that I can test
this on right now, but I will follow this HOWTO's development with great
interest and give it a go as soon as I can. I'm mainly interested in
super reliable 2 disc RAID 1 setups, but it looks like most things still
apply.
Any comments on SATA disks? I'm not sure where SATA fits in to all this
(is it an issue?).
A reliable method for building bootable RAID on Slackware for non-gurus
will propel Slackware into the realm of the "truly awesome" for me, I've
been a RedHat jock for too long!
Mick
On Wed, 2004-05-12 at 01:12, John Lange wrote:
> As mentioned, I have created a Slackware RAID How-To and an initial
> draft is located here:
>
> http://www.langefamily.ca/howto/SlackwareRaidHowTo.html
>
> This document covers getting Slackware installed on a system with RAID.
> This technique does not require a temporary hard drive or anything other
> than a Slackware boot CD.
>
> I am fairly new to linux software RAID so I really hope some more
> experienced people will take some time to read it and give me some
> feedback. I would hate to have some glaring errors inflicted on others!
>
> Thanks.
--
--------------------------------------
Ninti Systems: Smart IT Solutions
Michael Hall
Mobile: 0429 095 392
Ph/Fax: 08 8953 1442
Email: office at ninti dot com dot au
Web: http://ninti.com.au
--------------------------------------
next prev parent reply other threads:[~2004-05-11 23:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 15:42 Please review: Slackware RAID How-To John Lange
2004-05-11 23:51 ` Ninti Systems [this message]
2004-05-16 5:43 ` Ninti Systems
2004-05-16 6:40 ` Ninti Systems
2004-05-17 2:36 ` Ninti Systems
2004-05-17 4:51 ` Guy
2004-05-17 9:02 ` Ninti Systems
2004-05-20 1:42 ` John Lange
2004-05-20 2:06 ` Ninti Systems
2004-05-20 3:27 ` Guy
2004-05-20 3:33 ` John Lange
2004-05-20 5:02 ` Guy
2004-05-20 7:58 ` John Lange
2004-05-20 13:37 ` Guy
2004-05-21 2:25 ` Ninti Systems
2004-05-21 2:55 ` Guy
2004-05-21 2:47 ` Ninti Systems
2004-05-20 3:11 ` Guy
2004-05-20 4:35 ` Guy
-- strict thread matches above, loose matches on Subject: below --
2004-05-13 9:46 George Iosif
2004-05-14 6:21 George Iosif
[not found] <s0a48f9e.018@nsa.ase.ro>
2004-05-14 6:47 ` John Lange
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=1084319464.1071.17.camel@localhost \
--to=office@ninti.com.au \
--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).