From: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is an Intel motherboard RAID better or worse than software RAID?
Date: Mon, 20 Oct 2008 17:33:24 +0200 [thread overview]
Message-ID: <200810201733.24942.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <20081020073144.506f2b3a@mandalor.homelinux.net>
On Montag 20 Oktober 2008, Conway S. Smith wrote:
> On Mon, 20 Oct 2008 13:24:11 +0200
>
> Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de> wrote:
> > On Montag 20 Oktober 2008, Conway S. Smith wrote:
> > > On Mon, 20 Oct 2008 08:54:20 +0200
> > >
> > > Wolfgang Liebich <Wolfgang.Liebich@siemens.com> wrote:
> > > > Hi,
> > > >
> > > > <SNIP>
> > > >
> > > > > the howtos on gentoo-wiki worked well for me.
> > > >
> > > > I'm working with them, too. Just one question remains: I want
> > > > to use udev. Do I have to create the md devices or does udev
> > > > that for me?
> > >
> > > udev will do it for you. But make sure your initramfs init script
> > > unmounts /sys & /proc.
> >
> > just don't use an initramfs/initrd.
>
> From my reading initramfs/initrd is the preferred way of handling
> root filesystem on MD RAID - and the only way for metadata 1.[012]
> (although I'm having trouble finding where I read that only 0.90
> works w/ in-kernel detection/assembly).
>
> From /usr/share/doc/mdadm-2.6.7/README.initramfs.bz2: "The preferred
> way to assemble md arrays at boot time is using 'mdadm' or
> 'mdassemble' (which is a trimmed-down mdadm). To assemble an array
> which contains the root filesystem, mdadm needs to be run before that
> filesystem is mounted, and so needs to be run from an initial-ram-fs."
>
after a nice person on this list gave me a good tip, I was able to (and I
still do) have root on raid1 without initrd/ramfs crap.
commandline:
root=/dev/md1 md=1,1,/dev/sda3,/dev/sdb3 nopat nmi_watchdog=0
md auto assembling before init kicks in:
[ 4.066796] md: Autodetecting RAID arrays.
[ 4.139083] md: Scanned 8 and added 8 devices.
[ 4.139158] md: autorun ...
[ 4.139232] md: considering sdb6 ...
[ 4.139309] md: adding sdb6 ...
[ 4.139384] md: sdb5 has different UUID to sdb6
[ 4.139460] md: sdb3 has different UUID to sdb6
[ 4.139535] md: sdb1 has different UUID to sdb6
[ 4.139611] md: adding sda6 ...
[ 4.139686] md: sda5 has different UUID to sdb6
[ 4.139761] md: sda3 has different UUID to sdb6
[ 4.139837] md: sda1 has different UUID to sdb6
[ 4.140008] md: created md3
[ 4.140084] md: bind<sda6>
[ 4.140162] md: bind<sdb6>
[ 4.140240] md: running: <sdb6><sda6>
[ 4.140533] raid1: raid set md3 active with 2 out of 2 mirrors
[ 4.140650] md: considering sdb5 ...
[ 4.140726] md: adding sdb5 ...
[ 4.140801] md: sdb3 has different UUID to sdb5
[ 4.140884] md: sdb1 has different UUID to sdb5
[ 4.140960] md: adding sda5 ...
[ 4.141034] md: sda3 has different UUID to sdb5
[ 4.141110] md: sda1 has different UUID to sdb5
[ 4.141259] md: created md2
[ 4.141334] md: bind<sda5>
[ 4.141413] md: bind<sdb5>
[ 4.141491] md: running: <sdb5><sda5>
[ 4.141757] raid1: raid set md2 active with 2 out of 2 mirrors
[ 4.141872] md: considering sdb3 ...
[ 4.141950] md: adding sdb3 ...
[ 4.142025] md: sdb1 has different UUID to sdb3
[ 4.142101] md: adding sda3 ...
[ 4.142175] md: sda1 has different UUID to sdb3
[ 4.142325] md: created md1
[ 4.142399] md: bind<sda3>
[ 4.142476] md: bind<sdb3>
[ 4.142554] md: running: <sdb3><sda3>
[ 4.142818] raid1: raid set md1 active with 2 out of 2 mirrors
[ 4.142932] md: considering sdb1 ...
[ 4.143010] md: adding sdb1 ...
[ 4.143086] md: adding sda1 ...
[ 4.143160] md: created md0
[ 4.143234] md: bind<sda1>
[ 4.143315] md: bind<sdb1>
[ 4.143400] md: running: <sdb1><sda1>
[ 4.143666] raid1: raid set md0 active with 2 out of 2 mirrors
[ 4.143779] md: ... autorun DONE.
[ 4.143876] md: Loading md1: 1
[ 4.143958] md: couldn't update array info. -22
[ 4.144071] md: could not open unknown-block(0,1).
[ 4.144147] md: md_import_device returned -6
[ 4.144230] md: could not bd_claim sda3.
[ 4.144305] md: md_import_device returned -16
[ 4.144382] md: could not bd_claim sdb3.
[ 4.144457] md: md_import_device returned -16
[ 4.144533] md: starting md1 failed
[ 4.189731] reiser4: md1: found disk format 4.0.0.
[ 6.456886] VFS: Mounted root (reiser4 filesystem) readonly.
[ 6.456975] Freeing unused kernel memory: 316k freed
I know what man mdadm says - that initrd is prefered because it is more
'flexible' - but I prefer not using an initrd because I don't need that crap
and I really don't want to waste another 2 seconds of boot time on it.
next prev parent reply other threads:[~2008-10-20 15:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 13:08 [gentoo-user] Is an Intel motherboard RAID better or worse than software RAID? Wolfgang Liebich
2008-10-15 13:13 ` Pintér Tibor
2008-10-15 13:22 ` Alan McKinnon
2008-10-17 10:40 ` Wolfgang Liebich
2008-10-17 11:31 ` Neil Bothwick
2008-10-17 11:43 ` Volker Armin Hemmann
2008-10-18 16:54 ` Peter Humphrey
2008-10-20 6:54 ` Wolfgang Liebich
2008-10-20 9:13 ` Conway S. Smith
2008-10-20 11:24 ` Volker Armin Hemmann
2008-10-20 13:31 ` Conway S. Smith
2008-10-20 15:33 ` Volker Armin Hemmann [this message]
2008-10-21 8:59 ` Peter Humphrey
2008-10-21 18:04 ` Liebich, Wolfgang
2008-10-18 5:31 ` jormaa
2008-10-15 13:24 ` Dirk Heinrichs
2008-10-23 7:18 ` AW: " Liebich, Wolfgang
2008-10-15 13:34 ` Albert Hopkins
2008-10-15 13:41 ` Pintér Tibor
2008-10-15 14:45 ` Dan Cowsill
2008-10-15 16:48 ` Volker Armin Hemmann
2008-10-16 19:42 ` Paul Hartman
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=200810201733.24942.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--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