You are not logged in.
- Topics: Active | Unanswered
#1 2025-02-02 16:45:09
- Sidekick
- Member
- Registered: 2024-06-23
- Posts: 36
[Solved] SSD failing? Locks up my system and errors in journalctl
Hi,
I've a small SSD that houses my docker containers and contains only one ext4 partition, sdc1. As of two days ago I'm unable to start docker, with these errors appearing in my journalctl
Feb 02 16:19:33 systemd[1]: Started containerd container runtime.
Feb 02 16:19:33 systemd[1]: Starting Docker Application Container Engine...
Feb 02 16:19:33 dockerd[4738]: time="2025-02-02T16:19:33.566644684+01:00" level=info msg="Starting up"
Feb 02 16:19:33 dockerd[4738]: time="2025-02-02T16:19:33.600617394+01:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
Feb 02 16:19:33 kernel: ata9.00: exception Emask 0x11 SAct 0x180000 SErr 0x6c0100 action 0x6 frozen
Feb 02 16:19:33 kernel: ata9.00: irq_stat 0x48000008, interface fatal error
Feb 02 16:19:33 kernel: ata9: SError: { UnrecovData CommWake 10B8B BadCRC Handshk }
Feb 02 16:19:33 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:33 kernel: ata9.00: cmd 60/c8:98:40:19:80/00:00:1c:00:00/40 tag 19 ncq dma 102400 in
res 41/84:01:09:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:33 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:33 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:33 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:33 kernel: ata9.00: cmd 60/08:a0:60:25:81/00:00:1c:00:00/40 tag 20 ncq dma 4096 in
res 41/84:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:33 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:33 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:33 kernel: ata9: hard resetting link
Feb 02 16:19:34 kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Feb 02 16:19:34 kernel: ata9.00: supports DRM functions and may not be fully accessible
Feb 02 16:19:34 kernel: ata9.00: supports DRM functions and may not be fully accessible
Feb 02 16:19:34 kernel: ata9.00: configured for UDMA/133
Feb 02 16:19:34 kernel: ahci 0000:16:00.0: port does not support device sleep
Feb 02 16:19:34 kernel: sd 8:0:0:0: [sdc] tag#19 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Feb 02 16:19:34 kernel: sd 8:0:0:0: [sdc] tag#19 Sense Key : Aborted Command [current]
Feb 02 16:19:34 kernel: sd 8:0:0:0: [sdc] tag#19 Add. Sense: Scsi parity error
Feb 02 16:19:34 kernel: sd 8:0:0:0: [sdc] tag#19 CDB: Read(10) 28 00 1c 80 19 40 00 00 c8 00
Feb 02 16:19:34 kernel: I/O error, dev sdc, sector 478157120 op 0x0:(READ) flags 0x80700 phys_seg 25 prio class 0
Feb 02 16:19:34 kernel: ata9: EH completeIt'll then set up network stuff but later on this appears:
Feb 02 16:19:35 kernel: ata9.00: exception Emask 0x11 SAct 0x70418002 SErr 0x6d0100 action 0x6 frozen
Feb 02 16:19:35 kernel: ata9.00: irq_stat 0x48000008, interface fatal error
Feb 02 16:19:35 kernel: ata9: SError: { UnrecovData PHYRdyChg CommWake 10B8B BadCRC Handshk }
Feb 02 16:19:35 kernel: ata9.00: failed command: WRITE FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 61/08:08:10:c8:d6/00:00:06:00:00/40 tag 1 ncq dma 4096 out
res 41/84:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 60/08:78:b0:1a:40/00:00:06:00:00/40 tag 15 ncq dma 4096 in
res 41/84:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 60/18:80:b0:02:dd/00:00:1a:00:00/40 tag 16 ncq dma 12288 in
res 41/84:00:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 60/00:b0:40:58:ed/01:00:17:00:00/40 tag 22 ncq dma 131072 in
res 41/84:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: WRITE FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 61/08:e0:68:63:da/00:00:0d:00:00/40 tag 28 ncq dma 4096 out
res 41/84:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: WRITE FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 61/08:e8:98:88:44/00:00:0e:00:00/40 tag 29 ncq dma 4096 out
res 41/84:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: WRITE FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 61/10:f0:b0:b4:11/00:00:03:00:00/40 tag 30 ncq dma 8192 out
res 41/84:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9: hard resetting link
Feb 02 16:19:35 kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Feb 02 16:19:35 kernel: ata9.00: supports DRM functions and may not be fully accessible
Feb 02 16:19:35 kernel: ata9.00: supports DRM functions and may not be fully accessible
Feb 02 16:19:35 kernel: ata9.00: configured for UDMA/133
Feb 02 16:19:35 kernel: ahci 0000:16:00.0: port does not support device sleep
Feb 02 16:19:35 kernel: sd 8:0:0:0: [sdc] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Feb 02 16:19:35 kernel: sd 8:0:0:0: [sdc] tag#16 Sense Key : Aborted Command [current]
Feb 02 16:19:35 kernel: sd 8:0:0:0: [sdc] tag#16 Add. Sense: Scsi parity error
Feb 02 16:19:35 kernel: sd 8:0:0:0: [sdc] tag#16 CDB: Read(10) 28 00 1a dd 02 b0 00 00 18 00
Feb 02 16:19:35 kernel: I/O error, dev sdc, sector 450691760 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
Feb 02 16:19:35 kernel: sd 8:0:0:0: [sdc] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Feb 02 16:19:35 kernel: sd 8:0:0:0: [sdc] tag#22 Sense Key : Aborted Command [current]
Feb 02 16:19:35 kernel: sd 8:0:0:0: [sdc] tag#22 Add. Sense: Scsi parity error
Feb 02 16:19:35 kernel: sd 8:0:0:0: [sdc] tag#22 CDB: Read(10) 28 00 17 ed 58 40 00 01 00 00
Feb 02 16:19:35 kernel: I/O error, dev sdc, sector 401430592 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 0
Feb 02 16:19:35 kernel: ata9: EH complete
Feb 02 16:19:35 kernel: ata9.00: exception Emask 0x11 SAct 0xe1c08 SErr 0x690100 action 0x6 frozen
Feb 02 16:19:35 kernel: ata9.00: irq_stat 0x48000008, interface fatal error
Feb 02 16:19:35 kernel: ata9: SError: { UnrecovData PHYRdyChg 10B8B BadCRC Handshk }
Feb 02 16:19:35 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 60/a0:18:00:63:47/00:00:06:00:00/40 tag 3 ncq dma 81920 in
res 41/84:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 60/08:50:c0:9e:41/00:00:06:00:00/40 tag 10 ncq dma 4096 in
res 41/84:01:06:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 60/00:58:40:59:ed/01:00:17:00:00/40 tag 11 ncq dma 131072 in
res 41/84:00:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 60/08:60:00:59:ed/00:00:17:00:00/40 tag 12 ncq dma 4096 in
res 41/84:01:09:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 60/08:88:c8:47:a7/00:00:16:00:00/40 tag 17 ncq dma 4096 in
res 41/84:01:06:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 60/00:90:70:ba:70/01:00:18:00:00/40 tag 18 ncq dma 131072 in
res 41/84:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:35 kernel: ata9.00: cmd 60/00:98:e0:bd:70/01:00:18:00:00/40 tag 19 ncq dma 131072 in
res 41/84:01:09:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:35 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:35 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:35 kernel: ata9: hard resetting link
Feb 02 16:19:36 kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Feb 02 16:19:36 kernel: ata9.00: supports DRM functions and may not be fully accessible
Feb 02 16:19:36 kernel: ata9.00: supports DRM functions and may not be fully accessible
Feb 02 16:19:36 kernel: ata9.00: configured for UDMA/133
Feb 02 16:19:36 kernel: ahci 0000:16:00.0: port does not support device sleep
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#3 Sense Key : Aborted Command [current]
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#3 Add. Sense: Scsi parity error
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#3 CDB: Read(10) 28 00 06 47 63 00 00 00 a0 00
Feb 02 16:19:36 kernel: I/O error, dev sdc, sector 105341696 op 0x0:(READ) flags 0x80700 phys_seg 16 prio class 0
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#11 Sense Key : Aborted Command [current]
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#11 Add. Sense: Scsi parity error
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#11 CDB: Read(10) 28 00 17 ed 59 40 00 01 00 00
Feb 02 16:19:36 kernel: I/O error, dev sdc, sector 401430848 op 0x0:(READ) flags 0x80700 phys_seg 28 prio class 0
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#18 Sense Key : Aborted Command [current]
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#18 Add. Sense: Scsi parity error
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#18 CDB: Read(10) 28 00 18 70 ba 70 00 01 00 00
Feb 02 16:19:36 kernel: I/O error, dev sdc, sector 410040944 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 0
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#19 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#19 Sense Key : Aborted Command [current]
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#19 Add. Sense: Scsi parity error
Feb 02 16:19:36 kernel: sd 8:0:0:0: [sdc] tag#19 CDB: Read(10) 28 00 18 70 bd e0 00 01 00 00
Feb 02 16:19:36 kernel: I/O error, dev sdc, sector 410041824 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 0
Feb 02 16:19:36 kernel: ata9: EH complete
Feb 02 16:19:36 kernel: ata9: limiting SATA link speed to 1.5 Gbps
Feb 02 16:19:36 kernel: ata9.00: exception Emask 0x11 SAct 0xc404004 SErr 0x690100 action 0x6 frozen
Feb 02 16:19:36 kernel: ata9.00: irq_stat 0x48000008, interface fatal error
Feb 02 16:19:36 kernel: ata9: SError: { UnrecovData PHYRdyChg 10B8B BadCRC Handshk }
Feb 02 16:19:36 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:36 kernel: ata9.00: cmd 60/08:10:d8:07:05/00:00:16:00:00/40 tag 2 ncq dma 4096 in
res 41/84:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:36 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:36 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:36 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:36 kernel: ata9.00: cmd 60/08:70:10:43:41/00:00:06:00:00/40 tag 14 ncq dma 4096 in
res 41/84:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:36 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:36 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:36 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:36 kernel: ata9.00: cmd 60/00:b0:50:6c:47/01:00:06:00:00/40 tag 22 ncq dma 131072 in
res 41/84:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:36 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:36 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:36 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:36 kernel: ata9.00: cmd 60/c8:d0:30:56:ed/00:00:17:00:00/40 tag 26 ncq dma 102400 in
res 41/84:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:36 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:36 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:36 kernel: ata9.00: failed command: READ FPDMA QUEUED
Feb 02 16:19:36 kernel: ata9.00: cmd 60/00:d8:d8:c2:70/01:00:18:00:00/40 tag 27 ncq dma 131072 in
res 41/84:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Feb 02 16:19:36 kernel: ata9.00: status: { DRDY ERR }
Feb 02 16:19:36 kernel: ata9.00: error: { ICRC ABRT }
Feb 02 16:19:36 kernel: ata9: hard resetting link
Feb 02 16:19:36 kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Feb 02 16:19:36 kernel: ata9.00: supports DRM functions and may not be fully accessible
Feb 02 16:19:36 kernel: ata9.00: Read log 0x13 page 0x00 failed, Emask 0x1
Feb 02 16:19:36 kernel: ata9.00: Read log 0x00 page 0x00 failed, Emask 0x40
Feb 02 16:19:36 kernel: ata9.00: Security Log not supported
Feb 02 16:19:36 kernel: ata9.00: failed to set xfermode (err_mask=0x40)It continues like this until I finally managed to restart the system.
fsck.ext4 -f /dev/sdc1reports no errors and a fragmentation of 0.7% and 35746825/61049344 blocks
smartctl -t short /dev/sdcand 3 minutes later
smartctl -x /dev/sdcreturns this:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.10-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Samsung based SSDs
Device Model: Samsung SSD 750 EVO 250GB
Serial Number: <redacted>
LU WWN Device Id: <redacted>
Firmware Version: MAT01B6Q
User Capacity: 250.059.350.016 bytes [250 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
TRIM Command: Available
Device is: In smartctl database 7.3/5528
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Feb 2 17:17:23 2025 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x53) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 133) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
9 Power_On_Hours -O--CK 094 094 000 - 27433
12 Power_Cycle_Count -O--CK 097 097 000 - 2943
177 Wear_Leveling_Count PO--C- 096 096 000 - 18
179 Used_Rsvd_Blk_Cnt_Tot PO--C- 100 100 010 - 0
181 Program_Fail_Cnt_Total -O--CK 100 100 010 - 0
182 Erase_Fail_Count_Total -O--CK 100 100 010 - 0
183 Runtime_Bad_Block PO--C- 100 099 010 - 0
187 Uncorrectable_Error_Cnt -O--CK 100 100 000 - 0
190 Airflow_Temperature_Cel -O--CK 072 040 000 - 28
195 ECC_Error_Rate -O-RC- 200 200 000 - 0
199 CRC_Error_Count -OSRCK 098 098 000 - 1375
235 POR_Recovery_Count -O--C- 099 099 000 - 253
241 Total_LBAs_Written -O--CK 099 099 000 - 5936234001
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 1 Comprehensive SMART error log
0x03 GPL R/O 1 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x13 GPL R/O 1 SATA NCQ Send and Receive log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 SL VS 16 Device vendor specific log
0xa5 SL VS 16 Device vendor specific log
0xce SL VS 16 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 27433 -
# 2 Extended offline Completed without error 00% 27398 -
# 3 Short offline Completed without error 00% 27373 -
# 4 Short offline Completed without error 00% 27358 -
# 5 Short offline Completed without error 00% 27341 -
# 6 Extended offline Completed without error 00% 27294 -
# 7 Short offline Completed without error 00% 27271 -
# 8 Short offline Completed without error 00% 27253 -
# 9 Short offline Completed without error 00% 27239 -
#10 Short offline Completed without error 00% 27223 -
#11 Extended offline Completed without error 00% 27179 -
#12 Short offline Completed without error 00% 27157 -
#13 Short offline Completed without error 00% 27142 -
#14 Short offline Completed without error 00% 27125 -
#15 Short offline Completed without error 00% 27106 -
#16 Extended offline Completed without error 00% 27064 -
#17 Short offline Completed without error 00% 27038 -
#18 Short offline Completed without error 00% 27023 -
#19 Short offline Completed without error 00% 27010 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
255 0 65535 Read_scanning was never started
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
SCT Status Version: 3
SCT Version (vendor specific): 256 (0x0100)
Device State: Active (0)
Current Temperature: 29 Celsius
Power Cycle Min/Max Temperature: 23/40 Celsius
Lifetime Min/Max Temperature: 0/70 Celsius
Under/Over Temperature Limit Count: 4294967295/4294901760
SMART Status: 0xffff (Reserved)
SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 10 minutes
Min/Max recommended Temperature: 0/70 Celsius
Min/Max Temperature Limit: 0/70 Celsius
Temperature History Size (Index): 128 (8)
Index Estimated Time Temperature Celsius
9 2025-02-01 20:00 ? -
... ..(117 skipped). .. -
127 2025-02-02 15:40 ? -
0 2025-02-02 15:50 40 *********************
1 2025-02-02 16:00 23 ****
2 2025-02-02 16:10 26 *******
3 2025-02-02 16:20 29 **********
4 2025-02-02 16:30 28 *********
... ..( 2 skipped). .. *********
7 2025-02-02 17:00 28 *********
8 2025-02-02 17:10 29 **********
SCT Error Recovery Control:
Read: Disabled
Write: Disabled
Device Statistics (GP/SMART Log 0x04) not supported
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 236 Command failed due to ICRC error
0x0002 2 210 R_ERR response for data FIS
0x0003 2 210 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0005 2 10 R_ERR response for non-data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 10 R_ERR response for host-to-device non-data FIS
0x0008 2 6 Device-to-host non-data FIS retries
0x0009 2 301 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 241 Device-to-host register FISes sent due to a COMRESET
0x000b 2 0 CRC errors within host-to-device FIS
0x000d 2 0 Non-CRC errors within host-to-device FIS
0x000f 2 0 R_ERR response for host-to-device data FIS, CRC
0x0010 2 0 R_ERR response for host-to-device data FIS, non-CRC
0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC
0x0013 2 0 R_ERR response for host-to-device non-data FIS, non-CRCWhat does this mean? Is the drive failing?
Last edited by Sidekick (2025-02-03 01:11:50)
Offline
#2 2025-02-02 18:17:25
- jonno2002
- Member
- Registered: 2016-11-21
- Posts: 765
Re: [Solved] SSD failing? Locks up my system and errors in journalctl
well firstly backup the data on that drive reguardless if you havent already !
that smartctl report looks more like a bad sata cable/port than a dead drive, all the self tests have passed without error, i would recommend a new sata cable and also run a memtest
Offline
#3 2025-02-02 21:04:20
- seth
- Member
- Registered: 2012-09-03
- Posts: 61,632
Re: [Solved] SSD failing? Locks up my system and errors in journalctl
Since it's on comm_wake, see https://wiki.archlinux.org/title/Power_ … Management and try to use medium_power instead of med_power_with_dipm (which a bunch of drives got afforded overoptimistically)
If that doesn't help try to add "pcie_aspm=off" to the https://wiki.archlinux.org/title/Kernel_parameters but as jonno2002 pointed out: looking at the cables (also the power one!) is always a good idea 
Online
#4 2025-02-02 21:21:25
- cryptearth
- Member
- Registered: 2024-02-03
- Posts: 1,337
Re: [Solved] SSD failing? Locks up my system and errors in journalctl
jonno2002 wrote:
well firstly backup the data on that drive reguardless if you havent already !
that smartctl report looks more like a bad sata cable/port than a dead drive, all the self tests have passed without error, i would recommend a new sata cable and also run a memtest
although it is a possibility - sithout OP physically touching the cable or moving the pc around (or have an earthquake shake it) I doubt a sata data cable can fail in such a way - rather it would fail completely
if it's anything in the data path any solder connection is way more likely due to thermal cycle having way greater effects than on a cable (and as sata data cables usually fully pitted at thier connections its unlikely the inner solder connections within the plastic would fail in such a way)
anyway - aside from the data path the power supply could be another option all the way from the psu to the drife itself
if possible the first idea I would try is a different system - if the error moves along with the drive its the drive itself - if the issue vanishes it could be anything of the system from power to motherboard to failing chipset or even cpu
Offline
#5 2025-02-03 01:10:33
- Sidekick
- Member
- Registered: 2024-06-23
- Posts: 36
Re: [Solved] SSD failing? Locks up my system and errors in journalctl
Used a new cable and yep, works fine now. Guess the cable just reached it's end of life. Thanks for the help @jonno2002
@seth I guess that means I don't have to play around with the power modes?
@cryptearth looking a bit closer at the cable it had a double-bend before going into a gromit. I think what happened was that the cable was a bit too long and when I closed the case, the pressure forced the cable into that form. Add to that the constant changes in temperature and you get a bad cable over, apparently, the course of a couple months.
Offline
#6 2025-02-03 05:16:02
- cryptearth
- Member
- Registered: 2024-02-03
- Posts: 1,337
Re: [Solved] SSD failing? Locks up my system and errors in journalctl
ok - have to admit: not expected that
Offline
#7 2025-02-03 07:46:57
- seth
- Member
- Registered: 2012-09-03
- Posts: 61,632
Re: [Solved] SSD failing? Locks up my system and errors in journalctl
I guess that means I don't have to play around with the power modes?
No 
Cables remain the undefeated champion to ruin your day. 
Online