Should I be worried with these hard drive test results?

If you've made backed up images or backed up files then you can use the drive until the terminal event.

Many OP will replace a Windows drive displaying any significant problems (for example recurrent logical errors or chkdsk problems).

The time cost for troubleshooting can be compared to a working drive.

Also before drive failure there can be performance problems such as slow read, slow write, hangs, freezes, BSOD, etc.

Once a drive has had bad blocks you can follow the event viewer to view the frequency of new reports:
Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using (howtogeek.com)

For chkdsk consider using these switches: chkdsk /b /v C:

This is the deepest switch, can take a long time, and makes sure if completed that bad blocks are no longer used.

Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

The C: displayed; 4 KB in bad sectors
The D: displayed: 20 KB in bad sectors

S.M.A.R.T. Attribute: Current Pending Sector Count | Knowledge Base (acronis.com)
Current Pending Sector Count Warning: What You Need To Know (harddrivegeek.com)
What to Do When Encountering Current Pending Sector Count? (minitool.com)
How to Fix Current Pending Sector Count Warning | by Satyeshu Kumar | Medium


Run the crucial scanner to view replacement options:
Crucial System Scanner
I'll stop doing tests now. Just gonna monitor changes using Sentinel and Event Viewer. Thanks!
 
I get this on hd sentinel, for my HDD seagate ST500DM002 (october 2012 ? ):


HDSentinel.png

Read More:
 
I get this on hd sentinel, for my HDD seagate ST500DM002 (october 2012 ? ):


View attachment 64089

Read More:
Wow 8 years! We almost have the same SMART readings except with the temp (I really should get my laptop cleaned). Do you know if it has bad sectors?
 
Also, why does your ssd have only 98% health?
Not sure, I get these values:
177,Wear Leveling Count,0,98,98,OK (Always passing),29
241,Total LBA Written,0,99,99,OK (Always passing),27409282440

No, I don't have bad sectors on the seagate hdd.
You can also compare your values with others if you click the world icon (the eight one, from right and from left).
 
That's why I'm confused with my tests. When chkdsk detects bad sectors, aren't disk monitoring tools supposed to detect them too? Especially SeaTools.
 
There's a difference between bad sectors not used (SeaTools repaired) and the same bad sectors which of course still exist.
 
I'm not sure if I understand you. Do you mean those bad sectors that chkdsk found have been repaired already by SeaTools? So when I run chkdsk again it won't report anything under bad sectors anymore?
 
Quote: I'm not sure if I understand you. Do you mean those bad sectors that chkdsk found have been repaired already by SeaTools? So when I run chkdsk again it won't report anything under bad sectors anymore? Quote

Repaired is not the word. Skipped over purposely is what's happening. Not to get too technical, but there's a reserve of spare sectors. Once that gets used up, you can no longer substitute the good for the skipped. Better than when I started in this business when the repaired were kept as a file and I wasted time looking at a totally unusable string of garbage.
 
I'm too sleepy now so I'll just get back to this tomorrow. And I know I said I'll stop but I just want to understand more so I can stop obsessing with this issue. Thank you everyone!
 
If a sector has some physical flaw, it cannot be repaired. This may be due to an impurity in the materials, or a defect/damage caused during manufacturing. Either way, it is bad and always will be bad.

But a sector can be marked as bad for other reasons. Perhaps there was a formatting error, corrupt data in the file tables, or something else that caused it to be marked as bad in the tables at the factory or some time later.

A hard drive analysis tool like Seatools or Check Disk may analyze the sector again and discover it is good, just incorrectly marked as bad in the tables. It will update the tables to mark that sector available for use again. It did not "repair" the bad sector. It just found it was not bad after all.
 
Not just to pile on this is much ado about nothing because we have some indication the drive has some bad sectors checkdisk may have dealt with
(hiding them from Windows basically) but where I stopped was the drive is 5 years old and there is nothing more important than preserving files and data and a 5 year old hard drive is just too old to feel good about regardless of what the tests say. athey are inexpoensive these days so time to move on if for no other reason than a hard drive lasted well for 5 years.
 
Hello. I'm back again. I just wanna ask if this is normal. My hard drive has 2 partitions, C and D. C is where Windows is installed. Copying from C to D is very fast. The average is 50 MB/s and it sometimes reaches 200 MB/s. Copying files from C to C is has the same speeds. Now, copying from D to C is extremely slow. It usually starts at 20+ MB/s then it goes down to usually 1 MB/s or slower. Same with copying from D to D. Something that only happens when copying from D to C is if the file is particularly large like 3 GB or bigger then the whole computer slows down. I can't launch applications. And the applications that I use while the transfer is happening lag too. I uninstalled my antivirus but the problem still persists. I'm not sure if this happened before Windows got fixed or when I ran those chkdsk because I don't usually exchange big files between the 2 partitions. I also tested copying a 2 GB file from my external drive to both C and D and the speeds were quite fast, about 50 MB/s to 100 MB/s.

I'm also getting these on Event Viewer. I'm not sure if they're related but they mention disk and C drive

Type : Information
Date : 12/10/2020
Time : 4:13:31 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/10/2020
Time : 3:32:47 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/10/2020
Time : 3:29:27 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/10/2020
Time : 3:24:00 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/10/2020
Time : 3:08:42 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/10/2020
Time : 1:49:58 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/10/2020
Time : 1:40:40 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/10/2020
Time : 1:38:15 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/10/2020
Time : 1:20:02 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/10/2020
Time : 1:19:28 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/10/2020
Time : 1:19:11 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Error
Date : 12/10/2020
Time : 1:12:24 PM
Event : 25
Source : volsnap
Category : None
User : N/A
Computer : Server
Description:
The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

Type : Information
Date : 12/10/2020
Time : 1:06:47 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/10/2020
Time : 11:11:27 AM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/10/2020
Time : 11:09:00 AM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/9/2020
Time : 9:51:26 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/9/2020
Time : 7:38:44 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/9/2020
Time : 7:35:06 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/9/2020
Time : 7:31:22 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/9/2020
Time : 7:31:13 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/9/2020
Time : 6:35:01 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/9/2020
Time : 6:32:54 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/9/2020
Time : 4:50:42 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/9/2020
Time : 4:44:51 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/9/2020
Time : 4:31:22 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/9/2020
Time : 4:27:52 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/9/2020
Time : 1:21:05 PM
Event : 33
Source : volsnap
Category : None
User : N/A
Computer : Server
Description:
The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.

Type : Information
Date : 12/8/2020
Time : 6:51:31 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/8/2020
Time : 5:44:39 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/8/2020
Time : 1:00:53 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/7/2020
Time : 10:49:36 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/7/2020
Time : 10:39:36 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/5/2020
Time : 10:15:12 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/5/2020
Time : 10:05:19 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/5/2020
Time : 9:08:51 PM
Event : 4
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service stopped.

Type : Information
Date : 12/5/2020
Time : 8:58:52 PM
Event : 3
Source : Virtual Disk Service
Category : None
User : N/A
Computer : Server
Description:
Service started.

Type : Information
Date : 12/3/2020
Time : 9:34:00 PM
Event : 33
Source : volsnap
Category : None
User : N/A
Computer : Server
Description:
The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.

And fortunately, the hard drive is still doing fine so far. No bad block logs on event viewer and no changes in SMART.
 
Bad Sectors Explained: Why Hard Drives Get Bad Sectors and What You Can Do About It

“A few bad sectors don’t indicate that a hard drive is about to fail — they can just happen. However, if your hard drive is rapidly developing bad sectors, it may be a sign that your hard drive is failing.”

What Is a bad sector and how can I repair it?

Bad sectors are fairly common with normal computer use and the imperfections of the world we live in . . .


The presence of a few bad sectors is of very little concern. What is of concern is if you have a bad sector count that is not stable and rising rapidly. It is not at all uncommon for a drive to develop a few bad sectors over its service lifetime (which, in my experience, generally exceeds 10 years for most of them) and they are designed to handle that eventuality.

The myth that a drive having developed a couple of bad sectors over time, with no change in count over long periods of time after any count change, being on death's door and in need of immediate replacement needs to die. It will also be interesting to see how this gets carried over to SSDs, as myths often do.
 
@britechguy
In my experience with spinners since 1995, you are exactly correct.

As with anything, there is always an exception. Those 2.5'' laptop Seagates are mostly (not all of them) good for about 5-7 years depending on use.

I quit using Seagate years ago based on experience and data. I went through 2 6TB Seagate on my surveillance system in 1.5 years, switched to WD, and haven't had an issue since. I lost a Seagate 8TB in my offsite NAS after 6 months, switched to WD, and haven't had an issue since. All drives mentioned were surveillance or NAS grade.
Then again, I had a 2TB Seagate as a backup drive in an old PC that lasted 10+ years.

Backblaze Hard Drive Stats

This is my 2cents only. I don't want to hijack the thread. :) We'll go to the lounge if more discussion is needed.
 
Rob,

Well, it's absolutely certain that for all brands, over time, certain models have proven problematic. Some so much so that lawsuits ensued. I just want to make clear that my statements are about the general case. When known "problem children" are involved, one has to view things with a more jaundiced eye.

But the concept that the presence of bad sectors, in and of itself, indicates a drive in imminent or even not-so-imminent failure needed to die years ago. And I am shocked at how frequently it continues to be promulgated to this day. It's the rate of acquisition of bad sectors that is on the increase and over a short period of time that's the red flag. If your bad sector count ticks up by, say, one every couple of years, if that, you don't have a problem.
 
I think the age of the drive almost means more than the amount of bad sectors and the older the drive the more likely it will continue to produce bad sectors
and since the average used doe not backup anything regularly or even at all I like to use ther age of 5 years as my end of life for most hard drives though my experience to Brian is similar in that WD drives always last longer and again in my experience Seagates seldom make it that long.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top