Gentoo Archives: gentoo-user

From: Pau Peris <sibok1981@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5
Date: Fri, 26 Oct 2012 15:41:56
Message-Id: CAOq67MC7=+aOg7ycVHL0-G0nL-XTiO2_AVm2NiDo8Om+dCZpEA@mail.gmail.com
In Reply to: Re: [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5 by Paul Hartman
1 Thx a lot Paul,
2
3 this morning i noticed there was some kind of issue on my old initrd which
4 works fine for 2.6 kernels, so created a new initrd which works fine and
5 let me to boot into GNU/Gentoo Linux with same 3.5 bzImage.
6
7 Gonna check if the issue came from mdadm, thx :)
8
9 2012/10/26 Paul Hartman <paul.hartman+gentoo@×××××.com>
10
11 > On Fri, Oct 26, 2012 at 3:36 AM, Pau Peris <sibok1981@×××××.com> wrote:
12 > > Hi,
13 > >
14 > >
15 > > i'm running GNU/Gentoo Linux with a custom compiled kernel and i've just
16 > > migrated from a 2.6 kernel to a 3.5.
17 > >
18 > >
19 > > As my HD's are on raid 0 mode i use a custom initrd file in order to be
20 > able
21 > > to boot. While kernel 2.6 is able to boot without problems the new 3.5
22 > > compiled kernel fails to boot complaining about "no block devices found".
23 > > After taking a look at initrd.cpio contained scripts i can see the
24 > failure
25 > > message is given by mdadm tool.
26 > >
27 > >
28 > > Does anyone has a clue about that? Thansk in advanced. :)
29 >
30 > There is a bug with certain versions of mdadm failing to assemble
31 > arrays, maybe you using one of the affected versions.
32 > see https://bugs.gentoo.org/show_bug.cgi?id=416081
33 >
34 >
35
36
37 --
38 Pau Peris Rodriguez
39 http://www.pauperis.com
40
41 Aquest correu electrònic conté informació de caràcter confidencial dirigida
42 exclusivament al seu/s destinatari/s tant mateix va dirigit exclusivament
43 als seu/s destinatari/s primari/s present/s. Així, queda prohibida la seva
44 divulgació, copia o distribució a tercers sense prèvia autorització escrita
45 per part de Pau Peris Rodriguez. En cas d'haver rebut aquesta informació
46 per error, es demana que es notifiqui immediatament d'aquesta circumstancia
47 mitjançant la direcció electrònica de la persona del emissor.