From: Mark Knecht <markknecht@gmail.com>
To: Leslie Rhorer <lrhorer@satx.rr.com>
Cc: Mdadm <linux-raid@vger.kernel.org>
Subject: Re: RAID Configuration For New Home Server
Date: Sun, 6 Jun 2010 07:56:04 -0700 [thread overview]
Message-ID: <AANLkTinh1WtkzAgS8cOC1idj-7tcS4OMv9s3qRGwdhrf@mail.gmail.com> (raw)
In-Reply-To: <BA.E9.03181.F158B0C4@cdptpa-omtalb.mail.rr.com>
On Sun, Jun 6, 2010 at 4:23 AM, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
<SNIP>
>
> Oh, I almost forgot. It may be of notable mention an array with a
> 1.0 superblock can be read as if it were an ordinary partition. This means
> one can build a 1.0 superblock array containing a file system (ext2 may be
> the best choice in this case), but boot from the partition just as if it
> were not an array. Once the system is booted, the array can be assembled
> and then /boot can be mounted. This is because:
>
> 1. The 1.0 superblock is at the *END* of the array.
>
> 2. The file system when created only uses up the front part of the
> partition, leaving the superblock intact.
>
> 3. GRUB does not require the file system to be mounted in order to read the
> kernel and the initrd. (Actually, it could be made to work even if it did
> mount the partition, but since it does not, it makes it much easier.)
>
> Indeed, this is the only way of which I know to boot to an array
> using GRUB legacy.
>
>
Actually that is of interest. If there's a way to use a single RAID
boot partition by itself once in awhile then there's value there if
something has gone wrong and you're just trying to get the machine up
and running.
Thanks!
- Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-06 14:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 17:08 RAID Configuration For New Home Server Carlos Mennens
2010-06-01 17:56 ` Mark Knecht
2010-06-01 22:59 ` Ryan Wagoner
2010-06-02 4:03 ` Leslie Rhorer
2010-06-02 6:08 ` Simon Matthews
2010-06-02 6:33 ` Leslie Rhorer
2010-06-02 7:51 ` tron
2010-06-02 14:24 ` Leslie Rhorer
2010-06-02 7:54 ` tron
2010-06-02 13:00 ` Carlos Mennens
2010-06-02 15:31 ` John Robinson
2010-06-05 17:45 ` Kristleifur Daðason
2010-06-05 17:19 ` Leslie Rhorer
2010-06-05 19:41 ` Mark Knecht
2010-06-05 23:56 ` Leslie Rhorer
2010-06-06 1:04 ` Keld Simonsen
2010-06-06 1:57 ` Simon Matthews
2010-06-06 2:01 ` Leslie Rhorer
2010-06-06 2:43 ` Mark Knecht
2010-06-06 5:19 ` Leslie Rhorer
2010-06-06 11:23 ` Leslie Rhorer
2010-06-06 14:56 ` Mark Knecht [this message]
2010-06-06 20:47 ` Leslie Rhorer
2010-06-06 14:50 ` Mark Knecht
2010-06-06 20:35 ` Leslie Rhorer
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=AANLkTinh1WtkzAgS8cOC1idj-7tcS4OMv9s3qRGwdhrf@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.com \
/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).