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 6012B138CD0 for ; Sun, 31 May 2015 14:18:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 57FA7E0956; Sun, 31 May 2015 14:18:22 +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 2AC20E091B for ; Sun, 31 May 2015 14:18:20 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01a.mail.zen.net.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Yz44B-0002va-QB for gentoo-user@lists.gentoo.org; Sun, 31 May 2015 14:18:19 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Failure to start md at boot Date: Sun, 31 May 2015 15:18:19 +0100 Message-ID: <30493751.oiu7PPONDd@wstn> User-Agent: KMail/4.14.3 (Linux/3.18.12-gentoo; KDE/4.14.3; x86_64; ; ) In-Reply-To: <201505311307.08048.michaelkintzios@gmail.com> References: <130281423.bVMpkzIQgX@wstn> <201505311307.08048.michaelkintzios@gmail.com> 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: 88daada5-3393-412b-9963-621cf3d035ab X-Archives-Hash: 65f35875f3c073d4dea850ad21e6e68f On Sunday 31 May 2015 13:06:58 Mick wrote: > On Sunday 31 May 2015 10:01:43 Peter Humphrey wrote: > > 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. > > Did you try my suggestion to (also) specify the metadata type to see if it > makes a difference? Ah, no, I missed that. I'll try it and see how it goes. > Something else to check: > > Make sure that the /etc/fstab name for the RAID device and your > /etc/mdadm.conf use the same name. Yes, they're the same - but fstab isn't consulted until long after the VGs are started, is it? > If you have changed the partitions on this RAID, or recreated it, make sure > to run 'mdadm --zero-superblock', before you delete the partition from the > partition table, or you could recover it when you recreate a partition if > not zeroed. Nope, haven't changed anything since creation. > Have a look at smartctl output to see if there is something wrong with any > of the md7 disks. I was suspicious of the spinning disks I've just replaced with SSDs, because they were showing a few errors and not a lot of remaining life. Smartctl doesn't recognise the SSDs so I don't know how useful its output is, but it's not reporting anything anyway. -- Rgds Peter