@[email protected] to [email protected]English • 15 hours agoShould I be worried?lemmy.mlimagemessage-square20fedilinkarrow-up141arrow-down14
arrow-up137arrow-down1imageShould I be worried?lemmy.ml@[email protected] to [email protected]English • 15 hours agomessage-square20fedilink
minus-square@[email protected]linkfedilink-2•edit-212 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-square@[email protected]linkfedilink2•8 hours agoI don’t get how you were able to arrive at that conclusion by looking at the console output, but sure, why not.
minus-square@[email protected]linkfedilink1•7 hours agoI am not trolling. I’m just very bad at finding information online.
minus-squareTimeSquirrellinkfedilink2•12 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-square@[email protected]linkfedilink-2•12 hours agoIt doesn’t tell anything to me. The only disk related thing I know is fsck.
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 don’t get how you were able to arrive at that conclusion by looking at the console output, but sure, why not.
Is this real? I feel like you are trolling
I am not trolling. I’m just very bad at finding information online.
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.