public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pau Peris <sibok1981@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5
Date: Fri, 26 Oct 2012 11:23:48 +0200	[thread overview]
Message-ID: <CAOq67MAJBTy+Vu-AeYhtOum-bx+haiRkUwjoL2+uY1Bo_h0ybg@mail.gmail.com> (raw)
In-Reply-To: <2989063f-e3e9-436e-9987-584d14305b04@email.android.com>

[-- 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 --]

  reply	other threads:[~2012-10-26  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26  8:36 [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5 Pau Peris
2012-10-26  8:48 ` Neil Bothwick
2012-10-26  9:10 ` J. Roeleveld
2012-10-26  9:23   ` Pau Peris [this message]
2012-10-26 15:04 ` Paul Hartman
2012-10-26 15:39   ` Pau Peris

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=CAOq67MAJBTy+Vu-AeYhtOum-bx+haiRkUwjoL2+uY1Bo_h0ybg@mail.gmail.com \
    --to=sibok1981@gmail.com \
    --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