On 9/12/26 09:03, Gary Dale wrote:
...
# tail -n 40 syslog
2026-09-12T11:47:08.699532-04:00 TheLibrarian kernel: md: md_import_device returned -22 2026-09-12T11:47:08.919469-04:00 TheLibrarian kernel: ata2.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x0 2026-09-12T11:47:08.919482-04:00 TheLibrarian kernel: ata2.00: irq_stat 0x40000008 2026-09-12T11:47:08.919485-04:00 TheLibrarian kernel: ata2.00: failed command: READ FPDMA QUEUED 2026-09-12T11:47:08.919487-04:00 TheLibrarian kernel: ata2.00: cmd 60/08:28:08:08:00/00:00:00:00:00/40 tag 5 ncq dma 4096 in 2026-09-12T11:47:08.919489-04:00 TheLibrarian kernel:          res 41/40:00:0a:08:00/00:00:00:00:00/40 Emask 0x409 (media error) <F> 2026-09-12T11:47:08.919491-04:00 TheLibrarian kernel: ata2.00: status: { DRDY ERR } 2026-09-12T11:47:08.919493-04:00 TheLibrarian kernel: ata2.00: error: { UNC } 2026-09-12T11:47:08.931930-04:00 TheLibrarian kernel: ata2.00: configured for UDMA/133 2026-09-12T11:47:08.931945-04:00 TheLibrarian kernel: sd 1:0:0:0: [sde] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s 2026-09-12T11:47:08.931948-04:00 TheLibrarian kernel: sd 1:0:0:0: [sde] tag#5 Sense Key : Medium Error [current] 2026-09-12T11:47:08.931950-04:00 TheLibrarian kernel: sd 1:0:0:0: [sde] tag#5 Add. Sense: Unrecovered read error - auto reallocate failed 2026-09-12T11:47:08.931953-04:00 TheLibrarian kernel: sd 1:0:0:0: [sde] tag#5 CDB: Read(16) 88 00 00 00 00 00 00 00 08 08 00 00 00 08 00 00 2026-09-12T11:47:08.931954-04:00 TheLibrarian kernel: I/O error, dev sde, sector 2058 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 2026-09-12T11:47:08.931956-04:00 TheLibrarian kernel: Buffer I/O error on dev sde1, logical block 1, async page read
2026-09-12T11:47:08.935441-04:00 TheLibrarian kernel: ata2: EH complete
2026-09-12T11:47:09.156374-04:00 TheLibrarian kernel: ata2.00: exception Emask 0x0 SAct 0x4000000 SErr 0x0 action 0x0 2026-09-12T11:47:09.156387-04:00 TheLibrarian kernel: ata2.00: irq_stat 0x40000008 2026-09-12T11:47:09.156389-04:00 TheLibrarian kernel: ata2.00: failed command: READ FPDMA QUEUED 2026-09-12T11:47:09.156392-04:00 TheLibrarian kernel: ata2.00: cmd 60/08:d0:08:08:00/00:00:00:00:00/40 tag 26 ncq dma 4096 in 2026-09-12T11:47:09.156395-04:00 TheLibrarian kernel:          res 41/40:00:0a:08:00/00:00:00:00:00/40 Emask 0x409 (media error) <F> 2026-09-12T11:47:09.156397-04:00 TheLibrarian kernel: ata2.00: status: { DRDY ERR } 2026-09-12T11:47:09.159694-04:00 TheLibrarian kernel: ata2.00: error: { UNC } 2026-09-12T11:47:09.171702-04:00 TheLibrarian kernel: ata2.00: configured for UDMA/133 2026-09-12T11:47:09.171714-04:00 TheLibrarian kernel: sd 1:0:0:0: [sde] tag#26 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s 2026-09-12T11:47:09.171717-04:00 TheLibrarian kernel: sd 1:0:0:0: [sde] tag#26 Sense Key : Medium Error [current] 2026-09-12T11:47:09.171720-04:00 TheLibrarian kernel: sd 1:0:0:0: [sde] tag#26 Add. Sense: Unrecovered read error - auto reallocate failed 2026-09-12T11:47:09.171722-04:00 TheLibrarian kernel: sd 1:0:0:0: [sde] tag#26 CDB: Read(16) 88 00 00 00 00 00 00 00 08 08 00 00 00 08 00 00 2026-09-12T11:47:09.171724-04:00 TheLibrarian kernel: I/O error, dev sde, sector 2058 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
2026-09-12T11:47:09.171726-04:00 TheLibrarian kernel: ata2: EH complete
2026-09-12T11:47:09.327835-04:00 TheLibrarian kernel: ata2.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x0 2026-09-12T11:47:09.327848-04:00 TheLibrarian kernel: ata2.00: irq_stat 0x40000008 2026-09-12T11:47:09.327851-04:00 TheLibrarian kernel: ata2.00: failed command: READ FPDMA QUEUED 2026-09-12T11:47:09.327854-04:00 TheLibrarian kernel: ata2.00: cmd 60/08:d8:08:08:00/00:00:00:00:00/40 tag 27 ncq dma 4096 in 2026-09-12T11:47:09.327857-04:00 TheLibrarian kernel:          res 41/40:00:0a:08:00/00:00:00:00:00/40 Emask 0x409 (media error) <F> 2026-09-12T11:47:09.327860-04:00 TheLibrarian kernel: ata2.00: status: { DRDY ERR } 2026-09-12T11:47:09.331467-04:00 TheLibrarian kernel: ata2.00: error: { UNC } 2026-09-12T11:47:09.343451-04:00 TheLibrarian kernel: ata2.00: configured for UDMA/133 2026-09-12T11:47:09.343457-04:00 TheLibrarian kernel: Buffer I/O error on dev sde1, logical block 1, async page read
2026-09-12T11:47:09.343459-04:00 TheLibrarian kernel: ata2: EH complete


On 9/12/26 09:12, Andy Smith wrote:
> This is a pretty low level error and I'd be a little worried.
>
> Are you able to read the whole disk with dd without error?
>
> # dd if=/dev/sde of=/dev/null
>
> And smartctl long self-test comes out okay?
>
> # smartctl -t long /dev/sde


+1


I also suggest:

1. Check the AC outlet with an electrical multimeter when the computer is operating.

2.  Check the computer power supply unit (PSU) output with a PSU tester.

3. Unplug and re-plug all of the the cables inside the case. For various reasons, even gold-plated electrical connectors can become intermittent over the years -- especially when the signals are hundreds of megahertz. Beware that all electrical connectors have a connect-disconnect cycle rating, which can be as low as 10 cycles. I replace all red SATA cables on sight -- I once cut one open and found corroded copper sand inside.

4. Audit everything connected to your disk drives. Make sure all of the ratings meet or exceed the disk ratings. Replace anything that is wrong, degraded, or ambiguous. Over the years, I had been collecting and re-using SATA I, II, and III cables and racks. This turned into a nightmare around 2019. I have since replaced all of my SATA cables and racks with new, rated, marked, and/or locking SATA III 6 Gbps components. My servers now have SAS disks and locking cables. The hardware is now reliable.

5. I agree that reading the entire disk can find bad blocks, but I prefer to verify both write and read. In the past, I zero-filled drives. The problem is that all of those zeroes look the same. Now I use a pseudo-random number generator to lay down a predictable, unique and non-repeating pattern on disk. This makes it possible to find even more problems, including disks with fraudulent size.


Finally, now might be a god time to consider reworking your storage to include data integrity. AIUI dm-integrity is not production ready. I am unsure about btrfs. I use and recommend ZFS for data storage and backup.


David

Reply via email to