Raid system fails to boot after moving from 2.6 kernel to 3.5 - linux.gentoo.user

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
linux.gentoo.user
Message from discussion Raid system fails to boot after moving from 2.6 kernel to 3.5
Path: ha8ni72329wib.1!nntp.google.com!feeder2.cambriumusenet.nl!feed.tweaknews.nl!209.197.12.246.MISMATCH!nx02.iad01.newshosting.com!newshosting.com!216.196.98.146.MISMATCH!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!nrc-news.nrc.ca!goblin3!goblin.stu.neva.ru!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!news.musoftware.de!wum.musoftware.de!newsfeed.x-privat.org!bofh.it!news.nic.it!robomod
From: "J. Roeleveld" <jo...@antarean.org>
Newsgroups: linux.gentoo.user
Subject: Re: [gentoo-user] Raid system fails to boot after moving from 2.6 kernel to 3.5
Date: Fri, 26 Oct 2012 11:20:02 +0200
Message-ID: <jYOf8-7mj-19@gated-at.bofh.it>
References: <jYNCq-6rL-17@gated-at.bofh.it>
User-Agent: K-9 Mail for Android
Reply-To: gentoo-u...@lists.gentoo.org
MIME-Version: 1.0
Approved: robo...@news.nic.it
Lines: 77
Organization: linux.* mail to news gateway
Sender: robo...@news.nic.it
Bytes: 4328
Content-Type: multipart/alternative; boundary="----F2P0VIMEIN2A1D3V1QSP3E4U0JT5J6"

------F2P0VIMEIN2A1D3V1QSP3E4U0JT5J6
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Pau Peris <sibok1...@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 try=
ing 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=3Dsync" to the kernel commandline to see if it's th=
e same cause.

--
Joost
--=20
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
------F2P0VIMEIN2A1D3V1QSP3E4U0JT5J6
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head/><body><html><head></head><body><div class=3D"gmail_quote">Pa=
u Peris &lt;sibok1...@gmail.com&gt; wrote:<blockquote class=3D"gmail_quot=
e" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 20=
4, 204); padding-left: 1ex;">

<p style=3D"margin:0px">Hi,</p><p style=3D"margin:0px"><br /></p><p style=
=3D"margin:0px">i&#39;m running GNU/Gentoo Linux with a custom compiled k=
ernel and i&#39;ve just migrated from a 2.6 kernel to a 3.5.</p><p style=3D=
"margin:0px">
<br /></p><p style=3D"margin:0px">As my HD&#39;s are on raid 0 mode i use=
 a custom initrd file in order to be able to boot. While kernel 2.6 is ab=
le to boot without problems the new 3.5 compiled kernel fails to boot com=
plaining about &quot;no block devices found&quot;. After taking a look at=
 initrd.cpio contained scripts i can see the failure message is given by =
mdadm tool.</p>
<p style=3D"margin:0px"><br /></p><p style=3D"margin:0px">Does anyone has=
 a clue about that? Thansk in advanced. :)</p><div><br /></div>
</blockquote></div><br clear=3D"all">Paul,<br>
<br>
I had a similar issue with a new system. There it was caused by mdadm try=
ing to start the raid devices before all the drives were identified.<br>
Try disabling &quot;Asynchronous SCSI scanning&quot; in the kernel config=
. (CONFIG_SCSI_SCAN_ASYNC)<br>
Or add &quot;scsi_mod.scan=3Dsync&quot; to the kernel commandline to see =
if it&#39;s the same cause.<br>
<br>
--<br>
Joost<br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body=
></html></body></html>
------F2P0VIMEIN2A1D3V1QSP3E4U0JT5J6--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
