November 20, 201411 yr Hi, after years of running unRaid without any mayor issues. I now face this: I had a failing disk6. As I had replaced drive from time to time was not worried. While replacing that drive with a new one and rebuilding disk6 the parity drive failed too (like 75% through the rebuilding). So I lost data of disk6, bad. But I can live with it, as it did only hold backups I have redundant somewhere else. I had another spare drive, so I replaced the parity drive too. Now the state looks like in the attached screenshot. I have the option to rebuild, but if I try that in syslog I only see: Nov 20 21:44:20 bunk kernel: md: recovery thread woken up ... Nov 20 21:44:20 bunk kernel: md: recovery thread has nothing to resync Any ideas how I can get from here to a state where unraid calculates parity again? Thxs, Tim
November 21, 201411 yr Before you begin, how badly did these drives fail? Can you post smartctl reports for review? Did you look at the smart reports? To move forward with what you have... Capture the serial numbers that are currently configured. You can try stopping the array unassigning the drives in question (since they were both replaced). start the array. then stop it again after everything settles Assign the data drive in slot 6 (Remember the serial) start the array. Validate all data drives are where they should be. FYI, I would not FORMAT anything until I validated the data drives are what I expect. stop the array. Assign the parity drive (last). start the array. Parity calculation should kick off. if that doesn't work, you can always start from scratch with new config in the utilities tab. capture main screen drive assignments some how. stop the array. go to new config. enable the new config. assign data drives first. start the array. validate data. FYI, I would not FORMAT anything until I validated the data drives are what I expect. stop the array. assign parity last. start the array.
November 22, 201411 yr Author Frank1940: Yes, both new disks where precleared. I have resolved the issue by following WeeboTechs advised. Had to assign new config, parity sync is running now. I have checked the failed disks on another machine and actually the data drive that was reported failing looks ok checking with smartctl now. So not sure what that was. The parity drive that failed was a Seagate Constellation CS SED 3TB and is no even recognized as SATA device anymore now, so I started RMA for it. I'll format the new drive when I have parity over the existing disks again. Thxs alot for the help.
Archived
This topic is now archived and is closed to further replies.