(argh and somehow I lost the list cc: again)
To recap:
> Sep 16 21:47:44 ArchPC kernel: ata3.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x0
> Sep 16 21:47:44 ArchPC kernel: ata3.00: irq_stat 0x40000008
> Sep 16 21:47:44 ArchPC kernel: ata3.00: failed command: READ FPDMA QUEUED
> Sep 16 21:47:44 ArchPC kernel: ata3.00: cmd 60/80:28:80:40:9b/00:00:1b:00:00/40 tag 5 ncq dma 65536 in
> res 43/40:80:b0:40:9b/00:00:1b:00:00/00 Emask 0x409 (media error) <F>
> Sep 16 21:47:44 ArchPC kernel: ata3.00: status: { DRDY SENSE ERR }
> Sep 16 21:47:44 ArchPC kernel: ata3.00: error: { UNC }
> Sep 16 21:47:44 ArchPC kernel: audit: type=1130 audit(1600285664.564:3248): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=spdynu comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Sep 16 21:47:44 ArchPC kernel: ata3.00: configured for UDMA/133
> Sep 16 21:47:44 ArchPC kernel: sd 2:0:0:0: [sdc] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
> Sep 16 21:47:44 ArchPC kernel: sd 2:0:0:0: [sdc] tag#5 Sense Key : Medium Error [current]
> Sep 16 21:47:44 ArchPC kernel: sd 2:0:0:0: [sdc] tag#5 Add. Sense: Unrecovered read error - auto reallocate failed
> Sep 16 21:47:44 ArchPC kernel: sd 2:0:0:0: [sdc] tag#5 CDB: Read(16) 88 00 00 00 00 00 1b 9b 40 80 00 00 00 80 00 00
> Sep 16 21:47:44 ArchPC kernel: blk_update_request: I/O error, dev sdc, sector 463159472 op 0x0:(READ) flags 0x0 phys_seg 10 prio class 0
> Sep 16 21:47:44 ArchPC kernel: ata3: EH complete
...
>>> From the dmesg, you have errors on sdc. What is the physical volume behind dm-1? Is this sdc, or is this a cdrom?
>> /dev/sdc is the only drive with XFS on my system, i don't have a cdrom.
>
> Then I think your hardware is failing.
On 9/19/20 12:17 PM, Agustín Casasampere Fernandez wrote:
>> Then I think your hardware is failing.
> Is there any way to recover the data?
There are data recovery firms out there, but I can't help you with hardware issues.
> like, clear the inode that can't be mapped, so xfs_repair can at least try to do something, or some utility that will allow me to copy some of the files over from /dev/mapper/storage over to a different hard drive?
>
> I still think this is not a hardware issue, the drive is way too new, and it's not that heavy on use, it has never been filled, and it's location has been static.
Then perhaps it's a driver error, but the dmesg says "media error" and "Unrecovered read error"
This isn't something XFS can fix or recover from; the problem seems to lie
below the filesystem.
-Eric
