Skip to main content
Server Fault

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • +1, and the general philosophy of your answer applies perfectly also to similar issues at least with MD, LVM, Btrfs, and GPFS, in my experience (only the actual commands will vary, of course). Most of the time, it's hardware that needs fixing first, and then it's typically quite easy to get the volume/array going, unless you make it much worse by randomly hitting things with hammers you find somewhere on the internet before actually understanding the root cause/fixing the flaky HW. In short, any kind of --force, or "read-write bruteforce repair" are last resort, not first thing to try. Commented 17 hours ago
  • Thank you for this well thought-out guide! I'll post more detains in a reply below. Commented 16 hours ago
  • It dawned on me that something similar had happened before, so i tried something: I tried importing the pool omitting each device in turn. Eventually, the pool imported perfectly, (no -X needed), so something was up with that device (which by all my observations still worked, and once I properly added another device in place of that one, I formatted it, and that worked too). The disk in question was the one I was intending to replace anyway, as I know it to be failing (slowly). Anyway the issue is fixed but if you have any more questions about what happened, I'm happy to answer them. Commented 16 hours ago