| 1 |
On Montag 20 Oktober 2008, Conway S. Smith wrote: |
| 2 |
> On Mon, 20 Oct 2008 13:24:11 +0200 |
| 3 |
> |
| 4 |
> Volker Armin Hemmann <volker.armin.hemmann@××××××××××××.de> wrote: |
| 5 |
> > On Montag 20 Oktober 2008, Conway S. Smith wrote: |
| 6 |
> > > On Mon, 20 Oct 2008 08:54:20 +0200 |
| 7 |
> > > |
| 8 |
> > > Wolfgang Liebich <Wolfgang.Liebich@×××××××.com> wrote: |
| 9 |
> > > > Hi, |
| 10 |
> > > > |
| 11 |
> > > > <SNIP> |
| 12 |
> > > > |
| 13 |
> > > > > the howtos on gentoo-wiki worked well for me. |
| 14 |
> > > > |
| 15 |
> > > > I'm working with them, too. Just one question remains: I want |
| 16 |
> > > > to use udev. Do I have to create the md devices or does udev |
| 17 |
> > > > that for me? |
| 18 |
> > > |
| 19 |
> > > udev will do it for you. But make sure your initramfs init script |
| 20 |
> > > unmounts /sys & /proc. |
| 21 |
> > |
| 22 |
> > just don't use an initramfs/initrd. |
| 23 |
> |
| 24 |
> From my reading initramfs/initrd is the preferred way of handling |
| 25 |
> root filesystem on MD RAID - and the only way for metadata 1.[012] |
| 26 |
> (although I'm having trouble finding where I read that only 0.90 |
| 27 |
> works w/ in-kernel detection/assembly). |
| 28 |
> |
| 29 |
> From /usr/share/doc/mdadm-2.6.7/README.initramfs.bz2: "The preferred |
| 30 |
> way to assemble md arrays at boot time is using 'mdadm' or |
| 31 |
> 'mdassemble' (which is a trimmed-down mdadm). To assemble an array |
| 32 |
> which contains the root filesystem, mdadm needs to be run before that |
| 33 |
> filesystem is mounted, and so needs to be run from an initial-ram-fs." |
| 34 |
> |
| 35 |
after a nice person on this list gave me a good tip, I was able to (and I |
| 36 |
still do) have root on raid1 without initrd/ramfs crap. |
| 37 |
|
| 38 |
commandline: |
| 39 |
root=/dev/md1 md=1,1,/dev/sda3,/dev/sdb3 nopat nmi_watchdog=0 |
| 40 |
|
| 41 |
md auto assembling before init kicks in: |
| 42 |
[ 4.066796] md: Autodetecting RAID arrays. |
| 43 |
[ 4.139083] md: Scanned 8 and added 8 devices. |
| 44 |
[ 4.139158] md: autorun ... |
| 45 |
[ 4.139232] md: considering sdb6 ... |
| 46 |
[ 4.139309] md: adding sdb6 ... |
| 47 |
[ 4.139384] md: sdb5 has different UUID to sdb6 |
| 48 |
[ 4.139460] md: sdb3 has different UUID to sdb6 |
| 49 |
[ 4.139535] md: sdb1 has different UUID to sdb6 |
| 50 |
[ 4.139611] md: adding sda6 ... |
| 51 |
[ 4.139686] md: sda5 has different UUID to sdb6 |
| 52 |
[ 4.139761] md: sda3 has different UUID to sdb6 |
| 53 |
[ 4.139837] md: sda1 has different UUID to sdb6 |
| 54 |
[ 4.140008] md: created md3 |
| 55 |
[ 4.140084] md: bind<sda6> |
| 56 |
[ 4.140162] md: bind<sdb6> |
| 57 |
[ 4.140240] md: running: <sdb6><sda6> |
| 58 |
[ 4.140533] raid1: raid set md3 active with 2 out of 2 mirrors |
| 59 |
[ 4.140650] md: considering sdb5 ... |
| 60 |
[ 4.140726] md: adding sdb5 ... |
| 61 |
[ 4.140801] md: sdb3 has different UUID to sdb5 |
| 62 |
[ 4.140884] md: sdb1 has different UUID to sdb5 |
| 63 |
[ 4.140960] md: adding sda5 ... |
| 64 |
[ 4.141034] md: sda3 has different UUID to sdb5 |
| 65 |
[ 4.141110] md: sda1 has different UUID to sdb5 |
| 66 |
[ 4.141259] md: created md2 |
| 67 |
[ 4.141334] md: bind<sda5> |
| 68 |
[ 4.141413] md: bind<sdb5> |
| 69 |
[ 4.141491] md: running: <sdb5><sda5> |
| 70 |
[ 4.141757] raid1: raid set md2 active with 2 out of 2 mirrors |
| 71 |
[ 4.141872] md: considering sdb3 ... |
| 72 |
[ 4.141950] md: adding sdb3 ... |
| 73 |
[ 4.142025] md: sdb1 has different UUID to sdb3 |
| 74 |
[ 4.142101] md: adding sda3 ... |
| 75 |
[ 4.142175] md: sda1 has different UUID to sdb3 |
| 76 |
[ 4.142325] md: created md1 |
| 77 |
[ 4.142399] md: bind<sda3> |
| 78 |
[ 4.142476] md: bind<sdb3> |
| 79 |
[ 4.142554] md: running: <sdb3><sda3> |
| 80 |
[ 4.142818] raid1: raid set md1 active with 2 out of 2 mirrors |
| 81 |
[ 4.142932] md: considering sdb1 ... |
| 82 |
[ 4.143010] md: adding sdb1 ... |
| 83 |
[ 4.143086] md: adding sda1 ... |
| 84 |
[ 4.143160] md: created md0 |
| 85 |
[ 4.143234] md: bind<sda1> |
| 86 |
[ 4.143315] md: bind<sdb1> |
| 87 |
[ 4.143400] md: running: <sdb1><sda1> |
| 88 |
[ 4.143666] raid1: raid set md0 active with 2 out of 2 mirrors |
| 89 |
[ 4.143779] md: ... autorun DONE. |
| 90 |
[ 4.143876] md: Loading md1: 1 |
| 91 |
[ 4.143958] md: couldn't update array info. -22 |
| 92 |
[ 4.144071] md: could not open unknown-block(0,1). |
| 93 |
[ 4.144147] md: md_import_device returned -6 |
| 94 |
[ 4.144230] md: could not bd_claim sda3. |
| 95 |
[ 4.144305] md: md_import_device returned -16 |
| 96 |
[ 4.144382] md: could not bd_claim sdb3. |
| 97 |
[ 4.144457] md: md_import_device returned -16 |
| 98 |
[ 4.144533] md: starting md1 failed |
| 99 |
[ 4.189731] reiser4: md1: found disk format 4.0.0. |
| 100 |
[ 6.456886] VFS: Mounted root (reiser4 filesystem) readonly. |
| 101 |
[ 6.456975] Freeing unused kernel memory: 316k freed |
| 102 |
|
| 103 |
I know what man mdadm says - that initrd is prefered because it is more |
| 104 |
'flexible' - but I prefer not using an initrd because I don't need that crap |
| 105 |
and I really don't want to waste another 2 seconds of boot time on it. |
Archives