SSD ATA failed command: READ FPDMA QUEUED

[takeseem]

when I upgrade to kernel 5.0.0-32-generic #34~18.04.2-Ubuntu, my computer wake up from mem's sleep or power on, my /dev/sda1 will remount to ready only.
It's happend many too times, but about 1 month before it's not happend.

1. sudo smartctl -a /dev/sda
---------------------------------------
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.0.0-32-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: SanDisk SSD PLUS 480GB
Serial Number: 183299803102
LU WWN Device Id: 5 001b44 8b9450075
Firmware Version: UG4500RL
User Capacity: 480,113,590,272 bytes [480 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Nov 5 09:49:48 2019 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
     was never started.
     Auto Offline Data Collection: Disabled.
Self-test execution status: ( 32) The self-test routine was interrupted
     by the host with a hard or soft reset.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x15) SMART execute Offline immediate.
     No Auto Offline data collection support.
     Abort Offline collection upon new
     command.
     No Offline surface scan supported.
     Self-test supported.
     No Conveyance Self-test supported.
     No 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: ( 85) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct 0x0032 100 100 000 Old_age Always - 0
  9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 2509
 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 945
165 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 65
166 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 1
167 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 0
168 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 3
169 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 287
170 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 0
171 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
172 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
173 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 1
174 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 17
184 End-to-End_Error 0x0032 100 100 --- Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 12
188 Command_Timeout 0x0032 100 100 --- Old_age Always - 0
194 Temperature_Celsius 0x0022 074 057 000 Old_age Always - 26 (Min/Max 2/57)
199 UDMA_CRC_Error_Count 0x0032 100 100 --- Old_age Always - 0
230 Unknown_SSD_Attribute 0x0032 100 100 000 Old_age Always - 77310722066
232 Available_Reservd_Space 0x0033 100 100 005 Pre-fail Always - 100
233 Media_Wearout_Indicator 0x0032 100 100 --- Old_age Always - 131
234 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 732
241 Total_LBAs_Written 0x0030 100 100 000 Old_age Offline - 274
242 Total_LBAs_Read 0x0030 100 100 000 Old_age Offline - 628
244 Unknown_Attribute 0x0032 000 100 --- Old_age Always - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 2507 -
# 2 Extended offline Aborted by host 90% 2495 -
# 3 Short offline Aborted by host 60% 2495 -

Selective Self-tests/Logging not supported
---------------------------------------

1. /var/log/syslog
---------------------------------------
Nov 5 09:20:33 localhost kernel: [16158.460256] ata1.00: exception Emask 0x0 SAct 0x800000 SErr 0x40000 action 0x0
Nov 5 09:20:33 localhost kernel: [16158.460263] ata1.00: irq_stat 0x40000008
Nov 5 09:20:33 localhost kernel: [16158.460267] ata1: SError: { CommWake }
Nov 5 09:20:33 localhost kernel: [16158.460272] ata1.00: failed command: READ FPDMA QUEUED
Nov 5 09:20:33 localhost kernel: [16158.460280] ata1.00: cmd 60/08:b8:e8:25:01/00:00:30:00:00/40 tag 23 ncq dma 4096 in
Nov 5 09:20:33 localhost kernel: [16158.460280] res 41/40:00:e8:25:01/00:00:30:00:00/00 Emask 0x409 (media error) <F>
Nov 5 09:20:33 localhost kernel: [16158.460283] ata1.00: status: { DRDY ERR }
Nov 5 09:20:33 localhost kernel: [16158.460286] ata1.00: error: { UNC }
Nov 5 09:20:33 localhost kernel: [16158.466531] ata1.00: configured for UDMA/133
Nov 5 09:20:33 localhost kernel: [16158.466554] sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Nov 5 09:20:33 localhost kernel: [16158.466559] sd 0:0:0:0: [sda] tag#23 Sense Key : Medium Error [current]
Nov 5 09:20:33 localhost kernel: [16158.466562] sd 0:0:0:0: [sda] tag#23 Add. Sense: Unrecovered read error - auto reallocate failed
Nov 5 09:20:33 localhost kernel: [16158.466567] sd 0:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 30 01 25 e8 00 00 08 00
Nov 5 09:20:33 localhost kernel: [16158.466570] print_req_error: I/O error, dev sda, sector 805381608 flags 3000
Nov 5 09:20:33 localhost kernel: [16158.466604] ata1: EH complete
Nov 5 09:20:33 localhost kernel: [16158.466633] EXT4-fs error (device sda1): ext4_find_entry:1455: inode #25171387: comm updatedb.mlocat: reading directory lblock 0
Nov 5 09:20:33 localhost kernel: [16158.467755] Aborting journal on device sda1-8.
Nov 5 09:20:33 localhost kernel: [16158.468456] EXT4-fs (sda1): Remounting filesystem read-only
---------------------------------------

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
Date: Tue Nov 5 09:37:01 2019
ProcEnviron:
 LANGUAGE=zh_CN:zh:en_US:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

[Kokoko3k (kokoko3k)]

Hi,
I was searching for something similar because i've the very same SSD model, and an error that looks almost equal to yours.
My distro, however, is not Ubuntu, I use Arch.

Even if we use different kernels, it is weird that we're starting to have problems since November 2019, isnt'it?

My theory, is that while Arch uses vanilla kernel as much as possible and is a rolling distro, Ubuntu may have backported newer kernel "features" from (mine) 5.3.8 to (yours) 5.0.0-32.
That features breaks something.

Please, forgive me if it is not allowed, i'm just posting here a link to my archlinux forum post:
https://bbs.archlinux.org/viewtopic.php?id=250764

As you can see, we've the very same ssd (different firmware), and smart looks really ok.
I've even tried to reproduce the error via hdparm,dd and badblock program or the full smart self test, but everything seems to be right.
The only way to reproduce the issue, for me, is to read every single file from the partition.
As i do that, i've exactly 4 warnings in the log.
Fortunately i've never had a write error, and my system does not remount the partition read only has it happen in your case, but that could be a configuration thing.
The only downside for me seems that while the error is triggered, the system freezes up for a second or so.

Can i ask you:
* What is your motherboard chipset? I'm using an Asus Z97-K (so Z97 chipset onboard)
* When has kernel 5.0.0-32-generic (ubuntu) been released?
* What is and when your previous kernel been released? Mine, 5.3.8.1, has been released in 2019, October, 29

Let's try to isolate the issue :)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.