January 5, 20224 yr I've been having some fun, I have several SSDs and recently found that several files have input/output error when read. I have tried xfs_repair but the files aren't moved / dealt with. I've rebooted with the array stopped (since this concerns cache only), and mounted the disk: root@xxx-xxx:/path/Games.1952.1080p.BluRay.Remux.AVC.FLAC.2.0-HiFi# mv Games.1952.BluRay.Remux.1080p.AVC.FLAC.2.0-HiFi.mkv /mnt/downloads/completes/sabnzbd/movies/completes/Games.1952.1080p.BluRay.Remux.AVC.FLAC.2.0-HiFi/ mv: error reading 'Games.1952.BluRay.Remux.1080p.AVC.FLAC.2.0-HiFi.mkv': Input/output error [ 294.995043] xfs filesystem being mounted at /mnt/disks/cache supports timestamps until 2038 (0x7fffffff) [ 483.438612] ata4.00: exception Emask 0x0 SAct 0x600000 SErr 0x0 action 0x0 [ 483.438616] ata4.00: irq_stat 0x40000008 [ 483.438622] ata4.00: failed command: READ FPDMA QUEUED [ 483.438628] ata4.00: cmd 60/00:a8:10:7d:07/02:00:21:00:00/40 tag 21 ncq dma 262144 in res 41/40:00:30:7e:07/00:02:21:00:00/00 Emask 0x409 (media error) <F> [ 483.438630] ata4.00: status: { DRDY ERR } [ 483.438632] ata4.00: error: { UNC } [ 483.439080] ata4.00: supports DRM functions and may not be fully accessible [ 483.442157] ata4.00: supports DRM functions and may not be fully accessible [ 483.444552] ata4.00: configured for UDMA/133 [ 483.444569] sd 5:0:0:0: [sdd] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s [ 483.444573] sd 5:0:0:0: [sdd] tag#21 Sense Key : 0x3 [current] [ 483.444576] sd 5:0:0:0: [sdd] tag#21 ASC=0x11 ASCQ=0x4 [ 483.444580] sd 5:0:0:0: [sdd] tag#21 CDB: opcode=0x28 28 00 21 07 7d 10 00 02 00 00 [ 483.444584] blk_update_request: I/O error, dev sdd, sector 554139184 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0 [ 483.444606] ata4: EH complete [ 483.444729] ata4.00: Enabling discard_zeroes_data [ 483.762728] ata4.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0 [ 483.762731] ata4.00: irq_stat 0x40000008 [ 483.762737] ata4.00: failed command: READ FPDMA QUEUED [ 483.762743] ata4.00: cmd 60/08:c8:b0:7e:07/00:00:21:00:00/40 tag 25 ncq dma 4096 in res 41/40:08:b0:7e:07/00:00:21:00:00/00 Emask 0x409 (media error) <F> [ 483.762746] ata4.00: status: { DRDY ERR } [ 483.762748] ata4.00: error: { UNC } [ 483.762996] ata4.00: supports DRM functions and may not be fully accessible [ 483.765512] ata4.00: supports DRM functions and may not be fully accessible [ 483.767510] ata4.00: configured for UDMA/133 [ 483.767524] sd 5:0:0:0: [sdd] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s [ 483.767528] sd 5:0:0:0: [sdd] tag#25 Sense Key : 0x3 [current] [ 483.767531] sd 5:0:0:0: [sdd] tag#25 ASC=0x11 ASCQ=0x4 [ 483.767534] sd 5:0:0:0: [sdd] tag#25 CDB: opcode=0x28 28 00 21 07 7e b0 00 00 08 00 [ 483.767538] blk_update_request: I/O error, dev sdd, sector 554139312 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 483.767552] ata4: EH complete [ 483.767653] ata4.00: Enabling discard_zeroes_data [ 483.932594] ata4.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0 [ 483.932597] ata4.00: irq_stat 0x40000008 [ 483.932602] ata4.00: failed command: READ FPDMA QUEUED [ 483.932608] ata4.00: cmd 60/08:88:b0:7e:07/00:00:21:00:00/40 tag 17 ncq dma 4096 in res 41/40:08:b0:7e:07/00:00:21:00:00/00 Emask 0x409 (media error) <F> [ 483.932610] ata4.00: status: { DRDY ERR } [ 483.932612] ata4.00: error: { UNC } [ 483.932858] ata4.00: supports DRM functions and may not be fully accessible [ 483.935448] ata4.00: supports DRM functions and may not be fully accessible [ 483.937495] ata4.00: configured for UDMA/133 [ 483.937509] sd 5:0:0:0: [sdd] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s [ 483.937513] sd 5:0:0:0: [sdd] tag#17 Sense Key : 0x3 [current] [ 483.937516] sd 5:0:0:0: [sdd] tag#17 ASC=0x11 ASCQ=0x4 [ 483.937519] sd 5:0:0:0: [sdd] tag#17 CDB: opcode=0x28 28 00 21 07 7e b0 00 00 08 00 [ 483.937523] blk_update_request: I/O error, dev sdd, sector 554139312 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 483.937537] ata4: EH complete [ 483.937632] ata4.00: Enabling discard_zeroes_data I feel like really there's a bad block and these files need to be hidden/removed (the disk is an SSD), but I was expecting xfs_repair /dev/sdd1 to take care of that ¯\_(ツ)_/¯ beyonder-nas-diagnostics-20220105-1734.zip Edited January 5, 20224 yr by spamalam
January 5, 20224 yr Community Expert Cache is reporting media errors, xfs_repair won't work on a failing device, best bet is to clone the device to a new one with ddrescue then use xfs_repair on it.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.