How does this autistic program work?

How does this autistic program work?

The columns don't make sense. For instance, if a "treshhold" of something is 0, and all current values are above 0 by a bunch (100+) then it should mean your HDD is fucked. This makes no sense.

Attached: Portable-CrystalDiskInfo_1.png (688x772, 97K)

Convert to decimal you retard.

0 is 0 in BIN, OCT, DEC, DEX, frankly every single number system.

Is this a joke

>Current 117, Worst 99, Threshold 6
>the number's higher than the threshold, how isn't it fucked!?

Yes, that's what im saying. If more than 6 errors should be a warning and it was 117, how is that reasonable? Also how can be current 117 and worst 99? this is nonsense.

damn

Attached: ssd.png (916x706, 123K)

If Worst is lower than Current, then clearly lower is worse.

look at the temperature column

shits retarded

reminder that S.M.A.R.T. is pure placebo with zero predictive value.

Threshold current/worst values go DOWN, not up, in SMART.

Attached: Untitled.png (1204x780, 137K)

>implying smartctl -x /dev/sda isn't useful

it's made by a ching chong
what did you expect?

Attached: 1527693398103.jpg (1508x1920, 485K)

I dont get it

It all goes to 0?

Yes. The threshold values are only used for support purposes, e.g.: if value dips below threshold, then you have a right to warranty replacement. Most manufacturers replace units even if that's not the case though.

My previous screenshot is fucked up for some reason, the threshold values are missing.
Also,
>WD Red
>not trash
Pick one.

Attached: Untitled.png (1204x780, 125K)

>then you have a right to warranty replacement.
*even if it works properly.

cant be worse than my shitty seagates

>cant be worse
This is the drive dropping out on a sequential write.
Here's a bit of the smartctl output:
Error 7582 [21] occurred at disk power-on lifetime: 12591 hours (524 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 00 00 00 00 01 5d 59 00 40 00 Error: IDNF at LBA = 0x015d5900 = 22894848

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 01 00 00 10 00 00 01 5d 59 00 40 00 00:01:53.441 WRITE FPDMA QUEUED
61 01 00 00 08 00 00 01 5d 58 00 40 00 00:01:53.441 WRITE FPDMA QUEUED
61 01 00 00 f8 00 00 01 5d 57 00 40 00 00:01:53.440 WRITE FPDMA QUEUED
61 01 00 00 f0 00 00 01 5d 56 00 40 00 00:01:53.439 WRITE FPDMA QUEUED
61 01 00 00 e8 00 00 01 5d 55 00 40 00 00:01:53.438 WRITE FPDMA QUEUED

Attached: Untitled.png (923x686, 65K)

500gb, spotted the HDlet.

Assuming you are not trolling, how would a deteriorating hard drive have fail counts and error rates that decrease?

Some values fluctuate (that's why there's a "worst" column). Raw Read Error Rate is completely nonsensical on Seagate drives, for example, whereas on Western Digital drives it's a bad sign if it's anything other than zero.

For error counts, I guess it was a bug in HD Sentinel. Note how one screenshot had all the thresholds at 0. Also, don't forget that SMART is a drive feature that is backed by the drive's spare storage space (e.g. the internal error logs). If the drive is malfunctioning, SMART may as well.

I honestly don't know what the fuck happened with the Reallocation Event Count, I noticed it go down by one too. Probably some incongruity when the drive dropped out and restarted.

I dread this RMA, WD are utter fucking jews. Last I want is a refurb that lasts 6 months then dies out of warranty.