I bought an 8TB WD easystore external HD which has (and yes pretty much everyone knows this) a red drive EFAX (WDC WD80EFAX-68LHPN0). I ran the short and extended tests on HD sentinel and everything was fine.
Now when i left it attached to my server which has stablebit scanner, i received an email stating"
One or more disks are damaged and have data on them that is unreadable:
WD easystore 25FB USB Device - 344 KB unreadable (688 sectors) - The rest of the disk is still being scanned
Model: WDC WD80EFAX-68LHPN0"
When i look at the sectors it is the very first block part of it is which is unreadable (Red color block). I did a file scan and that was normal. EDIT: The rest of the drive on the surface scan checked out completely normal.
Given that i didnt find something with HD sentinel, is this potentially a false alarm especially given its the first block? I vaguely remember having a similar issue nearly 9 months back on another external drive and it turned out a false alarm. There was something about using a beta rather than stable version of scanner. I am running currently 2.5.2.3103 beta. I forget what the return policy for BB is and if this is a real issue, id rather return it now than have to setup a warranty with HD.
Question
asdaHP
I bought an 8TB WD easystore external HD which has (and yes pretty much everyone knows this) a red drive EFAX (WDC WD80EFAX-68LHPN0). I ran the short and extended tests on HD sentinel and everything was fine.
Now when i left it attached to my server which has stablebit scanner, i received an email stating"
One or more disks are damaged and have data on them that is unreadable:
WD easystore 25FB USB Device - 344 KB unreadable (688 sectors) - The rest of the disk is still being scanned
When i look at the sectors it is the very first block part of it is which is unreadable (Red color block). I did a file scan and that was normal. EDIT: The rest of the drive on the surface scan checked out completely normal.
Given that i didnt find something with HD sentinel, is this potentially a false alarm especially given its the first block? I vaguely remember having a similar issue nearly 9 months back on another external drive and it turned out a false alarm. There was something about using a beta rather than stable version of scanner. I am running currently 2.5.2.3103 beta. I forget what the return policy for BB is and if this is a real issue, id rather return it now than have to setup a warranty with HD.
thank you
Link to comment
Share on other sites
16 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.