From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 4D7FF1381FA for ; Sat, 3 May 2014 12:52:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D8EB0E0B04; Sat, 3 May 2014 12:52:22 +0000 (UTC) Received: from mail-ig0-f193.google.com (mail-ig0-f193.google.com [209.85.213.193]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C5CF9E0AE6 for ; Sat, 3 May 2014 12:52:21 +0000 (UTC) Received: by mail-ig0-f193.google.com with SMTP id uq10so572493igb.4 for ; Sat, 03 May 2014 05:52:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=aJKJNQn6Dp0e4N2rWIha9vmYR4bJiauBYN6SbZ7NXXI=; b=YjMoCn+eTf+OjMmmp5zyPaWCGrxHQDXU7LEbl09Tk4jXw2KAgmKmvfR2gobZicRijP vblNfxDWESkeZIVUYhWdXMaUkU0zdJhApH63hSW60cgQqXOydlA3RbiuV4RrHIjuE7/C Zo1wW0zCHLWWsezyQcCYoViNqevpRY6TK3GbrM6mjw1/0vaBW0WF+DJNr7PGpeyfwcdV QLa+F7nXK3Zv6JHoYb53mobrL6rN2awS9kfASLnTe73LQBG3C8Sg3y+WvQDI1OyLabjA c8TAocC/XYx9XOustVqrptqPyMej3ReVirzadPhzqJg6c74yHC091JY7dERCM2tb9IhT ZY7Q== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.42.21.133 with SMTP id k5mr21315659icb.1.1399121540990; Sat, 03 May 2014 05:52:20 -0700 (PDT) Received: by 10.64.57.104 with HTTP; Sat, 3 May 2014 05:52:20 -0700 (PDT) In-Reply-To: <5364DC3A.5060801@xunil.at> 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> Date: Sat, 3 May 2014 08:52:20 -0400 Message-ID: Subject: Re: [gentoo-user] boot problems From: Tom H To: Gentoo User Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 38370368-4acd-45cc-aff0-f915486f8e91 X-Archives-Hash: fedcadb1cef568b2d2ad7235206aeb5b On Sat, May 3, 2014 at 8:08 AM, Stefan G. Weichinger wrote: > > 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? Try "rd.md.uuid=<...>" for all the md arrays that you want to bring up.