I'm getting some errors on a zpool scrub operation. It's obvious that sdd has the problem both from the below output of zpool status and from the fact that the kernel message log has read errors about sdd. But how can I get detail about what has gone wrong? Has sdd given corrupt data in addition to read failures? Presumably the "(repairing)" string will disappear as soon as the scrub finishes, when that happens how would I determine that sdd was to blame without the kernel error log? # zpool status pool: tank state: ONLINE scan: scrub in progress since Thu Jul 25 16:38:01 2013 1.01T scanned out of 10.3T at 164M/s, 16h26m to go 1.40M repaired, 9.80% done config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sda ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 sdd ONLINE 0 0 0 (repairing) -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/