October 20, 201510 yr I'm having an issue where my parity drive goes in to an error state due to read errors after about one month of running. At first I thought it was an issue with the sas/sata cabe, but I've replaced that and it still comes back. I'm able to temporarily fix the issue by stopping the array and restarting. Then the disc shows back up and I can add to the array and do a fresh parity calculation. At this point I think it's time to RMA the drive (WD Red 6TB), but I thought I'd check in here to see if this is more likely to be an interface issue. The drive is connected via my AOC-SAS2LP-MV8. However, this card has been otherwise very reliable. This problem started when I upgraded some of my hardware (including the drive but not the card) and also upgraded to v6. Thanks for any advice!
October 20, 201510 yr You may want to search the forums and read up on the issues associated with the SAS2LP under unRAID 6. How do the Smart reports look for this drive? Also, do you have the 6TB drive set to spin down? If so, try disabling that and keep it spinning all the time. That is one of the things that worked for me while trying to stabilize my array. People are also replacing that card with IBM M1015's or similar LSI based cards.
October 21, 201510 yr Author Ok. I'll take a look at the forums for those issues. The SMART reports look fine for the drive. I will also try disabling spin down for that drive. Thanks.
Archived
This topic is now archived and is closed to further replies.