From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f44.google.com ([209.85.218.44]:35199 "EHLO mail-oi0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751158AbcH3SE3 (ORCPT ); Tue, 30 Aug 2016 14:04:29 -0400 Received: by mail-oi0-f44.google.com with SMTP id p186so2178848oia.2 for ; Tue, 30 Aug 2016 11:04:28 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Chris Murphy Date: Tue, 30 Aug 2016 12:04:27 -0600 Message-ID: Subject: Re: Recommendation on raid5 drive error resolution To: Gareth Pye Cc: Chris Murphy , linux-btrfs Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Tue, Aug 30, 2016 at 3:58 AM, Gareth Pye wrote: > Okay, things aren't looking good. The FS wont mount for me: > http://pastebin.com/sEEdRxsN Try to mount with -o ro,degraded. I have no idea which device it'll end up dropping, but it might at least get you a read only mount so you can get stuff off - if you want - without modifying the file system. One of us would have to go look in source to see what causes "[ 163.612313] BTRFS: failed to read the system array on sdd" to appear for each device. It's suspicious that every drive produces that message, and there are no fixup messages at all ever. So it sounds like it's not even getting far enough to figure out what's bad and reconstruct from parity. And I don't even see csum errors either, which is also suspicious. It's like the boot strapping itself is failing which kinda implicates superblocks? What do you get for btrfs rescue super-recover -v /dev/sdX ? -- Chris Murphy