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 AC5F9138827 for ; Fri, 2 Oct 2015 14:51:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AA80D21C08C; Fri, 2 Oct 2015 14:51:40 +0000 (UTC) Received: from smarthost01a.mail.zen.net.uk (smarthost01a.mail.zen.net.uk [212.23.1.1]) by pigeon.gentoo.org (Postfix) with ESMTP id 900CB21C026 for ; Fri, 2 Oct 2015 14:51:39 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01a.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Zi1gQ-0001aD-OR for gentoo-user@lists.gentoo.org; Fri, 02 Oct 2015 14:51:38 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Failure to start md at boot Date: Fri, 02 Oct 2015 15:51:38 +0100 Message-ID: <1579185.le34pmLpS1@wstn> User-Agent: KMail/4.14.8 (Linux/4.0.5-gentoo; KDE/4.14.8; x86_64; ; ) In-Reply-To: <130281423.bVMpkzIQgX@wstn> References: <130281423.bVMpkzIQgX@wstn> 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 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost01a-IP: [82.69.80.10] X-Archives-Salt: 35924f1a-55ca-4bea-96f8-d953b415be97 X-Archives-Hash: d77b6813f50a75a03c4641ab1f7e1e7c On Sunday 31 May 2015 10:01:43 I wrote: > I've split this out from the previous thread because it was getting messy. > I'd followed Rich Freeman's advice to specify arrays by UUID in mdadm.conf, > and this is what happened: > > On Friday 29 May 2015 01:10:52 I wrote: > > OK, so this is what I have at present. I haven't booted with it yet to > > test > > it - I'll do that in the morning: > > > > DEVICE /dev/sd[abcde][123456789] > > ARRAY /dev/md1 UUID=ea156c7f:183ca28e:c44c77eb:7ee19756 > > ARRAY /dev/md5 UUID=e7640378:966a5b3a:c44c77eb:7ee19756 > > ARRAY /dev/md7 UUID=c2d056c4:9118021f:ad73c633:b38fa97c > > Specifying the UUIDs hasn't helped. I still get failure to start /dev/md7 > during boot as often as not. What I hope will be the final postscript: I did eventually find the right setup, thus: # cat /etc/mdadm.conf # mdadm configuration file # DEVICE /dev/sd[ab][123456789] ARRAY /dev/md1 metadata=0.90 UUID=0240695f:38fe6523:7bfe4778:da957cc1 ARRAY /dev/md5 metadata=0.90 UUID=a6a8a1bf:f7058f1d:7bfe4778:da957cc1 ARRAY /dev/md7 metadata=1.2 UUID=77f93f10:1ff22cae:81c5117d:5c25873e ARRAY /dev/md8 metadata=0.90 UUID=ce921c64:3685e8c7:7bfe4778:da957cc1 ARRAY /dev/md9 metadata=1.2 UUID=0f74fff3:cdae1a64:0a44d949:4f1ad406 But I was still getting occasional failures of /dev/md7 to start - this contains all except the root and boot partitions of my everyday system, in LVM. It turns out that I had the wrong UUID specified in the file above, but nevertheless, almost always the system found the right devices to start. Now that I've corrected it I don't expect any more failures (that's what I meant when I said I hope this is the final postscript.) In case anyone's interested, I've been installing a qt5 equivalent of my main system, using md8 as the root partition and md9 (plus LVM) for everything else. Oh, except /boot, which is md1 in common with the main system. My fstabs are getting long and complicated! -- Rgds Peter