I am trialing drivepool and scanner on a Windows7x64 home premium machine with an ASRock H97 board using onboard USB3 and SATA3 connected drives.
1) Using 2.5.1.3602 it seems that the settings-scanner-heat-warning threshold is ignored for all my drives. The default install set this at 32F and all my drives alerted at around 89F. I changed the threshold to 103F but they still alerted. I got around this by telling each drive to ignore the MAX temp threshold, but that's not the same thing is it? I have since installed the Beta version due to my next issue but have not removed the individual drive override to check this issue..
2) I started a scan on a WD MyBook 1230 USB 4TB drive in hopes of testing it before shucking the case. It was running clean when I noticed no smart data being collected. I noticed a thread on the forums which it was indicated to install the BETA version and make changes to advanced settings. Which I did. Started a scan again and no smart data and immediately reported "unable to read 214 sectors". These appear to be the first sectors it started to scan. It is still scanning so I don't know how it will finish up but which scan do I believe?? If it ends up with only 214 sectors should I return it rather than shucking the case? Is that enough to be a considered a problem. Incidentally I have three of these and two report exactly the same 214 unreadable sectors and the third has yet to find a problem. Also is there any fix to get the SMART data? Will it be available when the drive is connected directly via SATA rather than USB3.0? It seems the other thread on here is left unresolved on this matter..
Question
frank33v
I am trialing drivepool and scanner on a Windows7x64 home premium machine with an ASRock H97 board using onboard USB3 and SATA3 connected drives.
1) Using 2.5.1.3602 it seems that the settings-scanner-heat-warning threshold is ignored for all my drives. The default install set this at 32F and all my drives alerted at around 89F. I changed the threshold to 103F but they still alerted. I got around this by telling each drive to ignore the MAX temp threshold, but that's not the same thing is it? I have since installed the Beta version due to my next issue but have not removed the individual drive override to check this issue..
2) I started a scan on a WD MyBook 1230 USB 4TB drive in hopes of testing it before shucking the case. It was running clean when I noticed no smart data being collected. I noticed a thread on the forums which it was indicated to install the BETA version and make changes to advanced settings. Which I did. Started a scan again and no smart data and immediately reported "unable to read 214 sectors". These appear to be the first sectors it started to scan. It is still scanning so I don't know how it will finish up but which scan do I believe?? If it ends up with only 214 sectors should I return it rather than shucking the case? Is that enough to be a considered a problem. Incidentally I have three of these and two report exactly the same 214 unreadable sectors and the third has yet to find a problem. Also is there any fix to get the SMART data? Will it be available when the drive is connected directly via SATA rather than USB3.0? It seems the other thread on here is left unresolved on this matter..
Link to comment
Share on other sites
5 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.