maliciousonion@lemmy.ml to Linux@lemmy.mlEnglish · 9 个月前Should I be worried?lemmy.mlimagemessage-square27fedilinkarrow-up166arrow-down14
arrow-up162arrow-down1imageShould I be worried?lemmy.mlmaliciousonion@lemmy.ml to Linux@lemmy.mlEnglish · 9 个月前message-square27fedilink
minus-squareLemmchen@feddit.orglinkfedilinkEnglisharrow-up7·9 个月前 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?
minus-squareGolfNovemberUniform@lemmy.mllinkfedilinkarrow-up1arrow-down7·edit-29 个月前Because to me it looked like someone or something was trying to get access to root features. I didn’t know it had anything to do with drives.
minus-squaremalo@lemmy.worldlinkfedilinkarrow-up10·9 个月前I too love talking about things I know nothing about.
minus-squarePossibly linux@lemmy.ziplinkfedilinkEnglisharrow-up7·9 个月前Is this real? I feel like you are trolling
minus-squareGolfNovemberUniform@lemmy.mllinkfedilinkarrow-up1arrow-down1·9 个月前I am not trolling. I’m just very bad at finding information online.
minus-squareTimeSquirrel@kbin.melroy.orglinkfedilinkarrow-up5·9 个月前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.
minus-squareGolfNovemberUniform@lemmy.mllinkfedilinkarrow-up1arrow-down6·9 个月前It doesn’t tell anything to me. The only disk related thing I know is fsck.
minus-squareLemmchen@feddit.orglinkfedilinkarrow-up4·9 个月前I don’t get how you were able to arrive at that conclusion by looking at the console output, but sure, why not.
Huh? What has that to do with a possibly failing drive?
Because to me it looked like someone or something was trying to get access to root features. I didn’t know it had anything to do with drives.
I too love talking about things I know nothing about.
Is this real? I feel like you are trolling
I am not trolling. I’m just very bad at finding information online.
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.
It doesn’t tell anything to me. The only disk related thing I know is fsck.
I don’t get how you were able to arrive at that conclusion by looking at the console output, but sure, why not.