From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-155405-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 40F1C1381FA
	for <garchives@archives.gentoo.org>; Sat,  3 May 2014 12:17:46 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id E6673E0AD7;
	Sat,  3 May 2014 12:17:39 +0000 (UTC)
Received: from ns1.bonedaddy.net (ns1.bonedaddy.net [70.91.141.202])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id D8450E0A6E
	for <gentoo-user@lists.gentoo.org>; Sat,  3 May 2014 12:17:38 +0000 (UTC)
Received: from ns1.bonedaddy.net (ns1.bonedaddy.net [192.168.1.4])
	by ns1.bonedaddy.net (8.14.8/8.14.4) with ESMTP id s43CHbD7002353
	for <gentoo-user@lists.gentoo.org>; Sat, 3 May 2014 08:17:37 -0400
Date: Sat, 3 May 2014 08:17:37 -0400
From: Todd Goodman <tsg@bonedaddy.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] boot problems
Message-ID: <20140503121737.GQ8451@ns1.bonedaddy.net>
References: <5364C0F9.3000906@xunil.at>
 <1408053.9yvCLYqSXs@andromeda>
 <5364CF2D.80407@xunil.at>
 <6539833.TvPLtO1q9n@andromeda>
 <5364D25F.5040004@xunil.at>
 <5364D55A.7020106@xunil.at>
 <5364DC3A.5060801@xunil.at>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5364DC3A.5060801@xunil.at>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Archives-Salt: c8dea5ef-2ae1-43bd-b770-196f532c5c36
X-Archives-Hash: f6221acf1db16e3b4734826d9d138759

* Stefan G. Weichinger <lists@xunil.at> [140503 08:09]:
> Am 03.05.2014 13:39, schrieb Stefan G. Weichinger:
> 
> > Booted with "rd.auto=1" and now I also get a funny start job
> > running/waiting for /dev/sda1 (/ on the SSD).
> > 
> > Oh my! :-)
> > 
> > pasta now.
> 
> So, back from speed-lunch now ;-)
> 
> While cooking the pasta I got a bit further:
> 
> Box boots now with kernel 3.14.1 and with commented LVs in fstab.
> 
> When I login and check there are no mdadm-raids assembled.
> 
> When I "mdadm -A --scan" they get correctly assembled:
> 
> 
> # cat /proc/mdstat
> Personalities : [raid1]
> md4 : active raid1 sdb3[0] sdc6[2]
>       52395904 blocks super 1.2 [2/2] [UU]
> 
> md1 : active raid1 sdb6[0] sdc3[1]
>       623963072 blocks [2/2] [UU]
> 
> (Don't ask for the strange setup with sdb3/sdc6 and sdb6/sdc3,
> historically grown somehow ...)
> 
> "vgchange -ay" then gets me all my LVs. Great so far.
> 
> So the question is, what part of the whole setup should now assemble the
> arrays?
> 
> I think, dracut, right?
> 
> So I will now test booting with these funny "rd.auto" kernel line
> parameters ...
> 
> Has mdadm.service to be enabled as well? Or is that redundant in a way?
> 
> Stefan

FWIW, I have a similar problem with mdadm and dracut and do something
similarly to what's described in:

http://rich0gentoo.wordpress.com/2012/01/21/a-quick-dracut-module/

Todd