Bad Block but 100% Health?

After my PC rebooted due to a power outage, i've noticed a few "The device, \Device\Harddisk1\DR1, has a bad block." errors in event viewer. I've tried a few different HD utilities but they kind of show conflicting results. HDtune does show 0.1% damaged blocks, and HDSentinel shows that there are bad blocks/bad clusters, but it also shows the drive as in 100% health.

I'm wondering is this something i should be concerned about? The drive is fairly new, as i've only used it for about a month or so, and i haven't actually had any noticeable issues with it so far.

Windows version is 22H2 OS Build 19045.2251

zebal said:

I suggest slow format, which is a guarantee that bad blocks won't be used by system.

Since this is my OS drive it sounds like i'd have to pick up a replacement drive and reinstall windows on it first? That would be pretty funny, i literally just had to do that with this drive since it replaced another ssd that started to have issues after a few years.

With a traditional hard drive bad sectors can forecast a failure, but due to the nature of flash technology it's normal to have a small number of bad sectors on an SSD. As long as the number of bad sectors does not change, there is no reason for concern; firmware on the SSD tracks bad sectors and marks them as unusable, so even though bad sectors are present on the drive, reliability is unaffected and data is never written to them.

My SSD Has Bad Sectors | Crucial UK

Health or SMART attempts to predict drive failure.

Drives will fail with SMART values > 90% when there are power outages or drops as these are sudden events.

If SMART are run after a drive has failed other drive tests it may still read the same parameters and report the same algorithm values.


How do I interpret SMART diagnostic utilities results? | Support Seagate US


Open administrative command prompt and type or copy and paste:

chkdsk /b /v W:

Run on all disk drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v/ E: etc.


C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)


Type: Y

Reboot as needed.


Running these chkdsk switches can take significant time so plan to run on the Windows drive overnight while sleeping.


https://www.tenforums.com/attachment...kfromevent.bat


Overnight run the Sea Tools for Windows long generic test:

SeaTools | Support Seagate US

How to use SeaTools for Windows | Support Seagate US

zbook said:

Health or SMART attempts to predict drive failure.

Drives will fail with SMART values > 90% when there are power outages or drops as these are sudden events.

If SMART are run after a drive has failed other drive tests it may still read the same parameters and report the same algorithm values.


How do I interpret SMART diagnostic utilities results? | Support Seagate US


Open administrative command prompt and type or copy and paste:

chkdsk /b /v W:

Run on all disk drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v/ E: etc.


C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)


Type: Y

Reboot as needed.


Running these chkdsk switches can take significant time so plan to run on the Windows drive overnight while sleeping.


https://www.tenforums.com/attachment...kfromevent.bat


Overnight run the Sea Tools for Windows long generic test:

SeaTools | Support Seagate US

How to use SeaTools for Windows | Support Seagate US

Tried out seatools short generic test on the drive in question and it seems to abort itself after 9% Wonder if it's running into the exact same damaged blocks hdtune is, i have no idea how that works.

A short or long generic test should not fail.

This is a failed drive.

Seek warranty replacement.

See if the long generic test fails too.
(make images for warranty replacement)

zbook said:

A short or long generic test should not fail.

This is a failed drive.

Seek warranty replacement.

See if the long generic test fails too.
(make images for warranty replacement)

Sounds like i'm replacing this drive then, pretty tragic seeing as how i've only used it for about 3 weeks.

Consider an Uninterruptible Power Supply UPS if power outages are frequent.

https://www.amazon.com/Computer-Unin...F8&node=764572

And consider making free backup images:

Backup and Restore with Macrium Reflect