this post was submitted on 18 Oct 2025
8 points (100.0% liked)

datahoarder

8900 readers
1 users here now

Who are we?

We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.

We are one. We are legion. And we're trying really hard not to forget.

-- 5-4-3-2-1-bang from this thread

founded 5 years ago
MODERATORS
 

cross-posted from: https://swg-empire.de/post/4845931

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?

you are viewing a single comment's thread
view the rest of the comments
[–] tomten@lemmy.world 4 points 1 week ago

Yeah that drive is dying, replace it.