maliciousonion to LinuxEnglish · 6 hours agoShould I be worried?imagemessage-square16fedilinkarrow-up131arrow-down13
arrow-up128arrow-down1imageShould I be worried?maliciousonion to LinuxEnglish · 6 hours agomessage-square16fedilink
minus-squareLemmchen@feddit.orglinkfedilinkEnglisharrow-up3·4 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?
minus-squareGolfNovemberUniformlinkfedilinkarrow-up1arrow-down1·edit-23 hours agoBecause 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.
minus-squaremalo@lemmy.worldlinkfedilinkarrow-up2·36 minutes agoI too love talking about things I know nothing about.
minus-squareTimeSquirrel@kbin.melroy.orglinkfedilinkarrow-up2·3 hours agoFirst 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-squareGolfNovemberUniformlinkfedilinkarrow-up1arrow-down2·3 hours agoIt doesn’t tell anything to me. The only disk related thing I know is fsck.
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 only features. I didn’t know it had anything to do with drives.
I too love talking about things I know nothing about.
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.