maliciousonion@lemmy.ml to Linux@lemmy.mlEnglish · 4 months agoShould I be worried?lemmy.mlimagemessage-square32fedilinkarrow-up165arrow-down14
arrow-up161arrow-down1imageShould I be worried?lemmy.mlmaliciousonion@lemmy.ml to Linux@lemmy.mlEnglish · 4 months agomessage-square32fedilink
minus-squareGolfNovemberUniform@lemmy.mllinkfedilinkarrow-up1arrow-down7·edit-23 months agodeleted by creator
minus-squaremalo@lemmy.worldlinkfedilinkarrow-up10·4 months agoI too love talking about things I know nothing about.
minus-squarePossibly linux@lemmy.ziplinkfedilinkEnglisharrow-up7·4 months agoIs this real? I feel like you are trolling
minus-squareGolfNovemberUniform@lemmy.mllinkfedilinkarrow-up1arrow-down1·edit-23 months agodeleted by creator
minus-squareTimeSquirrel@kbin.melroy.orglinkfedilinkarrow-up5·4 months 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-up1arrow-down7·edit-23 months agodeleted by creator
minus-squareLemmchen@feddit.orglinkfedilinkarrow-up4·4 months agoI don’t get how you were able to arrive at that conclusion by looking at the console output, but sure, why not.
deleted by creator
I too love talking about things I know nothing about.
Is this real? I feel like you are trolling
deleted by creator
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.
deleted by creator
I don’t get how you were able to arrive at that conclusion by looking at the console output, but sure, why not.