Skip to main content
2 of 2
replaced http://serverfault.com/ with https://serverfault.com/

narrow situation but broad answer - closing useful?

I admit in advance: This egoisticly motivated: I do not consider the question a good one (relevant information missing, no research effort recognizable) I just got into a bad mood because I like my answer (and was thinking about better approaches for the case that the asker was going to try this) and now I had to realize that the question got closed:

Can I recover data from a RAID5 after accidental changed of disk order?

I can accept that problems with a certain hardware (related to that hardware in that sense that either the problem cannot occur with other products or that the solution is not usable for other products) are considered as too narrow and closed but does that make sense if an answer offers (or at least tries to) a generic approach?

Obviously you can create disk order problems with many controllers. I don't know though whether other ones are stupid enough to result in such failure. But the question title is broad and the answer is broad. So why should this one not be of use for later users searching for the problem?

Hauke Laging
  • 5.4k
  • 11
  • 8