Hardware

4939 readers

175 users here now

All things related to technology hardware, with a focus on computing hardware.

Rules (Click to Expand):

Follow the Lemmy.world Rules - https://mastodon.world/about
Be kind. No bullying, harassment, racism, sexism etc. against other users.
No Spam, illegal content, or NSFW content.
Please stay on topic, adjacent topics (e.g. software) are fine if they are strongly relevant to technology hardware. Another example would be business news for hardware-focused companies.
Please try and post original sources when possible (as opposed to summaries).
If posting an archived version of the article, please include a URL link to the original article in the body of the post.

Some other hardware communities across Lemmy:

Augmented Reality - !augmented_reality@lemmy.world
Gaming Laptops - !gaminglaptops@lemmy.world
Laptops - !laptops@lemmy.world
Linux Hardware - !linuxhardware@programming.dev
Mechanical Keyboards - !mechanical_keyboards@programming.dev
Monitors - !monitors@piefed.social
Raspberry Pi - !raspberry_pi@programming.dev
Retro Computing - !retrocomputing@lemmy.sdf.org
Virtual Reality - !virtualreality@lemmy.world

Icon by "icon lauk" under CC BY 3.0

founded 2 years ago

MODERATORS

Alphane_Moon@lemmy.world

Disk has read errors but SMART says PASSED (swg-empire.de)

submitted 2 months ago by bjoern_tantau@swg-empire.de to c/hardware@lemmy.world

3 comments fedilink hide all child comments

I've had multiple reads fail on a fairly new drive.

I did a smartctl -t long /dev/sdb but after checking back a few minutes later smartctl -a /dev/sdb showed that no tests were running and that the previous test had "the read element of the test failed".

I did smartctl -t offline /dev/sdb next and after that was done smartctl -x /dev/sdb showed about 1500 errors but it also reported SMART as PASSED.

Here is the output of smartctl -x /dev/sdb: https://pastebin.com/09rNZZfD

How should I interpret these results? Was my assumption that the long test was done wrong? Should I replace the drive? Or might something else be wrong, like the SATA connection?

top 3 comments

sorted by: hot top controversial new old

[–] Buffalox@lemmy.world 5 points 2 months ago

SMART sucks.

[–] orris@lemmy.world 4 points 2 months ago

Iirc Seagate use hex and modulus calculations, meaning the data looks scary but is totally fine. Do a google search for “interoperate seagate smart data” and there are a bunch if good resources and potentially apps that will help.

[–] BrightCandle@lemmy.world 3 points 2 months ago* (last edited 2 months ago)

The primary smart parameters are passing but its a bit concerning that such a young drive is showing read error count, that isn't a good sign even if its within the makers tolerance. What failed was just the long test you requested.

Its not uncommon for drives to fail in weird ways and the smart shows as fine. When you come across problems like a long test failing or occasional checksum problems on your raid array or a read error its a better indicator that something is wrong. Presumably something made you think you better run a long test, and then it failed. I would say Contact reseller for warranty replacement you have enough to go on showing there is something going wrong on the drive, long tests should not be failing on a healthy device.