• @[email protected]
    link
    fedilink
    -4
    edit-2
    15 hours 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.

    • @[email protected]
      link
      fedilink
      English
      313 hours 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?

      • @[email protected]
        link
        fedilink
        -2
        edit-2
        12 hours 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.

        • @[email protected]
          link
          fedilink
          28 hours ago

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

        • @malo
          link
          410 hours ago

          I too love talking about things I know nothing about.

        • TimeSquirrel
          link
          fedilink
          212 hours 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.

    • @[email protected]OP
      link
      fedilink
      English
      415 hours ago

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

      • @[email protected]
        link
        fedilink
        -3
        edit-2
        15 hours 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.