@[email protected] to [email protected]English • 1 month agoShould I be worried?lemmy.mlimagemessage-square27fedilinkarrow-up156arrow-down15
arrow-up151arrow-down1imageShould I be worried?lemmy.ml@[email protected] to [email protected]English • 1 month agomessage-square27fedilink
minus-square@[email protected]linkfedilink-6•edit-21 month 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]linkfedilink0•1 month agoI am not trolling. I’m just very bad at finding information online.
minus-squareTimeSquirrellinkfedilink5•1 month 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-6•1 month agoIt doesn’t tell anything to me. The only disk related thing I know is fsck.
minus-square@[email protected]linkfedilink4•1 month agoI don’t get how you were able to arrive at that conclusion by looking at the console output, but sure, why not.
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.
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.