February 13, 201610 yr I had a parity drive fall offline and it triggered the 188 command-timeout, and has had a value of 54 ever since. unRAID keeps warning me about this every time the drive spins down and it's spun back up. I was told unRAID is supposed to remember this and not warn me again. The drive has 0 errors, and I even ran parity check twice when I noticed this, but it all came back with 0 errors. The smart check returns overall-health: passed. Thanks.
February 13, 201610 yr I had a parity drive fall offline and it triggered the 188 command-timeout, and has had a value of 54 ever since. unRAID keeps warning me about this every time the drive spins down and it's spun back up. I was told unRAID is supposed to remember this and not warn me again. The drive has 0 errors, and I even ran parity check twice when I noticed this, but it all came back with 0 errors. The smart check returns overall-health: passed. Thanks. There were some bugs with it remembering. Upgrade to 6.1.8
Archived
This topic is now archived and is closed to further replies.