April 21, 200917 yr Thanks again Robj! Booting into normal Unraid mode (and not BubbaRaid) seemed to fix my issue with running the smartctl tests. It's running the long test now without being aborted. Even if passes, I think I may try to verify that it is the parity drive clicking during copies and RMA that. It definitely does not seem normal when you hear 10-20 clicks in a row while copying. Ok that is odd. I had array stopped, made sure bubba/unmenu weren't running and I started the long test on the parity. After about 30 min the smart status showed again aborted by host?!?! I'm wondering, does the drive spin down setting affect it during a smart test? It was set to 30 minutes. I'm setting it to never and running the test again.
April 21, 200917 yr Thanks again Robj! Booting into normal Unraid mode (and not BubbaRaid) seemed to fix my issue with running the smartctl tests. It's running the long test now without being aborted. Even if passes, I think I may try to verify that it is the parity drive clicking during copies and RMA that. It definitely does not seem normal when you hear 10-20 clicks in a row while copying. Ok that is odd. I had array stopped, made sure bubba/unmenu weren't running and I started the long test on the parity. After about 30 min the smart status showed again aborted by host?!?! I'm wondering, does the drive spin down setting affect it during a smart test? It was set to 30 minutes. I'm setting it to never and running the test again. I would think it would abort. To run the long smart test the disk must be spinning. If you explicitly send it a command to stop spinning, it might have exactly the effect you are describing. (The spin-down is an explicit command from emhttp in recent versions of unRAID and does not rely on the disk's time-out setting.)
April 21, 200917 yr Thanks again Robj! Booting into normal Unraid mode (and not BubbaRaid) seemed to fix my issue with running the smartctl tests. It's running the long test now without being aborted. Even if passes, I think I may try to verify that it is the parity drive clicking during copies and RMA that. It definitely does not seem normal when you hear 10-20 clicks in a row while copying. Ok that is odd. I had array stopped, made sure bubba/unmenu weren't running and I started the long test on the parity. After about 30 min the smart status showed again aborted by host?!?! I'm wondering, does the drive spin down setting affect it during a smart test? It was set to 30 minutes. I'm setting it to never and running the test again. I would think it would abort. To run the long smart test the disk must be spinning. If you explicitly send it a command to stop spinning, it might have exactly the effect you are describing. (The spin-down is an explicit command from emhttp in recent versions of unRAID and does not rely on the disk's time-out setting.) Thanks Joe for that clarification, makes sense as you explain it.
Archived
This topic is now archived and is closed to further replies.