On Tue, Aug 30, 2016 at 3:58 AM, Gareth Pye <gar...@cerberos.id.au> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
