public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: raid1 grub ext4
Date: Thu, 14 Apr 2011 15:14:53 +0200	[thread overview]
Message-ID: <4DA6F34D.1030701@binarywings.net> (raw)
In-Reply-To: <loom.20110414T144335-897@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]

Am 14.04.2011 14:56, schrieb James:
> Florian Philipp <lists <at> binarywings.net> writes:
> 
> 
> 
>> Your boot partition is not by any chance a logical partition and
>> therefore would be (hd0,4) and not (hd0,0)?
> 
> grub> root (hd0,4)
> Error 22: No such partition
> 
> No?
> 
> 
>> You can try to use 0.90 metadata by specifying it while creating the
>> RAID with mdadm. I'm using it myself because AFAIK this is the only way
>> for grub to handle a single RAID containing partitions instead of
>> partitions containing RAIDs.
> 
> OK so I read about this "0.90 metadata" but could not find
> details (syntax) of when and exactly how to use this information.
> OK, so, I've rebooted and got the md1, md2, md3 renamed by
> (whatever) to md125 md127 and md126, respectively. 
> 

The parameter for specifying metadata versions is -e. Try
mdadm --create --metadata=0.90 ...

Of course it can only be specified while creating the array.

The renaming is pretty ugly. You can force specific names by
circumventing the kernel autodetection. Add the following kernel parameters:
raid=noautodetect md=0,/dev/sda1,/dev/sdb1 ...

This assembles md0 with sda1 and sdb1. You can also try to keep
autodetection on and only force the numbering for your raid partition.

Hope this helps,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2011-04-14 13:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 18:12 [gentoo-user] raid1 grub ext4 James
2011-04-11 20:18 ` Mick
2011-04-12  5:57   ` Stroller
2011-04-12 14:10     ` [gentoo-user] " James
2011-04-12 14:31       ` Peter Humphrey
2011-04-12 14:57         ` Dale
2011-04-12 15:16           ` Joost Roeleveld
2011-04-12 15:44           ` Peter Humphrey
2011-04-13 10:14           ` Alex Schuster
2011-04-11 20:49 ` [gentoo-user] " Neil Bothwick
2011-04-12  2:09   ` Mark Shields
2011-04-12  9:11     ` Neil Bothwick
2011-04-12 14:20       ` [gentoo-user] " James
2011-04-12 16:53         ` James
2011-04-13  9:46           ` Florian Philipp
2011-04-14 12:56             ` James
2011-04-14 13:14               ` Florian Philipp [this message]
2011-04-14 14:41               ` Paul Hartman
2011-04-14 13:10             ` James
2011-04-14 13:41               ` James
2011-04-14 14:11                 ` Florian Philipp
2011-04-14 15:07                   ` James
2011-04-14 15:52                     ` Florian Philipp
2011-04-14 16:29                       ` James
2011-04-14 19:49                         ` Florian Philipp
2011-04-14 20:19                           ` James
2011-04-14 21:12                             ` Florian Philipp
2011-04-14 20:24                           ` James
2011-04-14 14:13                 ` Dale
2011-04-14 14:52                   ` James
2011-04-14 16:14                     ` Dale
2011-04-14 16:34                       ` James

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=4DA6F34D.1030701@binarywings.net \
    --to=lists@binarywings.net \
    --cc=gentoo-user@lists.gentoo.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