wisem2540 Posted November 30, 2018 Share Posted November 30, 2018 Noticed these while rebuilding parity on a new parity drive. Just want to make sure they are normal. Any feedback is appreciated. Parity rebuild is also hitting some slow spots. 30-40MB unraid-syslog-20181129-1937.zip unraid-diagnostics-20181129-1942.zip Quote Link to comment
JorgeB Posted November 30, 2018 Share Posted November 30, 2018 Disk5 is causing the errors, SMART looks fine, maybe a connection issue, though since it's the infamous ST3000DM001 you never know. Quote Link to comment
wisem2540 Posted November 30, 2018 Author Share Posted November 30, 2018 8 hours ago, johnnie.black said: Disk5 is causing the errors, SMART looks fine, maybe a connection issue, though since it's the infamous ST3000DM001 you never know. Thanks for the reply. Its connected to the same backplane and HBA as everything else, so who knows? Is this a bad drive in general or just bad for unraid? I guess what I am asking is should I just swap it out, and if so, would it function ok for normal desktop use, or as an external HD? Quote Link to comment
JorgeB Posted November 30, 2018 Share Posted November 30, 2018 2 hours ago, wisem2540 said: Is this a bad drive in general or just bad for unraid? So notorious it has its own wiki page: https://en.wikipedia.org/wiki/ST3000DM001 Quote Link to comment
Squid Posted November 30, 2018 Share Posted November 30, 2018 The ST3000DM001's are far far more reliable IMHO than say a WD. But I know that I'm a lone wolf on that opinion. Quote Link to comment
John_M Posted November 30, 2018 Share Posted November 30, 2018 55 minutes ago, Squid said: But I know that I'm a lone wolf on that opinion. For some reason I read that as Ironwolf FWIW my preferred brand is Toshiba, so I suppose I'm not "normal" either. Quote Link to comment
wisem2540 Posted November 30, 2018 Author Share Posted November 30, 2018 I still see a couple of these "task abort messages in log - presumably they could be from the same drive, as it is no longer part of the array, but is still connected to the system. I am rebuilding Disk5 onto the 6TB now (Former Parity drive) Nov 30 16:26:12 Unraid kernel: sd 3:0:3:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 I assume drive sdi is this questionable drive, but for some reason, its not showing in my web interface right now... don't know why. I figured it would show under unassigned. Thanks for checking unraid-syslog-20181130-1743.zip unraid-diagnostics-20181130-1741.zip Quote Link to comment
JorgeB Posted December 1, 2018 Share Posted December 1, 2018 Yes, it's the same disk, it dropped offline now, so at least no more errors. Quote Link to comment
wisem2540 Posted December 1, 2018 Author Share Posted December 1, 2018 1 minute ago, johnnie.black said: Yes, it's the same disk, it dropped offline now, so at least no more errors. Thanks for the quick reply JB! 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.