Let me make clear that i am NOT blaming stable bit for any of these issues; the drives in question ST3000DM001-9YN166, have been a headache from the start but am wondering how these drives could "interact" with stable bit to cause drive issues; after a few days of creating a pool with 3x3TB drives the first drive reported just "9% health" and "The drive 336 bad sectors during its self test" according to Hard disk sentinel. It also seems that this issue is not specific to me...
So what are my options; don't pool the ST3000DM001 drives; but how can we be sure that this type of "conflict" doesn't occur with other drive types and sizes
Question
PetabytesPlease
Let me make clear that i am NOT blaming stable bit for any of these issues; the drives in question ST3000DM001-9YN166, have been a headache from the start but am wondering how these drives could "interact" with stable bit to cause drive issues; after a few days of creating a pool with 3x3TB drives the first drive reported just "9% health" and "The drive 336 bad sectors during its self test" according to Hard disk sentinel. It also seems that this issue is not specific to me...
https://homeservershow.com/forums/topic/8890-seagate-st3000dm001-data-corruption/
So what are my options; don't pool the ST3000DM001 drives; but how can we be sure that this type of "conflict" doesn't occur with other drive types and sizes
Link to comment
Share on other sites
8 answers to this question
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.