My IncusOS host has slow pool performance and I can hear one of the disks making unusual noise. The disk probably needs replacing. Through IncusOS, how do I determine the serial number for the drive affected by this problem?
The logs have these abnormal messages and they indicate ata4.00 is where the problem is:
[2026/06/25 18:12:13 EDT] kernel: ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 22
res 40/00:0c:78:28:00/00:00:02:00:00/40 Emask 0x50 (ATA bus error)
[2026/06/25 18:12:13 EDT] kernel: ata4.00: status: { DRDY }
[2026/06/25 18:12:13 EDT] kernel: ata4: hard resetting link
[2026/06/25 18:12:19 EDT] kernel: ata4: link is slow to respond, please be patient (ready=0)
[2026/06/25 18:12:20 EDT] kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[2026/06/25 18:12:20 EDT] kernel: ata4.00: configured for UDMA/133
[2026/06/25 18:12:20 EDT] kernel: ata4.00: retrying FLUSH 0xea Emask 0x50
[2026/06/25 18:12:20 EDT] kernel: ata4: EH complete
[2026/06/25 18:12:35 EDT] kernel: ata4: link is slow to respond, please be patient (ready=0)
[2026/06/25 18:12:36 EDT] kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[2026/06/25 18:12:36 EDT] kernel: ata4.00: configured for UDMA/133
[2026/06/25 18:14:11 EDT] kernel: ata4.00: exception Emask 0x50 SAct 0x0 SErr 0x4070802 action 0xe frozen
[2026/06/25 18:14:11 EDT] kernel: ata4.00: irq_stat 0x00000040, connection status changed
[2026/06/25 18:14:11 EDT] kernel: ata4: SError: { RecovComm HostInt PHYRdyChg PHYInt CommWake DevExch }
[2026/06/25 18:14:11 EDT] kernel: ata4.00: failed command: FLUSH CACHE EXT
[2026/06/25 18:14:11 EDT] kernel: ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 12
res 40/00:7c:10:29:00/00:00:02:00:00/40 Emask 0x50 (ATA bus error)
[2026/06/25 18:14:11 EDT] kernel: ata4.00: status: { DRDY }
[2026/06/25 18:14:11 EDT] kernel: ata4: hard resetting link
[2026/06/25 18:14:17 EDT] kernel: ata4: link is slow to respond, please be patient (ready=0)
[2026/06/25 18:14:19 EDT] kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[2026/06/25 18:14:19 EDT] kernel: ata4.00: configured for UDMA/133
[2026/06/25 18:14:19 EDT] kernel: ata4.00: retrying FLUSH 0xea Emask 0x50
[2026/06/25 18:14:19 EDT] kernel: ata4: EH complete
[2026/06/25 18:14:27 EDT] kernel: ata4: link is slow to respond, please be patient (ready=0)
[2026/06/25 18:14:30 EDT] kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[2026/06/25 18:14:30 EDT] kernel: ata4.00: configured for UDMA/133
[2026/06/25 18:14:32 EDT] kernel: ata4.00: limiting speed to UDMA/100:PIO4
[2026/06/25 18:14:33 EDT] kernel: ata4: found unknown device (class 0)
[2026/06/25 18:14:38 EDT] kernel: ata4: link is slow to respond, please be patient (ready=0)
[2026/06/25 18:14:40 EDT] kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[2026/06/25 18:14:40 EDT] kernel: ata4.00: configured for UDMA/100
[2026/06/25 18:15:16 EDT] kernel: ata4.00: exception Emask 0x50 SAct 0x0 SErr 0x4070802 action 0xe frozen
[2026/06/25 18:15:17 EDT] kernel: ata4.00: irq_stat 0x00000040, connection status changed
[2026/06/25 18:15:17 EDT] kernel: ata4: SError: { RecovComm HostInt PHYRdyChg PHYInt CommWake DevExch }
[2026/06/25 18:15:17 EDT] kernel: ata4.00: failed command: FLUSH CACHE EXT
Despite the obvious problem, the ZFS pool is ONLINE, however, the scrub seems to be impacted by the slow disk problem.
All drives have passed SMART tests and there are no unusual errors, so based on this output here, I can’t figure out which one would be associated with ata4.00. Here’s an example of what one looks like:
You may be able to figure it out if you look at the early kernel boot messages when the drives were first probed. That should show you the ATA port coming online and then the drive in question appearing, hopefully with its serial or other useful characteristic.