[gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5

[gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5

[Pau Peris]

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

Hi,


i'm running GNU/Gentoo Linux with a custom compiled kernel and i've just
migrated from a 2.6 kernel to a 3.5.


As my HD's are on raid 0 mode i use a custom initrd file in order to be
able to boot. While kernel 2.6 is able to boot without problems the new 3.5
compiled kernel fails to boot complaining about "no block devices found".
After taking a look at initrd.cpio contained scripts i can see the failure
message is given by mdadm tool.


Does anyone has a clue about that? Thansk in advanced. :)

[-- Attachment #2: Type: text/html, Size: 736 bytes --]

Re: [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5

[Neil Bothwick]

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

On Fri, 26 Oct 2012 10:36:38 +0200, Pau Peris wrote:

> As my HD's are on raid 0 mode i use a custom initrd file in order to be
> able to boot. While kernel 2.6 is able to boot without problems the new
> 3.5 compiled kernel fails to boot complaining about "no block devices
> found". After taking a look at initrd.cpio contained scripts i can see
> the failure message is given by mdadm tool.

Add "set -x" to the top of your custom init script to see what's going on.


-- 
Neil Bothwick

Why do programmers get Halloween and Christmas confused?
Because oct 31 is the same as dec 25.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5

[J. Roeleveld]

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

Pau Peris <sibok1981@gmail.com> wrote:

>Hi,
>
>
>i'm running GNU/Gentoo Linux with a custom compiled kernel and i've
>just
>migrated from a 2.6 kernel to a 3.5.
>
>
>As my HD's are on raid 0 mode i use a custom initrd file in order to be
>able to boot. While kernel 2.6 is able to boot without problems the new
>3.5
>compiled kernel fails to boot complaining about "no block devices
>found".
>After taking a look at initrd.cpio contained scripts i can see the
>failure
>message is given by mdadm tool.
>
>
>Does anyone has a clue about that? Thansk in advanced. :)

Paul,

I had a similar issue with a new system. There it was caused by mdadm trying to start the raid devices before all the drives were identified.
Try disabling "Asynchronous SCSI scanning" in the kernel config. (CONFIG_SCSI_SCAN_ASYNC)
Or add "scsi_mod.scan=sync" to the kernel commandline to see if it's the same cause.

--
Joost
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 1525 bytes --]

Re: [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5

[Pau Peris]

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

Hi,

thanks a lot for both answers.

I've just checked my kernel config and CONFIG_SCSI_SCAN_ASYNC is not setted
so gonna take a look at it all with "set -x".

Thanks :)

2012/10/26 J. Roeleveld <joost@antarean.org>

> Pau Peris <sibok1981@gmail.com> wrote:
>>
>> Hi,
>>
>>
>> i'm running GNU/Gentoo Linux with a custom compiled kernel and i've just
>> migrated from a 2.6 kernel to a 3.5.
>>
>>
>> As my HD's are on raid 0 mode i use a custom initrd file in order to be
>> able to boot. While kernel 2.6 is able to boot without problems the new 3.5
>> compiled kernel fails to boot complaining about "no block devices found".
>> After taking a look at initrd.cpio contained scripts i can see the failure
>> message is given by mdadm tool.
>>
>>
>> Does anyone has a clue about that? Thansk in advanced. :)
>>
>>
> Paul,
>
> I had a similar issue with a new system. There it was caused by mdadm
> trying to start the raid devices before all the drives were identified.
> Try disabling "Asynchronous SCSI scanning" in the kernel config.
> (CONFIG_SCSI_SCAN_ASYNC)
> Or add "scsi_mod.scan=sync" to the kernel commandline to see if it's the
> same cause.
>
> --
> Joost
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>



-- 
Pau Peris Rodriguez
http://www.pauperis.com

Aquest correu electrònic conté informació de caràcter confidencial dirigida
exclusivament al seu/s destinatari/s tant mateix va dirigit exclusivament
als seu/s destinatari/s primari/s present/s. Així, queda prohibida la seva
divulgació, copia o distribució a tercers sense prèvia autorització escrita
per part de Pau Peris Rodriguez. En cas d'haver rebut aquesta informació
per error, es demana que es notifiqui immediatament d'aquesta circumstancia
mitjançant la direcció electrònica de la persona del emissor.

[-- Attachment #2: Type: text/html, Size: 3718 bytes --]

Re: [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5

[Paul Hartman]

On Fri, Oct 26, 2012 at 3:36 AM, Pau Peris <sibok1981@gmail.com> wrote:
> Hi,
>
>
> i'm running GNU/Gentoo Linux with a custom compiled kernel and i've just
> migrated from a 2.6 kernel to a 3.5.
>
>
> As my HD's are on raid 0 mode i use a custom initrd file in order to be able
> to boot. While kernel 2.6 is able to boot without problems the new 3.5
> compiled kernel fails to boot complaining about "no block devices found".
> After taking a look at initrd.cpio contained scripts i can see the failure
> message is given by mdadm tool.
>
>
> Does anyone has a clue about that? Thansk in advanced. :)

There is a bug with certain versions of mdadm failing to assemble
arrays, maybe you using one of the affected versions.
see https://bugs.gentoo.org/show_bug.cgi?id=416081

Re: [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5

[Pau Peris]

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

Thx a lot Paul,

this morning i noticed there was some kind of issue on my old initrd which
works fine for 2.6 kernels, so created a new initrd which works fine and
let me to boot into GNU/Gentoo Linux with same 3.5 bzImage.

Gonna check if the issue came from mdadm, thx :)

2012/10/26 Paul Hartman <paul.hartman+gentoo@gmail.com>

> On Fri, Oct 26, 2012 at 3:36 AM, Pau Peris <sibok1981@gmail.com> wrote:
> > Hi,
> >
> >
> > i'm running GNU/Gentoo Linux with a custom compiled kernel and i've just
> > migrated from a 2.6 kernel to a 3.5.
> >
> >
> > As my HD's are on raid 0 mode i use a custom initrd file in order to be
> able
> > to boot. While kernel 2.6 is able to boot without problems the new 3.5
> > compiled kernel fails to boot complaining about "no block devices found".
> > After taking a look at initrd.cpio contained scripts i can see the
> failure
> > message is given by mdadm tool.
> >
> >
> > Does anyone has a clue about that? Thansk in advanced. :)
>
> There is a bug with certain versions of mdadm failing to assemble
> arrays, maybe you using one of the affected versions.
> see https://bugs.gentoo.org/show_bug.cgi?id=416081
>
>


-- 
Pau Peris Rodriguez
http://www.pauperis.com

Aquest correu electrònic conté informació de caràcter confidencial dirigida
exclusivament al seu/s destinatari/s tant mateix va dirigit exclusivament
als seu/s destinatari/s primari/s present/s. Així, queda prohibida la seva
divulgació, copia o distribució a tercers sense prèvia autorització escrita
per part de Pau Peris Rodriguez. En cas d'haver rebut aquesta informació
per error, es demana que es notifiqui immediatament d'aquesta circumstancia
mitjançant la direcció electrònica de la persona del emissor.

[-- Attachment #2: Type: text/html, Size: 3316 bytes --]