Timeouts of about 1 minute with new SSD BX500, HD led on, kernel > 4.14

I am testing a system with various distributions. It seems that kernels later then 4.14 are causing timeouts specifically in combination with my new Crucial SSD BX500 (480 GB). This already happens during installation, especially when installing Grub. Later it happens incidentally at random and becomes less frequent over time. The internal SATA is set to AHCI.

Note that there is no trouble with kernel 4.14 or with other HDD or SSD drives. Also none of these symptoms with Windows 10 or for example KDE neon.

Any ideas what the reason could be and why this happens specifically with newer kernels, v4.19 and higher versions and only when using my Crucial SSD BX500. Thanks in advance.

> sudo dmesg
>  addr=? terminal=? res=success'
> [   33.768623] audit: type=1334 audit(1626716808.266:64): prog-id=15 op=UNLOAD
> [   33.768629] audit: type=1334 audit(1626716808.266:65): prog-id=14 op=UNLOAD
> [   33.768632] audit: type=1334 audit(1626716808.266:66): prog-id=13 op=UNLOAD
> [  333.618949] ata1.00: exception Emask 0x10 SAct 0x20000000 SErr 0x40d0002 action 0xe frozen
> [  333.618952] ata1.00: irq_stat 0x00000040, connection status changed
> [  333.618955] ata1: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch }
> [  333.618957] ata1.00: failed command: WRITE FPDMA QUEUED
> [  333.618961] ata1.00: cmd 61/18:e8:e1:bc:80/00:00:21:00:00/40 tag 29 ncq dma 12288 out
>                         res 40/00:6c:b1:c2:40/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
> [  333.618963] ata1.00: status: { DRDY }
> [  333.618966] ata1: hard resetting link
> [  334.498924] ata1: softreset failed (device not ready)
> [  334.498930] ata1: applying PMP SRST workaround and retrying
> [  334.655622] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [  334.659182] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
> [  334.664490] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
> [  334.664494] ata1.00: configured for UDMA/133
> [  334.675188] ata1: EH complete
> [  549.382242] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0xc0002 action 0x6 frozen
> [  549.382246] ata1: SError: { RecovComm CommWake 10B8B }
> [  549.382248] ata1.00: failed command: FLUSH CACHE EXT
> [  549.382252] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 14
>                         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> [  549.382253] ata1.00: status: { DRDY }
> [  549.382256] ata1: hard resetting link
> [  549.852224] ata1: softreset failed (device not ready)
> [  549.852228] ata1: applying PMP SRST workaround and retrying
> [  550.008899] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [  550.012459] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
> [  550.017761] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
> [  550.017764] ata1.00: configured for UDMA/133
> [  550.017766] ata1.00: retrying FLUSH 0xea Emask 0x4
> [  550.029043] ata1: EH complete
> [  576.353275] audit: type=1100 audit(1626717350.849:67): pid=2541 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:authentication grantors=? acct="gsm" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=failed'
> [  581.785066] audit: type=1100 audit(1626717356.279:68): pid=2541 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="gsm" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
> [  581.785299] audit: type=1101 audit(1626717356.279:69): pid=2541 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="gsm" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
> [  581.785578] audit: type=1110 audit(1626717356.283:70): pid=2541 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
> [  581.786404] audit: type=1105 audit(1626717356.283:71): pid=2541 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'

My system

> inxi -F
> System:    Host: gsm-man-kde Kernel: 5.10.49-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.22.3 Distro: Manjaro Linux
> Machine:   Type: Desktop System: Gigabyte product: GA-MA770-DS3 v: N/A serial: <superuser required>
>            Mobo: Gigabyte model: GA-MA770-DS3 serial: <superuser required> BIOS: Award v: F7 date: 01/05/2009
> CPU:       Info: Quad Core model: AMD Phenom II X4 920 bits: 64 type: MCP cache: L2: 2 MiB
>            Speed: 2813 MHz min/max: N/A Core speeds (MHz): 1: 2813 2: 2813 3: 2813 4: 2813
> Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] driver: radeon v: kernel
>            Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon unloaded: modesetting resolution: 1920x1080~60Hz
>            OpenGL: renderer: AMD PITCAIRN (DRM 2.50.0 5.10.49-1-MANJARO LLVM 12.0.0) v: 4.5 Mesa 21.1.4
> Audio:     Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia driver: snd_hda_intel
>            Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] driver: snd_hda_intel
>            Sound Server-1: ALSA v: k5.10.49-1-MANJARO running: yes
>            Sound Server-2: PulseAudio v: 14.2 running: yes
> Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
>            IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 00:1d:7d:af:84:2a
> Drives:    Local Storage: total: 1.02 TiB used: 9.12 GiB (0.9%)
>            ID-1: /dev/sda vendor: Crucial model: CT480BX500SSD1 size: 447.13 GiB
>            ID-2: /dev/sdb vendor: Western Digital model: WD3200AAJS-22B4A0 size: 298.09 GiB
>            ID-3: /dev/sdc vendor: Western Digital model: WD3200AAJS-56M0A0 size: 298.09 GiB
> Partition: ID-1: / size: 334.04 GiB used: 9.12 GiB (2.7%) fs: ext4 dev: /dev/sda3
> Swap:      Alert: No swap data was found.
> Sensors:   Message: No sensor data found. Is lm-sensors configured?
> Info:      Processes: 181 Uptime: 12m Memory: 7.77 GiB used: 1.02 GiB (13.1%) Shell: Bash inxi: 3.3.05

Have you checked for firmware updates?

F7 is the latest released update for the V1.0 motherboard.

Which version of KDE Neon did it work under? The latest KDE Neon release (more accurately, Ubuntu LTS + Neon repositories and packages) runs on the 5.4 kernel (or higher.)

Have you tested this SSD on a live session, perhaps trying to format it inside a live session? (I’m assuming you don’t have any important data stored on it?)

I am right now using the BX500 for Manjaro and KDE neon. Dual boot with Grub from Manjaro. KDE neon is the latest version and up to date. No timeouts with KDE neon, but MX Linux for instance has the same timeouts. I did not have any problems during the live session. Only during installation of Manjaro to the BX500, the installation of Grub showed several timeouts. Resizing the partition, occupying the whole disk (neon) and creating a new partition for Manjaro went smoothly. Formatting the new partition and installation of Manjaro, except for Grub, went also without problems. Same for applying many updates. Shutdown after installation of the updates however showed again some timeouts.

KDEneon:

Linux version 5.8.0-59-generic (buildd@lcy01-amd64-022) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #66~20.04.1-Ubuntu SMP Thu Jun 17 11:14:10 UTC 2021

Another example,
sudo dmesg

[ 317.375476] ata1.00: exception Emask 0x0 SAct 0x3fff0 SErr 0xc0002 action 0x6 frozen
[ 317.375481] ata1: SError: { RecovComm CommWake 10B8B }
[ 317.375484] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375488] ata1.00: cmd 61/08:20:31:4c:81/00:00:21:00:00/40 tag 4 ncq dma 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375489] ata1.00: status: { DRDY }
[ 317.375490] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375493] ata1.00: cmd 61/08:28:b1:95:cf/00:00:1b:00:00/40 tag 5 ncq dma 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375494] ata1.00: status: { DRDY }
[ 317.375497] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375500] ata1.00: cmd 61/80:30:f1:88:d4/00:00:1b:00:00/40 tag 6 ncq dma 65536 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375501] ata1.00: status: { DRDY }
[ 317.375503] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375506] ata1.00: cmd 61/08:38:c9:13:c8/00:00:2a:00:00/40 tag 7 ncq dma 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375507] ata1.00: status: { DRDY }
[ 317.375508] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375511] ata1.00: cmd 61/08:40:b9:95:cf/00:00:1b:00:00/40 tag 8 ncq dma 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375512] ata1.00: status: { DRDY }
[ 317.375513] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375516] ata1.00: cmd 61/48:48:71:7d:bd/00:00:0c:00:00/40 tag 9 ncq dma 36864 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375517] ata1.00: status: { DRDY }
[ 317.375518] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375521] ata1.00: cmd 61/08:50:c9:7d:bd/00:00:0c:00:00/40 tag 10 ncq dma 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375522] ata1.00: status: { DRDY }
[ 317.375523] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375526] ata1.00: cmd 61/08:58:99:80:bd/00:00:0c:00:00/40 tag 11 ncq dma 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375527] ata1.00: status: { DRDY }
[ 317.375528] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375531] ata1.00: cmd 61/08:60:41:83:bd/00:00:0c:00:00/40 tag 12 ncq dma 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375532] ata1.00: status: { DRDY }
[ 317.375533] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375537] ata1.00: cmd 61/08:68:a9:87:bd/00:00:0c:00:00/40 tag 13 ncq dma 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375537] ata1.00: status: { DRDY }
[ 317.375539] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375542] ata1.00: cmd 61/08:70:09:44:e4/00:00:1b:00:00/40 tag 14 ncq dma 4096 out
res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375543] ata1.00: status: { DRDY }
[ 317.375544] ata1.00: failed command: WRITE FPDMA QUEUED
[ 317.375547] ata1.00: cmd 61/08:78:d9:8d:bd/00:00:0c:00:00/40 tag 15 ncq dma 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375548] ata1.00: status: { DRDY }
[ 317.375549] ata1.00: failed command: READ FPDMA QUEUED
[ 317.375552] ata1.00: cmd 60/08:80:79:4b:bd/00:00:2a:00:00/40 tag 16 ncq dma 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375553] ata1.00: status: { DRDY }
[ 317.375554] ata1.00: failed command: READ FPDMA QUEUED
[ 317.375557] ata1.00: cmd 60/08:88:d1:f0:80/00:00:30:00:00/40 tag 17 ncq dma 4096 in
res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 317.375558] ata1.00: status: { DRDY }
[ 317.375561] ata1: hard resetting link
[ 317.844975] ata1: softreset failed (device not ready)
[ 317.844980] ata1: applying PMP SRST workaround and retrying
[ 318.001652] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 318.005227] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 318.010527] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 318.010531] ata1.00: configured for UDMA/133
[ 318.021245] ata1.00: device reported invalid CHS sector 0
[ 318.021249] ata1.00: device reported invalid CHS sector 0
[ 318.021254] ata1.00: device reported invalid CHS sector 0
[ 318.021256] ata1.00: device reported invalid CHS sector 0
[ 318.021260] ata1.00: device reported invalid CHS sector 0
[ 318.021262] ata1.00: device reported invalid CHS sector 0
[ 318.021263] ata1.00: device reported invalid CHS sector 0
[ 318.021268] ata1.00: device reported invalid CHS sector 0
[ 318.021331] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=30s
[ 318.021334] sd 0:0:0:0: [sda] tag#17 Sense Key : Illegal Request [current]
[ 318.021336] sd 0:0:0:0: [sda] tag#17 Add. Sense: Unaligned write command
[ 318.021338] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 30 80 f0 d1 00 00 08 00
[ 318.021341] blk_update_request: I/O error, dev sda, sector 813756625 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 318.021361] ata1: EH complete
[ 340.268435] audit: type=1100 audit(1626767035.439:70): pid=2770 uid=1000 auid=1000 ses=1 subj==unconfined msg=‘op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct=“gsm” exe="/usr/
bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success’
[ 340.269945] audit: type=1101 audit(1626767035.442:71): pid=2770 uid=1000 auid=1000 ses=1 subj==unconfined msg=‘op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct=“gsm” exe="/usr/bin/sudo" ho
stname=? addr=? terminal=/dev/pts/2 res=success’
[ 340.270219] audit: type=1110 audit(1626767035.442:72): pid=2770 uid=1000 auid=1000 ses=1 subj==unconfined msg=‘op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct=“root” exe="/usr/bin/su
do" hostname=? addr=? terminal=/dev/pts/2 res=success’
[ 340.271125] audit: type=1105 audit(1626767035.442:73): pid=2770 uid=1000 auid=1000 ses=1 subj==unconfined msg=‘op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct=“root” exe="/usr/bin/sud
o" hostname=? addr=? terminal=/dev/pts/2 res=success’

Example of normal boot, without serious delays, but still sata errors.
sudo dmesg:

[ 8.395582] ata1.00: exception Emask 0x10 SAct 0x780 SErr 0x40d0002 action 0xe frozen
[ 8.395585] ata1.00: irq_stat 0x00000040, connection status changed
[ 8.395588] ata1: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch }
[ 8.395590] ata1.00: failed command: READ FPDMA QUEUED
[ 8.395594] ata1.00: cmd 60/d0:38:f1:47:7c/00:00:2d:00:00/40 tag 7 ncq dma 106496 in
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
[ 8.395595] ata1.00: status: { DRDY }
[ 8.395596] ata1.00: failed command: READ FPDMA QUEUED
[ 8.395599] ata1.00: cmd 60/20:40:f1:85:1e/00:00:2b:00:00/40 tag 8 ncq dma 16384 in
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
[ 8.395600] ata1.00: status: { DRDY }
[ 8.395602] ata1.00: failed command: READ FPDMA QUEUED
[ 8.395605] ata1.00: cmd 60/98:48:49:ce:34/00:00:2b:00:00/40 tag 9 ncq dma 77824 in
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
[ 8.395605] ata1.00: status: { DRDY }
[ 8.395607] ata1.00: failed command: READ FPDMA QUEUED
[ 8.395610] ata1.00: cmd 60/38:50:c1:48:7c/00:00:2d:00:00/40 tag 10 ncq dma 28672 in
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
[ 8.395611] ata1.00: status: { DRDY }
[ 8.395614] ata1: hard resetting link
[ 9.292223] ata1: softreset failed (device not ready)
[ 9.292228] ata1: applying PMP SRST workaround and retrying
[ 9.448907] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 9.452476] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 9.457778] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 9.457782] ata1.00: configured for UDMA/133
[ 9.468572] sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=1s
[ 9.468577] sd 0:0:0:0: [sda] tag#7 Sense Key : Illegal Request [current]
[ 9.468579] sd 0:0:0:0: [sda] tag#7 Add. Sense: Unaligned write command
[ 9.468581] sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 2d 7c 47 f1 00 00 d0 00
[ 9.468585] blk_update_request: I/O error, dev sda, sector 763119601 op 0x0:(READ) flags 0x80700 phys_seg 26 prio class 0
[ 9.468604] sd 0:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=1s
[ 9.468606] sd 0:0:0:0: [sda] tag#8 Sense Key : Illegal Request [current]
[ 9.468607] sd 0:0:0:0: [sda] tag#8 Add. Sense: Unaligned write command
[ 9.468609] sd 0:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 2b 1e 85 f1 00 00 20 00
[ 9.468610] blk_update_request: I/O error, dev sda, sector 723420657 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 9.468630] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=1s
[ 9.468632] sd 0:0:0:0: [sda] tag#9 Sense Key : Illegal Request [current]
[ 9.468633] sd 0:0:0:0: [sda] tag#9 Add. Sense: Unaligned write command
[ 9.468635] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 2b 34 ce 49 00 00 98 00
[ 9.468636] blk_update_request: I/O error, dev sda, sector 724880969 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[ 9.468658] sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=1s
[ 9.468660] sd 0:0:0:0: [sda] tag#10 Sense Key : Illegal Request [current]
[ 9.468661] sd 0:0:0:0: [sda] tag#10 Add. Sense: Unaligned write command
[ 9.468663] sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 2d 7c 48 c1 00 00 38 00
[ 9.468665] blk_update_request: I/O error, dev sda, sector 763119809 op 0x0:(READ) flags 0x80000 phys_seg 7 prio class 0
[ 9.468675] ata1: EH complete
[ 9.468681] EXT4-fs error (device sda3): __ext4_get_inode_loc_noinmem:4445: inode #17437094: block 69730618: comm nm-dispatcher: unable to read itable block
[ 11.023045] radeon_dp_aux_transfer_native: 326 callbacks suppressed
[ 13.435585] ata1.00: exception Emask 0x10 SAct 0x40100 SErr 0x40d0002 action 0xe frozen
[ 13.435588] ata1.00: irq_stat 0x00000040, connection status changed
[ 13.435591] ata1: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch }
[ 13.435593] ata1.00: failed command: READ FPDMA QUEUED
[ 13.435597] ata1.00: cmd 60/08:40:b1:f1:03/00:00:2e:00:00/40 tag 8 ncq dma 4096 in
res 40/00:8c:71:1a:c8/00:00:1b:00:00/40 Emask 0x10 (ATA bus error)
[ 13.435598] ata1.00: status: { DRDY }
[ 13.435600] ata1.00: failed command: READ FPDMA QUEUED
[ 13.435603] ata1.00: cmd 60/20:90:81:1a:c8/00:00:1b:00:00/40 tag 18 ncq dma 16384 in
res 40/00:8c:71:1a:c8/00:00:1b:00:00/40 Emask 0x10 (ATA bus error)
[ 13.435604] ata1.00: status: { DRDY }
[ 13.435607] ata1: hard resetting link
[ 14.335564] ata1: softreset failed (device not ready)
[ 14.335568] ata1: applying PMP SRST workaround and retrying
[ 14.492245] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 14.495808] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 14.501119] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 14.501123] ata1.00: configured for UDMA/133
[ 14.511850] sd 0:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=1s
[ 14.511854] sd 0:0:0:0: [sda] tag#8 Sense Key : Illegal Request [current]
[ 14.511856] sd 0:0:0:0: [sda] tag#8 Add. Sense: Unaligned write command
[ 14.511859] sd 0:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 2e 03 f1 b1 00 00 08 00
[ 14.511862] blk_update_request: I/O error, dev sda, sector 772010417 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 14.511891] sd 0:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=1s
[ 14.511892] sd 0:0:0:0: [sda] tag#18 Sense Key : Illegal Request [current]
[ 14.511894] sd 0:0:0:0: [sda] tag#18 Add. Sense: Unaligned write command
[ 14.511896] sd 0:0:0:0: [sda] tag#18 CDB: Read(10) 28 00 1b c8 1a 81 00 00 20 00
[ 14.511897] blk_update_request: I/O error, dev sda, sector 466098817 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 14.511908] ata1: EH complete
[ 14.514676] kauditd_printk_skb: 9 callbacks suppressed
[ 14.514678] audit: type=1131 audit(1626773420.006:64): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg=‘unit=NetworkManager-dispatcher comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=?
addr=? terminal=? res=success’
[ 25.245433] logitech-hidpp-device 0003:046D:4008.0003: HID++ 2.0 device connected.
[ 33.814440] audit: type=1131 audit(1626773439.306:65): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg=‘unit=systemd-hostnamed comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success’
[ 33.942279] audit: type=1334 audit(1626773439.436:66): prog-id=16 op=UNLOAD
[ 33.942285] audit: type=1334 audit(1626773439.436:67): prog-id=15 op=UNLOAD
[ 33.942288] audit: type=1334 audit(1626773439.436:68): prog-id=14 op=UNLOAD
[ 68.060552] audit: type=1100 audit(1626773473.608:69): pid=1710 uid=1000 auid=1000 ses=1 subj==unconfined msg=‘op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct=“gsm” exe="/usr/bin/sud
o" hostname=? addr=? terminal=/dev/pts/2 res=success’
[ 68.062347] audit: type=1101 audit(1626773473.608:70): pid=1710 uid=1000 auid=1000 ses=1 subj==unconfined msg=‘op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct=“gsm” exe="/usr/bin/sudo" hostname=
? addr=? terminal=/dev/pts/2 res=success’
[ 68.062597] audit: type=1110 audit(1626773473.608:71): pid=1710 uid=1000 auid=1000 ses=1 subj==unconfined msg=‘op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct=“root” exe="/usr/bin/sudo" hos
tname=? addr=? terminal=/dev/pts/2 res=success’
[ 68.063499] audit: type=1105 audit(1626773473.608:72): pid=1710 uid=1000 auid=1000 ses=1 subj==unconfined msg=‘op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct=“root” exe="/usr/bin/sudo" host
name=? addr=? terminal=/dev/pts/2 res=success’

Have you tried with a different SATA cable and/or different SATA port and/or check for a loose connection? (All three steps above are not mutually exclusive. You can do all three at the same time.)

Are you saying with kernel 4.14, you get none of the above errors when using the drive?

If it works on KDE Neon kernel 5.8, what makes you believe the drive only behaves on kernel 4.14 and earlier?

I tried already several cables and another SATA port. No difference then. I will try some more ports.
Here is some dmesg output running kernel 4.14. No lagging at all with kernel 4.14.
Some errors: softreset failed (device not ready).

[ 1.277707] libata version 3.00 loaded.
[ 1.290029] ehci-pci 0000:00:13.5: USB 2.0 started, EHCI 1.00
[ 1.290283] hub 1-0:1.0: USB hub found
[ 1.290290] hub 1-0:1.0: 10 ports detected
[ 1.290787] ohci-pci: OHCI PCI platform driver
[ 1.291418] scsi host0: pata_atiixp
[ 1.291514] scsi host1: pata_atiixp
[ 1.291546] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf900 irq 14
[ 1.291547] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf908 irq 15
[ 1.291605] ahci 0000:00:12.0: version 3.0
[ 1.291719] ahci 0000:00:12.0: controller can’t do 64bit DMA, forcing 32bit
[ 1.291808] ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
[ 1.291810] ahci 0000:00:12.0: flags: ncq sntf ilck pm led clo pmp pio slum part ccc
[ 1.292332] scsi host2: ahci
[ 1.295784] scsi host3: ahci
[ 1.299266] scsi host4: ahci
[ 1.299394] scsi host5: ahci
[ 1.299431] ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f100 irq 22
[ 1.299434] ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f180 irq 22
[ 1.299436] ata5: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f200 irq 22
[ 1.299438] ata6: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f280 irq 22
[ 1.299692] ohci-pci 0000:00:13.0: OHCI PCI host controller
[ 1.299699] ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 2
[ 1.299734] ohci-pci 0000:00:13.0: irq 16, io mem 0xfe02e000
[ 1.307452] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 1.357585] hub 2-0:1.0: USB hub found
[ 1.357594] hub 2-0:1.0: 2 ports detected
[ 1.357884] ohci-pci 0000:00:13.1: OHCI PCI host controller
[ 1.357889] ohci-pci 0000:00:13.1: new USB bus registered, assigned bus number 3
[ 1.357923] ohci-pci 0000:00:13.1: irq 17, io mem 0xfe02d000
[ 1.417553] hub 3-0:1.0: USB hub found
[ 1.417562] hub 3-0:1.0: 2 ports detected
[ 1.418105] ohci-pci 0000:00:13.2: OHCI PCI host controller
[ 1.418111] ohci-pci 0000:00:13.2: new USB bus registered, assigned bus number 4
[ 1.418144] ohci-pci 0000:00:13.2: irq 18, io mem 0xfe02c000
[ 1.477547] hub 4-0:1.0: USB hub found
[ 1.477555] hub 4-0:1.0: 2 ports detected
[ 1.477770] ohci-pci 0000:00:13.3: OHCI PCI host controller
[ 1.477775] ohci-pci 0000:00:13.3: new USB bus registered, assigned bus number 5
[ 1.477793] ohci-pci 0000:00:13.3: irq 17, io mem 0xfe02b000
[ 1.537528] hub 5-0:1.0: USB hub found
[ 1.537537] hub 5-0:1.0: 2 ports detected
[ 1.537843] ohci-pci 0000:00:13.4: OHCI PCI host controller
[ 1.537851] ohci-pci 0000:00:13.4: new USB bus registered, assigned bus number 6
[ 1.537869] ohci-pci 0000:00:13.4: irq 18, io mem 0xfe02a000
[ 1.597536] hub 6-0:1.0: USB hub found
[ 1.597545] hub 6-0:1.0: 2 ports detected
[ 1.613458] ata6: SATA link down (SStatus 0 SControl 300)
[ 1.770048] ata4: softreset failed (device not ready)
[ 1.770139] ata4: applying PMP SRST workaround and retrying
[ 1.770158] ata3: softreset failed (device not ready)
[ 1.770250] ata3: applying PMP SRST workaround and retrying
[ 1.770269] ata5: softreset failed (device not ready)
[ 1.770362] ata5: applying PMP SRST workaround and retrying
[ 1.800038] usb 5-1: new full-speed USB device number 2 using ohci-pci
[ 1.920058] tsc: Refined TSC clocksource calibration: 2812.809 MHz
[ 1.920068] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x288b84f9b90, max_idle_ns: 440795272445 ns
[ 1.926731] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.926759] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.926786] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.927462] ata5.00: HPA detected: current 625140335, native 625142448
[ 1.927541] ata5.00: ATA-8: WDC WD3200AAJS-56M0A0, 01.03E01, max UDMA/133
[ 1.927543] ata5.00: 625140335 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.927546] ata5.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 1.928357] ata5.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 1.928359] ata5.00: configured for UDMA/133
[ 1.928923] ata3.00: ATA-10: CT480BX500SSD1, M6CR041, max UDMA/133
[ 1.928925] ata3.00: 937703088 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[ 1.930350] ata3.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 1.935648] ata3.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 1.935650] ata3.00: configured for UDMA/133
[ 1.935836] scsi 2:0:0:0: Direct-Access ATA CT480BX500SSD1 041 PQ: 0 ANSI: 5
[ 1.937246] sd 2:0:0:0: [sda] 937703088 512-byte logical blocks: (480 GB/447 GiB)
[ 1.937270] sd 2:0:0:0: [sda] Write Protect is off
[ 1.937272] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.937321] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[ 1.938043] sda: sda1 sda2 sda3
[ 1.938494] sd 2:0:0:0: [sda] Attached SCSI disk
[ 1.940338] ata4.00: ATA-8: WDC WD3200AAJS-22B4A0, 01.03A01, max UDMA/133
[ 1.940339] ata4.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.940343] ata4.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 1.941243] ata4.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 1.941245] ata4.00: configured for UDMA/133
[ 1.941391] scsi 3:0:0:0: Direct-Access ATA WDC WD3200AAJS-2 3A01 PQ: 0 ANSI: 5
[ 1.941601] sd 3:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 1.941612] sd 3:0:0:0: [sdb] Write Protect is off
[ 1.941613] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.941629] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[ 1.941688] scsi 4:0:0:0: Direct-Access ATA WDC WD3200AAJS-5 3E01 PQ: 0 ANSI: 5
[ 1.941939] sd 4:0:0:0: [sdc] 625140335 512-byte logical blocks: (320 GB/298 GiB)
[ 1.941959] sd 4:0:0:0: [sdc] Write Protect is off
[ 1.941962] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 1.941984] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[ 1.949290] sdb: sdb1 sdb2
[ 1.949694] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 1.957303] sdc: sdc1 sdc2
[ 1.957727] sd 4:0:0:0: [sdc] Attached SCSI disk

Other distributions have the same problems too. I also saw some remarks in other forums, where an advice was given to use kernel 4.14. After all this is old hardware, except for the SSD BX500.

That might be your only safe option. I honestly would not trust saving any data to that drive with the above errors, such as “failed command: READ FPDMA QUEUED” and “device reported invalid CHS sector”

That can lead to data loss and corruption.

I finally found an interesting topic on this, that might actually describe the same problem.

https://archived.forum.manjaro.org/t/solved-freezes-randomly/140917

Interesting. Check what scheduler is used, and see if changing it (i.e, “deadline” or “mq-deadline” or “none”) and then rebooting resolves this issue.

Make sure the “discard” option is not enable in your fstab for the SSD. Systemd weekly trims are the preferable route.

kernel 4.14 and below, have only sq schedulers (so not mq), but is possible to have mq schedulers by adding scsi_mod.use_blk_mq=1 to grub. You proably knows this, I just pointed out the instruction for the OP :slight_smile:

I was referring to their issues when using kernels 5.4 and higher (since they said they do not experience such issues on 4.14). If the goal is to be able to use the latest stable or LTS kernel (unless they are happy to stick with 4.14, in which they needn’t change anything.)

Good point though, and clarification never hurts. :slight_smile:

No difference when discard is added, but things get even worse with nodiscard.

UUID=b8a5edaf-c612-41dd-9e28-f1339e8c31e3 /              ext4    defaults,noatime 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

Not sure how to check or configure the scheduler.

/etc/udev/rules.d/60-ioschedulers.rules
It looks like this one gives good results with kernel 5.10.49-1-MANJARO

# set scheduler for NVMe
ACTION=="add|change", KERNEL=="nvme[0-9]*", ATTR{queue/scheduler}="none"
# set scheduler for SSD and eMMC
ACTION=="add|change", KERNEL=="sd[a-z]|mmcblk[0-9]*", ATTR{queue/rotational}=="0", ATTR{queue/scheduler}="bfq"
# set scheduler for rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", ATTR{queue/scheduler}="cfq"

Also i find that discard in fstab works better for the BX500 then nodiscard.

To check, depends on which device you’re interested in:
cat /sys/block/<device>/queue/scheduler


So for example,

$ cat /sys/block/sda/queue/scheduler
$ [mq-deadline] kyber bfq none

My SSD (/dev/sda, Samsung EVO) is using the multiqueue deadline scheduler (mq-deadline), which I believe is the default out of the box, because my un-edited 60-ioscheduler.rules file looks like so:

ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="0", ATTR{queue/scheduler}="deadline"
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", ATTR{queue/scheduler}="bfq-sq"

You can make a backup of the file /etc/udev/rules.d/60-ioscheduler.rules, and then modify it to override the scheduler based on a new rule.

EDIT: If you override a scheduler, make sure to use the exact name as shown in the supported schedulers. For example, if you change the scheduler to use magical-berries, the kernel will fallback to the default for that device, such as mq-deadline.


That’s odd, since discard can put more stress on the SSD to constantly trim on-the-fly. I think it’s safer to leave discard/nodiscard omitted from the fstab entry, and simply rely on the default weekly fstrim timer.

To make sure the timer is active:
systemctl status fstrim.timer

To make sure the service is being triggered by the above weekly timer:
systemctl status fstrim.service

Otherwise, unmask, enable, and start the timer:
systemctl unmask fstrim.timer
systemctl enable fstrim.timer
systemctl start fstrim.timer