achong0 Posted June 19, 2013 Share Posted June 19, 2013 Hi all, I am currently having an issue with my Parity drive continuously showing up with a red ball, and having millions and millions of writes to it. I have tried to rebuild the parity, and it works fine for a few days, and then dies again. I am not sure what the problem is, as I don't believe that we had any power outages in the mean time. I know that the rest of the forums basically say that I need to swap out the parity drive, however if this is avoidable, I would like to keep it that way. Unraid keeps telling me that my array is not protected, although I am still able to get to all of the data on the other drives, and everything seems to just work, apart from this drive. When I try to run a smart test, I get "The /boot/smarthistory/smarthistory.php file does not exist." and I am not sure what to do about it. Does anyone have any suggestions on what to do? If you do, please PM me. Regards Alistair Quote Link to comment
garycase Posted June 19, 2013 Share Posted June 19, 2013 Try a different SATA cable, and be sure it's firmly seated. If that doesn't resolve it, then you need to simply replace the drive. r.e. "... Unraid keeps telling me that my array is not protected, although I am still able to get to all of the data on the other drives, and everything seems to just work, apart from this drive. " ==> Of course you can read the data on the other drives, as they're okay. What UnRAID is telling you is that if one of those drives fails, you'll lose the data on it (that's what "not protected" means). If you had good parity, then if one of those drives failed, you could still read the data from it, as UnRAID would rebuild it from the rest of the drives + parity ==> that's what fault-tolerance is all about Quote Link to comment
dgaschk Posted June 19, 2013 Share Posted June 19, 2013 Disk 1 is having read issues as well. How many drives have non-zero errors counts? Attach a syslog. zip if needed. Quote Link to comment
garycase Posted June 19, 2013 Share Posted June 19, 2013 As dgaschk noted, disk1 also has errors. You need to double-check all of your cabling; your power connectors; etc. Something is clearly not right. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.