From: Pau Peris <sibok1981@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5
Date: Fri, 26 Oct 2012 10:36:38 +0200 [thread overview]
Message-ID: <CAOq67MBt2tgAWYTX2qwYcaLpq18erJafmraXOBu397+QTV+yeg@mail.gmail.com> (raw)
[-- 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 --]
next reply other threads:[~2012-10-26 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 8:36 Pau Peris [this message]
2012-10-26 8:48 ` [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5 Neil Bothwick
2012-10-26 9:10 ` J. Roeleveld
2012-10-26 9:23 ` Pau Peris
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=CAOq67MBt2tgAWYTX2qwYcaLpq18erJafmraXOBu397+QTV+yeg@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