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?

  • Björn@swg-empire.deOP
    2·
    2 months ago

    I did have errors with another port on the same controller. My motherboard has two controllers, so after seeing the first errors on this disk I switched it to the other controller as well.

    But after I had gotten read errors after switching to the good controller I figured that something must be wrong with the drive.

    I think I will try hooking up the drive via USB. Thanks!

    • thelittleblackbird@lemmy.world
      3·
      2 months ago

      Then most likely is the driver / pin of some signals in the hdd. Smart here is totally useless and if the failure is confirmed you can only swap the disk because the repair is usually not worthy. The test with the USB connector is a good one, but keep in mind that USB interface tends to disconnect from time to time, so. If you see errors make sure that they are different / same errors.

      Good luck