Hi. I have been using HD Sentinel for a few years now, and I find it very valuable to keep track of my HDs' status. However I am having trouble understanding something I saw today.
I have a Seagate drive that is just over 3 years old. It is used as a storage drive in an external enclosure. Today I fired it up and decided to have a look at HD Sentinel. I found four entries in the log for today (5/17/2014)
5/17/2014 12:50:44 PM,#197 Current Pending Sector Count 119 -> 123
5/17/2014 12:45:41 PM,#197 Current Pending Sector Count 109 -> 119
5/17/2014 12:45:41 PM,#5 Reallocated Sectors Count 0 -> 1
5/17/2014 12:40:24 PM,#197 Current Pending Sector Count 106 -> 109
But when I look at the S.M.A.R.T. window, I don't see anything reflecting those values. Can you help me understand how to read the information in this window? I have read the pages on your site explaining monitoring and S.M.A.R.T. values.
Additionally, I must point out that the drive was not even active at the times listed in the log. There WAS another HD from Western Digital that I was testing in the enclosure (that HD was a brand new drive that turned out to be failing). My computer clock has NOT been changed at any point.
The overview gives 100% for health and performance ("PERFECT").
I am including two screencaps from the program.
Thanks for any assistance you can provide.
Errors in log not shown in S.M.A.R.T. window?
Errors in log not shown in S.M.A.R.T. window?
- Attachments
-
- smart.PNG (81.72 KiB) Viewed 4992 times
-
- log.PNG (23.24 KiB) Viewed 4992 times
- hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Errors in log not shown in S.M.A.R.T. window?
Thanks for your message and excuse me for the issue.
Yes, recently we found that in some rare situations (depending on the external enclosure / adapter models) it is possible that after replacing the external hard disk (which had problems) the error-log may still show the errors previously detected with the other (previously used) drive.
Can you please use Report menu -> Send test report to developer option now, to check the situation, verify if this is the case?
Generally, after this discovered, version 4.50.1b version released with a fix, to prevent this from happening, but it would be nice to check if your external enclosure if also affected.
So I'd recommend to
- download and install the latest possible version (which is 4.50.4b now, from this link: http://www.hdsentinel.com/beta4/hdsenti ... p4504b.zip
- clear the error log by using the "Clear Log" button, to make sure that the log should be empty for this hard disk
- please use Report menu -> Send test report to developer option now - and maybe if you'll still encounter similar issue later. There should be no such problems, but it would be nice to confirm, depending on the external enclosure / hard disk.
Thanks for your attention and excuse me for the issues with this particular configuration.
Yes, recently we found that in some rare situations (depending on the external enclosure / adapter models) it is possible that after replacing the external hard disk (which had problems) the error-log may still show the errors previously detected with the other (previously used) drive.
Can you please use Report menu -> Send test report to developer option now, to check the situation, verify if this is the case?
Generally, after this discovered, version 4.50.1b version released with a fix, to prevent this from happening, but it would be nice to check if your external enclosure if also affected.
So I'd recommend to
- download and install the latest possible version (which is 4.50.4b now, from this link: http://www.hdsentinel.com/beta4/hdsenti ... p4504b.zip
- clear the error log by using the "Clear Log" button, to make sure that the log should be empty for this hard disk
- please use Report menu -> Send test report to developer option now - and maybe if you'll still encounter similar issue later. There should be no such problems, but it would be nice to confirm, depending on the external enclosure / hard disk.
Thanks for your attention and excuse me for the issues with this particular configuration.