Question How to Clear Old HDD Notice

[accesscpu_]

I noticed in SeaTools that my Seagate Iron Wolf gives me a notice stating that "SMART over-all health passed, but at least one of the SMART attributes breached the threshold in the past."

I checked the log, and the error is coming from the "Air Flow Temperature - Failed in the Past."

So I tried moving that drive from the slot underneath in my case to the open-air spot up front by the fans, to make sure it's getting more air-flow. But the notice still persists in SeaTools. I'm not even sure if this happened recently, or on my old system (where this drive originally was housed) and it just saved it from the past.

Is there a way to clear/reseat this attribute, so I can get an updated reading to see if the air flow is good now?

 

[USAFRet]

Is there a way to clear/reseat this attribute, so I can get an updated reading to see if the air flow is good now?

No.
Erasing SMART data is not a user thing.

 

[accesscpu_]

No.
Erasing SMART data is not a user thing.

The drive has a yellow exclamation/error notice on it, and I get this pop up notification about the old issue every time I load the program. Now that I've corrected the air-flow issue, is that not something I can correct (to see if it's now getting better air flow)? Seems like it should refresh somehow. I just need to force it to take a new reading.

 

[accesscpu_]

Also, I should mention that I have ran the Self Test, Short Generic and 2 Minute Generic Test on the drive, and all have passed.

 

[SkyNetRising]

Is there a way to clear/reseat this attribute, so I can get an updated reading to see if the air flow is good now?

No. You can't. It's by design.

The drive has a yellow exclamation/error notice on it, and I get this pop up notification about the old issue every time I load the program.

What program is that?
May be use a different program, that doesn't do that.

Anyway, if the problem bothers you so much and you absolutely have to use this particular program,
then get a new HDD.

 

[accesscpu_]

No. You can't. It's by design.

What program is that?
May be use a different program, that doesn't do that.

Anyway, if the problem bothers you so much and you absolutely have to use this particular program,
then get a new HDD.

It's SeaTools. I wouldn't say it bothers me. Just trying to make sure I'm not on the door step of a major hard drive problem (since this one if fairly new), or if this is just a false alarm over a non-issue error that is now "baked into the cake." I'm gonna run some more scans and report back.

 

[USAFRet]

It's SeaTools. I wouldn't say it bothers me. Just trying to make sure I'm not on the door step of a major hard drive problem (since this one if fairly new), or if this is just a false alarm over a non-issue error that is now "baked into the cake." I'm gonna run some more scans and report back.

Possibly it will go off in a few On/Off cycles and readings.

But it is nothing you can influence via DIY.

 

[accesscpu_]

Someone else explained this (and the reason it can't be cleared) is like a patients' medical history at the doctor. Something you wanna know about but not forget entirely. So that's a great way of explaining it.

I would say that I hope SMART data like this gets a little "smarter" in the future. I mean, if they had just time stamped the error, it would have cleared up so much confusion very easily. Something a doctor would ask their patient like "I see you had an isolated incident once 10 years ago and no knew instances...this is no real cause for concern."

Thanks for all the helpful info all!

 

[USAFRet]

Someone else explained this (and the reason it can't be cleared) is like a patients' medical history at the doctor. Something you wanna know about but not forget entirely. So that's a great way of explaining it.

Also, if it was easy to clear...Someone could have a faulty/failing drive, clear those values, and advertise it for sale as "Perfect! No faults!"

 

[accesscpu_]

Follow up:

So I just ran chkdsk on that drive (from an elevated command prompt), by specifying the drive letter. I didn't run chkdsk /r yet, because I read that files could be lost, if they are two close to bad sectors (and I haven't had the chance to back them up yet). But just the read-only chkdsk seems to have returned a positive result. Can anyone confirm these results? And I assume running chkdsk /r is not needed now?

Microsoft Windows [Version 10.0.22631.4037]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>chkdsk G:
The type of the file system is NTFS.
Volume label is Backupdrive.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
22528 file records processed.
File verification completed.
Phase duration (File record verification): 2.76 seconds.
4371 large file records processed.
Phase duration (Orphan file record recovery): 1.97 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.19 milliseconds.

Stage 2: Examining file name linkage ...
5 reparse records processed.
26724 index entries processed.
Index verification completed.
Phase duration (Index verification): 2.16 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 1.78 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.18 milliseconds.
5 reparse records processed.
Phase duration (Reparse point and Object ID verification): 0.56 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 28.73 milliseconds.
2099 data files processed.
Phase duration (Data attribute verification): 0.37 milliseconds.
CHKDSK is verifying Usn Journal...
35806344 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 448.25 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

15259645 MB total disk space.
14726274 MB in 16005 files.
5832 KB in 2100 indexes.
0 KB in bad sectors.
600727 KB in use by the system.
65536 KB occupied by the log file.
545565608 KB available on disk.

4096 bytes in each allocation unit.
3906469375 total allocation units on disk.
136391402 allocation units available on disk.
Total duration: 5.41 seconds (5415 ms).

 

[SkyNetRising]

Can anyone confirm these results? And I assume running chkdsk /r is not needed now?

High temperature warning has nothing to do with chkdsk.
Running chkdsk will not impact SMART logs data.

Chkdks found no file system corruption. So there's no file system corruption to fix.

 

[accesscpu_]

High temperature warning has nothing to do with chkdsk.
Running chkdsk will not impact SMART logs data.

Chkdks found no file system corruption. So there's no file system corruption to fix.

Yup, I was just going the extra mile to verify the integrity of the drive. Looks like I'm all good. Thanks!