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 117621381F3 for ; Sat, 22 Dec 2012 14:26:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 232A721C03A; Sat, 22 Dec 2012 14:26:08 +0000 (UTC) Received: from mail-bk0-f47.google.com (mail-bk0-f47.google.com [209.85.214.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AEF0FE0698 for ; Sat, 22 Dec 2012 14:24:57 +0000 (UTC) Received: by mail-bk0-f47.google.com with SMTP id j4so2799161bkw.6 for ; Sat, 22 Dec 2012 06:24:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding :content-type; bh=COTxy1ZAQPa2nP6Rpct2yl6GaPAwnr1euBFcpSuz/Sk=; b=Skv2h1rV2DVnxxDzSA/7YeSOBfIiCe+u2ZcHhhuwvHlbvL3DKDwrbuygrwpRuoo0Ck SJxXvgYzN5HdHtCzVkgTzKS51sB80k79bpvPazBlEr9rWJpc5HCS1rF6ZFcz6k8uGF9Q 5fo3SOjINBM5yEEnZfIYSZio1uendMUXqGYQ/yOXTVfM5B2Tkjpk28eNwcVWa8rtvFa9 X32xKlj+1ub0PqI+JIOQ6EaSHBZ8GZP3Hl+pPagOsGz3CUeMhNTgK5PwvFKqEJe+6Z9U ZIe7S+nAuHcGmGV824L/E8nkCT0VzYwYkZVxyr+1u9RU/La5OD928w7QOfq2NQJ8nJeL PySA== X-Received: by 10.204.9.139 with SMTP id l11mr7989517bkl.133.1356186296173; Sat, 22 Dec 2012 06:24:56 -0800 (PST) Received: from localhost.localnet (p4FC60065.dip0.t-ipconnect.de. [79.198.0.101]) by mx.google.com with ESMTPS id l17sm12058850bkw.12.2012.12.22.06.24.54 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 22 Dec 2012 06:24:55 -0800 (PST) From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Cc: Alan Mackenzie Subject: Re: [gentoo-user] How broken is my raid device /dev/md6? Date: Sat, 22 Dec 2012 15:24:53 +0100 Message-ID: <1442628.2Dn10PouDC@localhost> User-Agent: KMail/4.9.4 (Linux/3.4.20; KDE/4.9.4; x86_64; ; ) In-Reply-To: <20121222135342.GA3955@acm.acm> References: <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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: 92aef654-5cca-4a69-a42a-c5abe33f2c3b X-Archives-Hash: 6273574a91298b7730c0e6da7afe89a3 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 > [ 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. boot from systemrescuecd mdadm -S /dev/md6 mdadm -A /dev/md6 get some coffee. Make some popcorn. The resync will take some while. > > Thanks! -- #163933