November 7, 201114 yr I misunderstood. I though one of the bad drives was parity. You can remove them and the run initconfig.
November 7, 201114 yr You have 14-15TB of drive space there. I would be a bit more careful on what you do. This is the type of incident I'm afraid of getting myself in to with using unraid. I won't know what to do, and while the forum members are fantastic in trying to help you they are no means of securing a solution. Please, if you have a lot of data on those drives be real careful. I hate to see people lose files and data.
November 7, 201114 yr Author Thanks. That is exactly why I have been so patient. I wanted to have an expert opinion before I start guessing at a solution. I did an "initconfig" on the system last night and it is rebuilding parity now. It's 70% through with no errors, so far, so I'm cautiously optimistic that I'll only lose the data on the failed drive. I'm going to try to mount that failed drive on my PC by installing the reiser drivers and see if there is anything I can salvage from it. I'll post my results soon.
November 8, 201114 yr Thanks. That is exactly why I have been so patient. I wanted to have an expert opinion before I start guessing at a solution. I did an "initconfig" on the system last night and it is rebuilding parity now. It's 70% through with no errors, so far, so I'm cautiously optimistic that I'll only lose the data on the failed drive. I'm going to try to mount that failed drive on my PC by installing the reiser drivers and see if there is anything I can salvage from it. I'll post my results soon. Oh well, too late to help you now. If you had forced unRAID to think your failed drive was really failed, and the other red-balled drive that was working was good, you might not have lost anything. Basically, a modification of the "trust" procedure, but you would have had to force unRAID to think sdh was good (I think that was the drive still responding) As an example, It if was disk 2 you were forcing to be "built", you would type initconfig and immediately then type mdcmd set invalidslot 2 which would force disk2 to be reconstructed from what it thinks is valid parity in combination with all the other disks. To do this ALL THE OTHER DISKS MUST BE FUNCTIONING. Since you now have re-calculated parity, there's nothing else you can do to use it to recover the dead drive.
Archived
This topic is now archived and is closed to further replies.