smartctl shows error after Issues with HDD

Oddwierdo · 2024-03-11 15:15:12

Hi,

Today i switched my HDD it first went fine. But then i would get a lot of CRC errors. Arch wouldn't be able to mount the drive afterwards. So i opened the case and saw that some SATA Wire was bent really hard. I replaced it and the drive now shows up and seems to be okay.. Only the CRC errors seem to have increased.
Can someone tell me if this was "only" a faulty cable by checking my log?
https://pastebin.com/mJAic4eY

Also is there a way to get rid of that "log". Not speaking about the Smart Atributes but the actual "log" ?

seth · 2024-03-11 15:31:58

  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       0
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0

Looks uncritical, you can run badblocks (but in non-destructive mode it's gonna take a while) to search for bad … blocks.
But most likely this has just been the cable, notably if it was notably damaged.

Edit: you can also run a long self-test.

Edit #2:

Also is there a way to get rid of that "log". Not speaking about the Smart Atributes but the actual "log" ?

Why?
No.
Not w/o low-level disk tools and a decent chance to brick the drive and breaking one or two laws, I guess.
Why?

Last edited by seth (2024-03-11 15:36:10)

Oddwierdo · 2024-03-11 17:28:07

I just throught it is a bit annoying to see this error log whenever i check the drive (which i do regulary) but if i have read right only the last 5 errors will be shown so i guess that isn't an issue.

I think the Error was only from the bent cable. It's 39 on UDMA_CRC_Error_Count which was 0 before. So all errors seem to be related to this. The Cable was badly bent so i'm pretty sure it's the wire.
When this happend i also had this error in the journal

linux kernel: ata4.00: exception Emask 0x11 SAct 0x400 SErr 0x680100 action 0x6 frozen
linux kernel: ata4.00: irq_stat 0x48000008, interface fatal error
linux kernel: ata4: SError: { UnrecovData 10B8B BadCRC Handshk }
inux kernel: ata4.00: failed command: READ FPDMA QUEUED
linux kernel: ata4.00: cmd 60/08:50:18:00:00/00:00:00:00:00/40 tag 10 ncq dma 4096 in
res 43/84:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)

Could this also be from the Cable?

seth · 2024-03-11 17:31:25

Yes, is a bus error - very most likely the cable in this context.
(There's no certainty, the firmware could be fried, but if you had a lot of errors w/ the damaged cable an none since replacing the: it's been the cable)

Oddwierdo · 2024-03-11 17:59:24

That's good to know. No errors so far, can access the drive just fine. Hope it stays that way.

Arch Linux

#1 2024-03-11 15:15:12

smartctl shows error after Issues with HDD

#2 2024-03-11 15:31:58

Re: smartctl shows error after Issues with HDD

#3 2024-03-11 17:28:07

Re: smartctl shows error after Issues with HDD

#4 2024-03-11 17:31:25

Re: smartctl shows error after Issues with HDD

#5 2024-03-11 17:59:24

Re: smartctl shows error after Issues with HDD

Board footer