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 506AF1381F3 for ; Sat, 22 Dec 2012 14:01:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E8100E068C; Sat, 22 Dec 2012 14:01:32 +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 77E36E066B for ; Sat, 22 Dec 2012 14:00:19 +0000 (UTC) Received: (qmail 19156 invoked by uid 3782); 22 Dec 2012 14:00:16 -0000 Received: from acm.muc.de (pD9519E91.dip.t-dialin.net [217.81.158.145]) by colin.muc.de (tmda-ofmipd) with ESMTP; Sat, 22 Dec 2012 15:00:14 +0100 Received: (qmail 4013 invoked by uid 1000); 22 Dec 2012 13:53:42 -0000 Date: Sat, 22 Dec 2012 13:53:42 +0000 To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] How broken is my raid device /dev/md6? Message-ID: <20121222135342.GA3955@acm.acm> 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-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Archives-Salt: 1a037852-6c5a-441d-b0db-a3638b23b7c2 X-Archives-Hash: 9200eb3ecf6bad630fe61999bf90930e 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 [ 2.193224] md: bind [ 2.194538] md: running: 15 [ 2.195855] md: kicking non-fresh sda6 from array! 16 [ 2.197154] md: unbind 17 [ 2.205840] md: export_rdev(sda6) [ 2.207176] bio: create slab 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 [ 2.217569] md: bind [ 2.218765] md: running: [ 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. Thanks! -- Alan Mackenzie (Nuremberg, Germany).