Gentoo Forums :: View topic - disk device errors/failures in dmesg

disk device errors/failures in dmesg

View unanswered posts
View posts from last 24 hours

Gentoo Forums Forum Index

Kernel & Hardware

View previous topic :: View next topic

Author

Message

irets
Apprentice

Joined: 17 Dec 2019
Posts: 229

Posted: Sun Nov 07, 2021 9:22 pm Post subject: disk device errors/failures in dmesg

Hi,
I have noticed a couple of disk device related errors in my dmesg.

Code:

$ dmesg | grep -i fail
[ 4.255608] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[31548.984346] sr 1:0:0:0: [sr0] tag#27 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[31616.349196] sr 1:0:0:0: [sr0] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[31670.294347] sr 1:0:0:0: [sr0] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=121s
[31726.644241] sr 1:0:0:0: [sr0] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=59s
[44379.665145] sr 1:0:0:0: [sr0] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[60651.478625] sr 1:0:0:0: [sr0] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=15s
[60678.955172] sr 1:0:0:0: [sr0] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=160s
[67790.212526] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212532] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212538] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212543] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212548] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212553] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212558] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212563] ata4.00: failed command: WRITE FPDMA QUEUED
[133784.880732] sr 1:0:0:0: [sr0] tag#19 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=195s
[133840.757313] sr 1:0:0:0: [sr0] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=103s
[133899.937346] sr 1:0:0:0: [sr0] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=66s
[222758.273083] sr 1:0:0:0: [sr0] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s

Looking up ata4.00: failed command: WRITE FPDMA QUEUED brought me to an Arch Linux forum page where someone had the same errors and apparently their disk was at the end of it's life.
ata4.00 has lot of entries in dmesg:

Code:

$ dmesg | grep -i ata4
[ 1.740401] ata4: SATA max UDMA/133 abar m2048@0xf7315000 port 0xf7315280 irq 29
[ 2.053091] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.056280] ata4.00: supports DRM functions and may not be fully accessible
[ 2.056866] ata4.00: disabling queued TRIM support
[ 2.056867] ata4.00: ATA-11: Samsung SSD 870 QVO 2TB, SVQ01B6Q, max UDMA/133
[ 2.056868] ata4.00: 3907029168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[ 2.059009] ata4.00: supports DRM functions and may not be fully accessible
[ 2.059454] ata4.00: disabling queued TRIM support
[ 2.061259] ata4.00: configured for UDMA/133
[ 2.087734] ata4.00: Enabling discard_zeroes_data
[ 2.106022] ata4.00: Enabling discard_zeroes_data
[ 2.139294] ata4.00: Enabling discard_zeroes_data
[67790.212521] ata4.00: exception Emask 0x10 SAct 0x8fc00001 SErr 0x400100 action 0x6 frozen
[67790.212523] ata4.00: irq_stat 0x08000008, interface fatal error
[67790.212525] ata4: SError: { UnrecovData Handshk }
[67790.212526] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212530] ata4.00: cmd 61/02:00:24:48:a4/00:00:b3:00:00/40 tag 0 ncq dma 1024 out
[67790.212531] ata4.00: status: { DRDY }
[67790.212532] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212535] ata4.00: cmd 61/04:b0:9e:48:48/00:00:86:00:00/40 tag 22 ncq dma 2048 out
[67790.212536] ata4.00: status: { DRDY }
[67790.212538] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212541] ata4.00: cmd 61/02:b8:30:4a:48/00:00:86:00:00/40 tag 23 ncq dma 1024 out
[67790.212542] ata4.00: status: { DRDY }
[67790.212543] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212546] ata4.00: cmd 61/08:c0:92:54:dc/00:00:97:00:00/40 tag 24 ncq dma 4096 out
[67790.212547] ata4.00: status: { DRDY }
[67790.212548] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212551] ata4.00: cmd 61/04:c8:ae:54:dc/00:00:97:00:00/40 tag 25 ncq dma 2048 out
[67790.212552] ata4.00: status: { DRDY }
[67790.212553] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212556] ata4.00: cmd 61/0c:d0:12:48:38/00:00:b3:00:00/40 tag 26 ncq dma 6144 out
[67790.212557] ata4.00: status: { DRDY }
[67790.212558] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212561] ata4.00: cmd 61/02:d8:04:48:3c/00:00:b3:00:00/40 tag 27 ncq dma 1024 out
[67790.212562] ata4.00: status: { DRDY }
[67790.212563] ata4.00: failed command: WRITE FPDMA QUEUED
[67790.212566] ata4.00: cmd 61/28:f8:5c:13:3a/00:00:43:00:00/40 tag 31 ncq dma 20480 out
[67790.212567] ata4.00: status: { DRDY }
[67790.212569] ata4: hard resetting link
[67790.525353] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[67790.528501] ata4.00: supports DRM functions and may not be fully accessible
[67790.528941] ata4.00: disabling queued TRIM support
[67790.530963] ata4.00: supports DRM functions and may not be fully accessible
[67790.531336] ata4.00: disabling queued TRIM support
[67790.533036] ata4.00: configured for UDMA/133
[67790.533049] ata4: EH complete
[67790.533119] ata4.00: Enabling discard_zeroes_data

I don't quite understand why sr0 is also reporting failures because it's my CD drive and it's empty.
Can someone tell me more about these dmesg entries? I'd be surprised if one of my SSDs was dying but not my 5-6 years old HDD.

Additional information about my disks:

Code:

$ cat /proc/scsi/scsi
Attached devices:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: ASUS Model: DRW-24F1ST a Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: WDC WD20EZRX-00D Rev: 0A80
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: Samsung SSD 870 Rev: 1B6Q
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: KINGSTON SA400S3 Rev: K1B3
Type: Direct-Access ANSI SCSI revision: 05

Code:

$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 1.8T 0 disk
└─sda1 8:1 0 1.8T 0 part /mnt/hdd
sdb 8:16 0 1.8T 0 disk
└─sdb1 8:17 0 1.6T 0 part /
sdc 8:32 0 894.3G 0 disk
└─sdc1 8:33 0 894.3G 0 part /mnt/ssd2
sr0 11:0 1 1024M 0 rom

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 54849
Location: 56N 3W

Posted: Sun Nov 07, 2021 9:39 pm Post subject:

Irets,

Code:

[ 2.056867] ata4.00: ATA-11: Samsung SSD 870 QVO 2TB, SVQ01B6Q, max UDMA/133

What does smartctl -x saye about /dev/... whatever that is?

I suspect you have interface issues rather that drive issues.

Interface means motherboard chipset, data cable, or drive interface.
Poor quality SATA data cables are a never ending source of issues.

That

Code:

smartctl -x

command will tell what's going on inside the drive.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Display posts from previous:

	Gentoo Forums Forum Index Kernel & Hardware	All times are GMT
Page 1 of 1

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Copyright 2001-2025 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy