• GolfNovemberUniform
    link
    fedilink
    arrow-up
    5
    arrow-down
    14
    ·
    edit-2
    1 month ago

    I have no idea what all of that is but it looks like something I would worry about. I’d say it’s time for a clean install and thinking of a new root password.

    • Lemmchen@feddit.org
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 month ago

      I’d say it’s time for a clean install and thinking of a new root password.

      Huh? What has that to do with a possibly failing drive?

      • GolfNovemberUniform
        link
        fedilink
        arrow-up
        1
        arrow-down
        7
        ·
        edit-2
        1 month ago

        Because to me it looked like someone or something was trying to get access to root only features. I didn’t know it had anything to do with drives.

        • TimeSquirrel@kbin.melroy.org
          link
          fedilink
          arrow-up
          5
          ·
          1 month ago

          First clue was the “ata” prefacing every error message. Then various things like “SCSI parity error” which indicates data corruption during transmission. “Parity” data is used to double check the integrity of the actual data.

        • Lemmchen@feddit.org
          link
          fedilink
          arrow-up
          4
          ·
          1 month ago

          I don’t get how you were able to arrive at that conclusion by looking at the console output, but sure, why not.

    • maliciousonionOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 month ago

      It’s the same error, no matter how many times I reinstall. I assume it’s a hardware issue

      • GolfNovemberUniform
        link
        fedilink
        arrow-up
        3
        arrow-down
        8
        ·
        edit-2
        1 month ago

        Can be a distro/setup issue as well. Also you should’ve added this info to your post. It’s very useful for troubleshooting the issue.