maliciousonion@lemmy.ml to Linux@lemmy.mlEnglish · 15 days agoShould I be worried?lemmy.mlimagemessage-square22fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1imageShould I be worried?lemmy.mlmaliciousonion@lemmy.ml to Linux@lemmy.mlEnglish · 15 days agomessage-square22fedilink
minus-squareGolfNovemberUniform@lemmy.mllinkfedilinkarrow-up0·edit-215 days 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-up0·15 days agoI too love talking about things I know nothing about.
minus-squareLemmchen@feddit.orglinkfedilinkarrow-up0·15 days agoI don’t get how you were able to arrive at that conclusion by looking at the console output, but sure, why not.
minus-squarePossibly linux@lemmy.ziplinkfedilinkEnglisharrow-up0·15 days agoIs this real? I feel like you are trolling
minus-squareTimeSquirrel@kbin.melroy.orglinkfedilinkarrow-up0·15 days 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-squareGolfNovemberUniform@lemmy.mllinkfedilinkarrow-up0·15 days 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 too love talking about things I know nothing about.
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
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.