Hey guys. first time caller, long time listener. I'm at my wit's end... I'm not a pro at server setup, not by a long-shot. Any help at all would be hugely appreciated.
Here's my story (diagnostics attached), please stay with me if you can:
My array for quite a while has consisted of 13 drives (parity and 1 thru 12. No cache, I guess I'm patient). About a year ago I'd noticed that my "Disk 10" decided to take on an Egyptian theme and adopted a pyramid icon next to it (running 6.0.2 beta at the time, I believe). All of the contents were still accessible and usable without a hiccup, even though the temperature and some other stats were not reported and the web interface didn't think it was "spun-up". I'd chalked it up as some sort of glitch because it "worked" as far as I could tell and ignorance ensued.
Fast-forward to a week ago: I upgraded to 6.1.9 and Disk 10 then showed a big, red X that, when hovered over, reported "device is disabled, contents emulated". That added to the annoyance that more and more often I would get errors when writing files to the server. I have been stockpiling hard drives so I figured it was time to retire/replace Disk 10 as the physical drive must've taken a dump. That's just what I did... I copied all of the drive's contents to a big ol' external drive beforehand (hooray?), I shut her down, swapped out the drive and fired it back up. I defined the new HDD in Disk 10's spot and ran the super-long clear and then ran the super-super-long data rebuild. Good news: I got my green dot back! Bad news: about 90% of the files were not rebuilt to the drive (though all the folders were still there) and most all of the files that were still present were corrupt in that they would not open at all. These corrupt files also refused to be deleted, overwritten, renamed, etc. FYI: the web interface also thought the rebuilt drive was back up to the original content size (used/free).
Again, luckily, I have all of the contents of that a-hole Disk 10 currently backed-up on an external drive so all is not lost. I'd hoped that I could just reformat the drive so I redefined to xfs, rather than the original rfs because that's the only way I could figure out to initiate a reformat... I ended up with an empty Disk 10 with a happy green dot again. Not so thrilled to be "manually" rewriting 4TBs of data to a drive, but I'd accepted my defeat. Then, after just transferring approximately 5GB of data that damned red X came back again! It's back to "emulating" what is basically zero contents.
If you're still with me (thank you) my questions are pretty straightforward and short:
1) How do I get my parity drive to wipe its "memory" of the sh*tshow that is Disk 10 so it doesn't try to rebuild a worthless piece of garbage on a brand new, perfectly functional and "cleared" drive that I hope/plan to just manually repopulate?
2) Is there some other way I have/need to do this? Like I give this new physical drive a different number, say... disk 13, then once populated with the data I want on it, redefine it to become the new Disk 10 somehow? (Reason I want Disk 10 specifically to return is that it contains media that's already defined within a library).
Hey... you made it this far! Thank you so much!
server-diagnostics-20160907-1904.zip
server-diagnostics-20160907-1904.zip