• GolfNovemberUniform@lemmy.ml
    link
    fedilink
    arrow-up
    3
    arrow-down
    4
    ·
    edit-2
    2 months 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.

      • GolfNovemberUniform@lemmy.ml
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        edit-2
        2 months 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.

    • Lemmchen@feddit.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 months 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@lemmy.ml
        link
        fedilink
        arrow-up
        0
        arrow-down
        3
        ·
        edit-2
        2 months 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.

        • Lemmchen@feddit.org
          link
          fedilink
          arrow-up
          2
          ·
          2 months ago

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

        • TimeSquirrel@kbin.melroy.org
          link
          fedilink
          arrow-up
          2
          ·
          2 months 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.