Hi
I have a disk reported as Health = 58%. The Overview says :
"Problems occurred during the spin up of the disk 1 times. This can be caused by the disk itself or huge power load (weak power supply).
149 errors occured during data transfer. This may indicate problem of the device or with data/power cables. It is recommended to examine and replace the cables if possible.
At this point, warranty replacement of the disk is not yet possible, only if the health drops further.
It is recommended to examine the log of the disk regularly. All new problems found will be logged there.
It is recommended to continuously monitor the hard disk status."
How can I tell when this happened? For example say I tried a new PSU to potentially remedy this, how can I tell if the situation is resolved?
Also the Log says:
02/11/2014 04:13:17,#197 Current Pending Sector Count 1 -> 0
My web search shows that "The raw value of this attribute indicates the total number of sectors waiting for remapping. Later, when some of these sectors are read successfully, the value is decreased. "
So I'm guessing this value going to zero could possibly be a resolution of the above data transfer error as related to the spin-up error? Or could it just be some other unrelated event?
Establishing timeline of problems
-
hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Establishing timeline of problems
Hi,
Of course there is a timeline of problems: it is the LOG page of the hard disk.
There Hard Disk Sentinel shows all new hard disk problems (occured during both the active and inactive periods of Hard Disk Sentinel) found since the hard disk first analysed and monitoring started by Hard Disk Sentinel.
> How can I tell when this happened?
If this happened before first starting Hard Disk Sentinel, then it is not possible to tell when it happened.
Hard disk drives log the amount of errors / total count of problems, but not their date/time.
Hard Disk Sentinel when detects the change of the reported error counters, it immdiately adds the entry to the LOG page.
You can even configure an alert to be sent (for example in e-mail) when this happens, so then you'll be notified about any new (even minor) problem, degradation.
So if you'd have Hard Disk Sentinel installed previously, then it would show how the value changed with time.
> For example say I tried a new PSU to potentially remedy this, how can I tell if the situation is resolved?
Yes, it is possible that it is in the background. Environmental issues (unstable power source, PSU problems, cables/connection issues, general PC case overheating, etc...) can all cause problems.
But if that time Hard Disk Sentinel was not yet installed, we can't say for sure that the PSU caused the problems.
> Also the Log says:
> 02/11/2014 04:13:17,#197 Current Pending Sector Count 1 -> 0
This entry saved since Hard Disk Sentinel first detected the drive.
Then there was a pending (weak) sector reported, which is now fixed, which means that the status of the hard disk drive generally improved. The counter 1 changed to 0.
> My web search shows that "The raw value of this attribute indicates the total number of sectors waiting for remapping.
> Later, when some of these sectors are read successfully, the value is decreased. "
This is partially correct only.
It would be better if you search on the correct place, which exactly describes the situation:
http://www.hdsentinel.com/hard_disk_cas ... ectors.php
This shows everything about weak sectors, how they created, what they mean, how to fix and avoid them.
This clearly shows that the hard disk not neccessarily remap such sectors, but if their status verified and corrected, then the counter decreases without remapping the sector (without replacing with sector from the spare area).
> So I'm guessing this value going to zero could possibly be a resolution of the above data transfer error
> as related to the spin-up error? Or could it just be some other unrelated event?
These are usually different things, related to different parts of the hard disk.
Spin up issues are often related to power supply (see http://www.hdsentinel.com/hard_disk_case_spin_retry.php for details about this problem).
Data transfer errors are more related to cables / connections / overheat / overclocking which causes a general instability (see http://www.hdsentinel.com/hard_disk_cas ... _error.php for more information about this problem)
And the weak sector are more related to disk surface. Both of the above can cause one weak sector, but as it is alone not too serious (and as you can see, it may be fixed with time) it was not the biggest issue.
Generally, the Support -> Knowledge Base -> Hard Disk Cases and the F.A.Q. sections (and the Help of course) describe most common hard disk problems
Of course there is a timeline of problems: it is the LOG page of the hard disk.
There Hard Disk Sentinel shows all new hard disk problems (occured during both the active and inactive periods of Hard Disk Sentinel) found since the hard disk first analysed and monitoring started by Hard Disk Sentinel.
> How can I tell when this happened?
If this happened before first starting Hard Disk Sentinel, then it is not possible to tell when it happened.
Hard disk drives log the amount of errors / total count of problems, but not their date/time.
Hard Disk Sentinel when detects the change of the reported error counters, it immdiately adds the entry to the LOG page.
You can even configure an alert to be sent (for example in e-mail) when this happens, so then you'll be notified about any new (even minor) problem, degradation.
So if you'd have Hard Disk Sentinel installed previously, then it would show how the value changed with time.
> For example say I tried a new PSU to potentially remedy this, how can I tell if the situation is resolved?
Yes, it is possible that it is in the background. Environmental issues (unstable power source, PSU problems, cables/connection issues, general PC case overheating, etc...) can all cause problems.
But if that time Hard Disk Sentinel was not yet installed, we can't say for sure that the PSU caused the problems.
> Also the Log says:
> 02/11/2014 04:13:17,#197 Current Pending Sector Count 1 -> 0
This entry saved since Hard Disk Sentinel first detected the drive.
Then there was a pending (weak) sector reported, which is now fixed, which means that the status of the hard disk drive generally improved. The counter 1 changed to 0.
> My web search shows that "The raw value of this attribute indicates the total number of sectors waiting for remapping.
> Later, when some of these sectors are read successfully, the value is decreased. "
This is partially correct only.
It would be better if you search on the correct place, which exactly describes the situation:
http://www.hdsentinel.com/hard_disk_cas ... ectors.php
This shows everything about weak sectors, how they created, what they mean, how to fix and avoid them.
This clearly shows that the hard disk not neccessarily remap such sectors, but if their status verified and corrected, then the counter decreases without remapping the sector (without replacing with sector from the spare area).
> So I'm guessing this value going to zero could possibly be a resolution of the above data transfer error
> as related to the spin-up error? Or could it just be some other unrelated event?
These are usually different things, related to different parts of the hard disk.
Spin up issues are often related to power supply (see http://www.hdsentinel.com/hard_disk_case_spin_retry.php for details about this problem).
Data transfer errors are more related to cables / connections / overheat / overclocking which causes a general instability (see http://www.hdsentinel.com/hard_disk_cas ... _error.php for more information about this problem)
And the weak sector are more related to disk surface. Both of the above can cause one weak sector, but as it is alone not too serious (and as you can see, it may be fixed with time) it was not the biggest issue.
Generally, the Support -> Knowledge Base -> Hard Disk Cases and the F.A.Q. sections (and the Help of course) describe most common hard disk problems