From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-user+bounces-143654-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 531F51381F3 for <garchives@archives.gentoo.org>; Sun, 23 Dec 2012 12:28:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D76DF21C14A; Sun, 23 Dec 2012 12:28:45 +0000 (UTC) Received: from mail.muc.de (colin.muc.de [193.149.48.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 72A3121C166 for <gentoo-user@lists.gentoo.org>; Sun, 23 Dec 2012 12:27:23 +0000 (UTC) Received: (qmail 94241 invoked by uid 3782); 23 Dec 2012 12:27:21 -0000 Received: from acm.muc.de (pD951ACB6.dip.t-dialin.net [217.81.172.182]) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 23 Dec 2012 13:27:20 +0100 Received: (qmail 23733 invoked by uid 1000); 23 Dec 2012 12:20:48 -0000 Date: Sun, 23 Dec 2012 12:20:48 +0000 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How broken is my raid device /dev/md6? Message-ID: <20121223122048.GA23711@acm.acm> References: <20121222135342.GA3955@acm.acm> <1442628.2Dn10PouDC@localhost> 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: <1442628.2Dn10PouDC@localhost> User-Agent: Mutt/1.5.21 (2010-09-15) X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Alan Mackenzie <acm@muc.de> X-Primary-Address: acm@muc.de X-Archives-Salt: e1afc516-1531-42c8-b648-4de1178975ae X-Archives-Hash: 411e28350c048858db0d9dcfdf29899d On Sat, Dec 22, 2012 at 03:24:53PM +0100, Volker Armin Hemmann wrote: > Am Samstag, 22. Dezember 2012, 13:53:42 schrieb Alan Mackenzie: > > Hi, all. > > Just built kernel 3.6.11 and when I tried to install it with lilo, I got > > this difficult error message: > > Fatal: Trying to map files from unnamed device 0x0000 (NFS/RAID > > mirror down ?) > > . So I eventually had a look at dmesg for my raid setup, and found this > > - note lines 15 - 19: > > [ 2.148410] md: Waiting for all devices to be available before > > autodetect > > [ 2.149891] md: If you don't use raid, use raid=noautodetect > > [ 2.151546] md: Autodetecting RAID arrays. > > [ 2.180356] md: Scanned 4 and added 4 devices. > > [ 2.181819] md: autorun ... > > [ 2.183244] md: considering sdb6 ... > > [ 2.184666] md: adding sdb6 ... > > [ 2.186079] md: sdb3 has different UUID to sdb6 > > [ 2.187492] md: adding sda6 ... > > [ 2.188884] md: sda3 has different UUID to sdb6 > > [ 2.190484] md: created md6 > > [ 2.191883] md: bind<sda6> > > [ 2.193224] md: bind<sdb6> > > [ 2.194538] md: running: <sdb6><sda6> > > 15 [ 2.195855] md: kicking non-fresh sda6 from array! > > 16 [ 2.197154] md: unbind<sda6> > > 17 [ 2.205840] md: export_rdev(sda6) > > [ 2.207176] bio: create slab <bio-1> at 1 > > 19 [ 2.208520] md/raid1:md6: active with 1 out of 2 mirrors > > [ 2.209835] md6: detected capacity change from 0 to 34359672832 > > [ 2.211187] md: considering sdb3 ... > > [ 2.212444] md: adding sdb3 ... > > [ 2.213691] md: adding sda3 ... > > [ 2.215117] md: created md3 > > [ 2.216349] md: bind<sda3> > > [ 2.217569] md: bind<sdb3> > > [ 2.218765] md: running: <sdb3><sda3> > > [ 2.220025] md/raid1:md3: active with 2 out of 2 mirrors > > [ 2.221231] md3: detected capacity change from 0 to 429507543040 > > [ 2.222508] md: ... autorun DONE. > > [ 2.230821] md6: unknown partition table > > . Further perusal of a log file showed this error first happened on > > 2012-11-29. It would appear /dev/md6 has been firing on one cylinder > > ever since, and I've been unaware of this. :-( > > What does it mean for sda6 to be "non-fresh"? > > /dev/md6 is my root partition (including /usr :-(), so I can't unmount > > it for investigation. > > Could somebody please suggest how I might go about repairing this > > problem. > boot from systemrescuecd > mdadm -S /dev/md6 > mdadm -A /dev/md6 This didn't quite work, since mdadm -A merely restarted the array without the non-fresh partition. Still it got me searching, and what eventually worked was mdadm /dev/md6 -a /dev/sda6. (Where -a stands for "add".) The mdadm man page is very vague for this use case. > get some coffee. Make some popcorn. The resync will take some while. Indeed it did. The coffee settled me down somewhat. Thanks again! -- Alan Mackenzie (Nuremberg, Germany).