Does this suggest a bad SATA cable?

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help
Post Reply
User avatar
eiver
Level 5
Level 5
Posts: 566
Joined: Fri Jan 23, 2009 5:51 am

Does this suggest a bad SATA cable?

Post by eiver »

Hi I recently started to have a weird error, which occurs randomly. Sometimes the system won't boot at all and simply displays "read error" on the screen and nothing more. Some other times it would drop to grub rescue console saying that it could not find a device to boot. Recently after leaving the machine unattended for some time I discovered that the whole screen was covered with some stack trace. The system was not responsive at that time so I cound not copy that. It started with some Python errors and at the bottom of the stack was a failed attempt to write to disk.

I suspected that my brand new Samsung 840 SSD might be faulty. I used smartctl to perform short and long tests. Both tests revealed no errors. SMART data showed no indication of any error either.

Then I discoved this in my /var/log/syslog:

Code: Select all

[    5.129959] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    5.130808] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    5.130814] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    5.130818] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    5.131075] ata1.00: ATA-9: Samsung SSD 840 PRO Series, DXM04B0Q, max UDMA/133
[    5.131080] ata1.00: 250069680 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    5.131467] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    5.131473] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    5.131476] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    5.131774] ata1.00: configured for UDMA/133
[    5.131992] scsi 0:0:0:0: Direct-Access     ATA      Samsung SSD 840  DXM0 PQ: 0 ANSI: 5
[    5.132106] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    5.132109] sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)
[    5.132153] sd 0:0:0:0: [sda] Write Protect is off
[    5.132157] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    5.132193] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.132672]  sda: sda1 sda2 < sda5 >
[    5.132997] sd 0:0:0:0: [sda] Attached SCSI disk
[    5.139775] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x280100 action 0x6 frozen
[    5.139780] ata1.00: irq_stat 0x08000000, interface fatal error
[    5.139783] ata1: SError: { UnrecovData 10B8B BadCRC }
[    5.139796] ata1.00: failed command: READ FPDMA QUEUED
[    5.139799] ata1.00: cmd 60/08:00:88:01:00/00:00:00:00:00/40 tag 0 ncq 4096 in
[    5.139799]          res 40/00:00:88:01:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    5.139801] ata1.00: status: { DRDY }
[    5.139804] ata1: hard resetting link
[    5.457471] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    5.458312] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    5.458318] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    5.458322] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    5.458967] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    5.458973] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    5.458977] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    5.459275] ata1.00: configured for UDMA/133
[    5.459286] ata1: EH complete
[    5.460467] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x280100 action 0x6 frozen
[    5.460471] ata1.00: irq_stat 0x08000000, interface fatal error
[    5.460474] ata1: SError: { UnrecovData 10B8B BadCRC }
[    5.460477] ata1.00: failed command: READ FPDMA QUEUED
[    5.460483] ata1.00: cmd 60/08:00:30:03:00/00:00:00:00:00/40 tag 0 ncq 4096 in
[    5.460483]          res 40/00:00:30:03:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    5.460486] ata1.00: status: { DRDY }
[    5.460499] ata1: hard resetting link
[    5.776995] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    5.777837] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    5.777843] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    5.777846] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    5.778499] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    5.778505] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    5.778508] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    5.778807] ata1.00: configured for UDMA/133
[    5.778818] ata1: EH complete
[    5.784413] ata1.00: exception Emask 0x10 SAct 0x2 SErr 0x280100 action 0x6 frozen
[    5.784416] ata1.00: irq_stat 0x08000000, interface fatal error
[    5.784419] ata1: SError: { UnrecovData 10B8B BadCRC }
[    5.784421] ata1.00: failed command: READ FPDMA QUEUED
[    5.784424] ata1.00: cmd 60/08:08:18:81:eb/00:00:0d:00:00/40 tag 1 ncq 4096 in
[    5.784424]          res 40/00:08:18:81:eb/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
[    5.784426] ata1.00: status: { DRDY }
[    5.784429] ata1: hard resetting link
[    6.100513] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    6.101354] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    6.101357] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    6.101359] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    6.102005] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    6.102011] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    6.102015] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    6.102312] ata1.00: configured for UDMA/133
[    6.102324] ata1: EH complete
[    8.269996] xor: automatically using best checksumming function:
[    8.309191]    avx       : 17157.000 MB/sec
[    8.309516] device-mapper: dm-raid45: initialized v0.2594b
[    8.326696] Btrfs loaded
[    8.333424] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[    8.333427] EXT4-fs (sda1): write access will be enabled during recovery
[    8.383839] EXT4-fs (sda1): recovery complete
[    8.385328] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    8.444364] ata1: limiting SATA link speed to 3.0 Gbps
[    8.444368] ata1.00: exception Emask 0x10 SAct 0x7ffffffc SErr 0x280100 action 0x6 frozen
[    8.444370] ata1.00: irq_stat 0x08000000, interface fatal error
[    8.444372] ata1: SError: { UnrecovData 10B8B BadCRC }
[    8.444374] ata1.00: failed command: READ FPDMA QUEUED
[    8.444378] ata1.00: cmd 60/08:10:20:09:80/00:00:01:00:00/40 tag 2 ncq 4096 in
[    8.444378]          res 40/00:e8:00:0a:80/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[    8.444380] ata1.00: status: { DRDY }
[    8.444381] ata1.00: failed command: READ FPDMA QUEUED
[    8.444384] ata1.00: cmd 60/08:18:30:09:80/00:00:01:00:00/40 tag 3 ncq 4096 in
[    8.444384]          res 40/00:e8:00:0a:80/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[    8.444386] ata1.00: status: { DRDY }
[    8.444387] ata1.00: failed command: READ FPDMA QUEUED
[    8.444390] ata1.00: cmd 60/08:20:38:09:80/00:00:01:00:00/40 tag 4 ncq 4096 in
[    8.444390]          res 40/00:e8:00:0a:80/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[    8.444391] ata1.00: status: { DRDY }
I googled a bit and it seems it might be a bad sata cable... Can anyone, who is more experienced than me, confirm this? Could it be not the cable but the mobo itself?

Orbmiser
Level 6
Level 6
Posts: 1497
Joined: Thu Oct 18, 2012 5:16 pm
Location: Portland,Oregon
Contact:

Re: Does this suggest a bad SATA cable?

Post by Orbmiser »

Next step would take a look inside and inspect the connectors on MB side and SSD side.
Unplug and reseat them. Or even swap the ends around for further isolating of problem.
Easiest way is to use another sata cable.

If you have multiple sata devices like DVD rom drive would swap with that one after trying suggested above first.

Also can be a power supply issue. Usually running sensors command in a terminal will give you P.S. voltages.
If you have LMsensors installed which mint has by default?
If not can use synaptic to install LMsensors.
.

Post Reply

Return to “Hardware Support”