Question

23

Are these SATA errors dangerous?

rated 0 times [ 23] [ 0] / answers: 1 / hits: 157259 / 2 Years ago, wed, november 9, 2022, 2:22:12

I'm getting these errors ramdomly, and I don't know if its normal or not.

[39441.061856] ata3.00: failed to read SCR 1 (Emask=0x40)

[39441.061866] ata3.01: failed to read SCR 1 (Emask=0x40)

[39441.061892] ata3.15: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen

[39441.061897] ata3.15: irq_stat 0x08000000, interface fatal error

[39441.061904] ata3.15: SError: { UnrecovData 10B8B BadCRC }

[39441.061910] ata3.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

[39441.061917] ata3.01: exception Emask 0x100 SAct 0xe SErr 0x0 action 0x6 frozen

[39441.061923] ata3.01: failed command: READ FPDMA QUEUED

[39441.061933] ata3.01: cmd 60/a8:08:b0:48:62/00:00:00:00:00/40 tag 1 ncq 86016 in

[39441.061940] ata3.01: status: { DRDY }

[39441.061944] ata3.01: failed command: READ FPDMA QUEUED

[39441.061953] ata3.01: cmd 60/a8:10:b0:49:62/00:00:00:00:00/40 tag 2 ncq 86016 in

[39441.061959] ata3.01: status: { DRDY }

[39441.061963] ata3.01: failed command: READ FPDMA QUEUED

[39441.061972] ata3.01: cmd 60/58:18:58:4a:62/00:00:00:00:00/40 tag 3 ncq 45056 in

[39441.061978] ata3.01: status: { DRDY }

[39441.061987] ata3.15: hard resetting link

[39441.608302] ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

[39441.609090] ata3.00: hard resetting link

[39441.929246] ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[39441.929333] ata3.01: hard resetting link

[39442.249184] ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[39442.263242] ata3.00: configured for UDMA/133

[39442.277570] ata3.01: configured for UDMA/133

[39442.277725] ata3: EH complete

I'm also pasting smartctl -a for sda, sdb and sdc.

Thanks in advance for your help.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

defendle

Add To Favorites

Follow

Total Points: 219

Total Questions: 131

Total Answers: 112

Location: Finland

Member since Sat, Nov 6, 2021

3 Years ago

defendle questions

1 Low Disk Space on Filesystem.root Ubuntu

Mon, May 10, 21, 03:46, 3 Years ago

1 How to remap escape, tilde, and quotes on 21.10 with xkb options

Tue, Feb 21, 23, 09:23, 1 Year ago

1 Unable to launch browser from shell - it opens VSCode instead

Mon, Apr 18, 22, 04:56, 2 Years ago

1 How to Solve Increasing Size of MySQL Binlog Files Problem?

Tue, Jun 8, 21, 11:33, 3 Years ago

1 Where are GTK_IM_MODULE and GTK_MODULES set?

Mon, Dec 5, 22, 07:16, 1 Year ago

View All

answered 2 Years ago eballxeye · Accepted Answer

While I essentially agree with Geppettvs D'Constanzo's answer, I would suggest that some of the first things you might also try are

Checking that your SATA cable is securely attached and plugged into the sockets on the motherboard and hard drive.

Replacing your SATA cable. SATA cables are (relatively) inexpensive and you do sometimes get a "bad" one. Often simply replacing the cable is the easiest way to diagnose and solve a problem like this.

(Although it is somewhat unexpected that two cables would both be bad at the same time. Still, it's an easy thing to check so in my opinion probably worth doing.)

I just saw you pastbins containing the SMART data for your drives. Notice the unexpectedly large number of CRC errors for drives sdb and sdc. I suggest you start by checking the cables and connections for those drives.

junior@mediacenter:/$ sudo  smartctl -a /dev/sda

...

Model Family:     SAMSUNG SpinPoint M7E (AFT)

Device Model:     SAMSUNG HM321HI

...

199 UDMA_CRC_Error_Count    0x0036   200   200   000   Old_age  Always -    0



junior@mediacenter:/$ sudo  smartctl -a /dev/sdb

...

Model Family:     SAMSUNG SpinPoint F4 EG (AFT)

Device Model:     SAMSUNG HD204UI

...

199 UDMA_CRC_Error_Count    0x0036   100   100   000   Old_age  Always  -  57



junior@mediacenter:/$ sudo  smartctl -a /dev/sdc

...

Model Family:     SAMSUNG SpinPoint F4 EG (AFT)

Device Model:     SAMSUNG HD204UI

...

199 UDMA_CRC_Error_Count    0x0036   100   100   000   Old_age  Always  - 398

OK. So not a latpop then. ;-)

Of course, if this is happening on a laptop than none of the above apply and I'm not sure what advice to offer. Maybe remove and re-install the hard drive? Perhaps it just needs to be re-seated in its socket to improve the connection?

sbd and sdc are connected on the same external e-sata cable (Thermaltake Duo HDD Dock). i'll replace my e-sata cable.

It could be due to a faulty or low quality cable. It could also be that the cable is somehow moved, bumped, or otherwise jostled while the drive is being used.