SOLVED Dying Drive?

[nello]

I presume it's time to replace the drive

OctoberGroupNAS.local kernel log messages:
> (ada1:ahcich1:0:0:0): RES: 41 40 70 cc c7 40 e9 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 10 c0 9a 59 40 b1 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 c0 9a 59 40 b1 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 b8 51 6d 40 67 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 70 52 6d 40 67 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 b8 83 6d 40 67 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 b8 83 6d 40 67 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 b0 e2 69 40 66 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 b0 e2 69 40 66 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 80 38 7e df 40 67 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 38 7e df 40 67 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 80 b0 7c e0 40 67 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 b0 7c e0 40 67 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 78 f6 01 40 68 00 00 01 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 78 f6 01 40 68 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 e0 f5 02 40 68 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 e0 f5 02 40 68 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 88 fa 02 40 68 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 88 fa 02 40 68 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 30 fa 01 40 8b 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 30 fa 01 40 8b 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 30 fa 01 40 8b 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 30 fa 01 40 8b 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 d8 2b 05 40 8b 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 d8 2b 05 40 8b 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 f0 e2 b0 40 00 01 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 f0 e2 b0 40 00 01 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 f0 e2 b0 40 00 01 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 f0 e2 b0 40 00 01 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 c8 e7 d4 40 a3 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 c8 e7 d4 40 a3 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 50 a1 27 40 68 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 50 a1 27 40 68 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 a0 55 ee 40 8d 00 00 01 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 a8 55 ee 40 8d 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 f8 a3 55 40 8e 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 90 a4 55 40 8e 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 a0 89 08 40 a5 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 a0 89 08 40 a5 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 f0 70 1d 40 66 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 f0 70 1d 40 66 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 e0 8f 56 40 d7 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 e0 8f 56 40 d7 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 68 95 c5 40 5d 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 68 95 c5 40 5d 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 68 95 c5 40 5d 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 68 95 c5 40 5d 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 c0 47 21 40 01 01 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 c0 47 21 40 01 01 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 f0 4e 95 40 61 00 00 00 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 41 40 f8 4e 95 40 61 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_DMA48. ACB: 25 00 f0 2e bd 40 61 00 00 00 40 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada1:ahcich1:0:0:0): RES: 51 40 28 2f bd 40 61 00 00 00 00
> (ada1:ahcich1:0:0:0): Retrying command
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 70 32 d5 40 5f 00 00 01 00 00
> (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
> (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )

...

> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 98 f6 cc 40 08 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 98 f6 cc 40 08 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 70 cc e7 40 08 01 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 70 cc e7 40 08 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 78 f1 4b 40 0a 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 78 f1 4b 40 0a 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 28 58 f9 71 40 09 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 58 f9 71 40 09 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 88 8f 4d 40 0a 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 e0 8f 4d 40 0a 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 60 c6 c1 40 a4 00 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 60 c6 c1 40 a4 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 e0 6d 01 40 68 00 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 e0 6d 01 40 68 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 90 51 28 40 0b 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 90 51 28 40 0b 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 f8 80 fb 0a 40 cd 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 98 fb 0a 40 cd 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 d8 6b 1a 40 0e 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 d8 6b 1a 40 0e 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 30 a0 46 40 d3 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 30 a0 46 40 d3 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 90 f4 af 40 0f 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 90 f4 af 40 0f 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 c8 4d c1 40 d3 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 c8 4d c1 40 d3 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 b0 41 05 40 d3 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 b0 41 05 40 d3 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 98 38 84 84 40 d4 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 80 84 84 40 d4 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 88 01 e6 40 f5 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 88 01 e6 40 f5 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 90 75 c2 40 55 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 98 75 c2 40 55 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 30 90 05 14 40 56 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 90 05 14 40 56 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 c0 b9 f1 40 88 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 c0 b9 f1 40 88 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 d8 bc cd 40 56 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 d8 bc cd 40 56 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 70 1a b1 40 88 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 70 1a b1 40 88 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 d0 7e bf 40 8a 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 38 7f bf 40 8a 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 28 25 69 40 88 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 30 25 69 40 88 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 40 e5 0a 40 8a 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 40 e5 0a 40 8a 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 e0 6c 0c 40 8a 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 e0 6c 0c 40 8a 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 b8 a4 c5 40 59 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 c0 a4 c5 40 59 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 f8 9e c5 40 59 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 f8 9e c5 40 59 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 f8 9e c5 40 59 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 f8 9e c5 40 59 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 10 aa c4 40 59 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 10 aa c4 40 59 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 80 90 40 0d 40 d0 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 90 40 0d 40 d0 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 f0 32 96 40 58 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 f0 32 96 40 58 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 f0 32 96 40 58 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 f0 32 96 40 58 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 10 40 e2 40 58 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 48 40 e2 40 58 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 08 56 29 40 ce 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 08 56 29 40 ce 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 f0 23 0b 40 cf 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 f0 23 0b 40 cf 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 80 5e 59 40 1e 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 80 5e 59 40 1e 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 d0 a5 db 40 1e 01 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 d0 a5 db 40 1e 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 30 a6 b3 40 b0 00 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 30 a6 b3 40 b0 00 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a0 a0 d3 f5 40 1e 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 e8 d3 f5 40 1e 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 d0 4e d9 40 1d 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 d0 4e d9 40 1d 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 80 92 d7 40 1c 01 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 80 92 d7 40 1c 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 b0 14 0b 40 1d 01 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 b0 14 0b 40 1d 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 c8 d9 d6 40 1b 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 c8 d9 d6 40 1b 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 c8 d9 d6 40 1b 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 c8 d9 d6 40 1b 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 68 89 66 40 12 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 a8 89 66 40 12 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 38 23 f0 40 10 01 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 48 23 f0 40 10 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 30 72 d8 40 10 01 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 78 72 d8 40 10 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 f0 41 ac 40 11 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 f0 41 ac 40 11 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 a0 17 19 40 12 01 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 b0 17 19 40 12 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 a0 54 82 40 12 01 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 68 55 82 40 12 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 10 e4 e6 40 05 01 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 50 e4 e6 40 05 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 40 18 22 ea 40 05 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 18 22 ea 40 05 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 80 60 19 69 40 07 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 60 19 69 40 07 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 b0 6d 58 40 1e 01 00 01 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 e0 6d 58 40 1e 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 c0 50 8e 3f 40 1c 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 b0 8e 3f 40 1c 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 80 58 01 35 40 15 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 58 01 35 40 15 01 00 00 00
> (ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 08 d0 0f 40 20 01 00 00 00 00
> (ada1:ahcich1:0:0:0): RES: 41 40 08 d0 0f 40 20 01 00 00 00

-- End of security output --

 

[anodos]

I presume it's time to replace the drive

Yup. Be sure to follow the proper procedure http://doc.freenas.org/9.3/freenas_storage.html#replacing-a-failed-drive. Make sure you have smart monitoring configured if you haven't yet.

 

[nello]

Yup. Be sure to follow the proper procedure http://doc.freenas.org/9.3/freenas_storage.html#replacing-a-failed-drive.

Thank you; I was looking for that!

Make sure you have smart monitoring configured if you haven't yet.

I thought I did have it on; would you please send me a link on how to do it so that I get it right this time?

Thank you!

 

[BigDave]

http://doc.freenas.org/9.3/freenas_services.html?highlight=smart#s-m-a-r-t

 

[nello]

http://doc.freenas.org/9.3/freenas_services.html?highlight=smart#s-m-a-r-t

Yes, I thought that I had configured this correctly:

And yes, I had SMART turned on:

But I didn't get a SMART error (despite or in addition to the security log bad-sector errors).

Perhaps I'm misunderstanding how SMART reporting works.

 

[solarisguy]

In case you did not replace the drive, from an SSH session you may want to execute
smartctl -a /dev/ada1

 

[Robert Trevellyan]

Perhaps I'm misunderstanding how SMART reporting works.

Looks like you have 2 pieces of the puzzle in place. The 3rd piece is email reporting. Email sending is under System | Email, and you need a recipient email address in the SMART service settings.

 

[nello]

Yes, I have the 3rd piece already in place:

And when I click the "Send Test Mail" button I receive the test message.

Any other ideas to explain why SMARTd didn't send me a warning that my drive was failing?

- nello

 

[nello]

Looks like you have 2 pieces of the puzzle in place. The 3rd piece is email reporting.

Is there a 4th piece?

Does a SMART Test task need to be configured?
http://doc.freenas.org/9.3/freenas_tasks.html#index-3

- nello

 

[Robert Trevellyan]

Is there a 4th piece?

For the SMART checks, the email has to be set in the SMART service settings. I was thinking of that as integral to the 3rd piece.

Does a SMART Test task need to be configured?

It's confusing, isn't it?

SMART checks and SMART tests are quite different. The former checks the drive's self-monitoring data for signs of problems, is managed through the SMART Service, and defaults to every 30 minutes. The latter initiates self-tests, which either pass or fail, is managed through the SMART Task, and should be run anywhere from daily to weekly for the short version, and weekly to monthly for the extended version. Both are important for the long-term health of your data.

I assume you already set up an email address for the root user. That's the destination for the daily security run output, which is where I think you should have been notified of the errors you saw. By the way, those errors might indicate a problem with the drive, but might also indicate problems with a cable, or a controller. The only way to know for sure it to check everything, step by step. Start with the smartctl output, as suggested, and go from there.

 

[nello]

For the SMART checks, the email has to be set in the SMART service settings.

Yes, I had an email address in the SMART Service:

… self-tests, which either pass or fail, is managed through the SMART Task, and should be run anywhere from daily to weekly for the short version, and weekly to monthly for the extended version.

Okay, I set this up

I assume you already set up an email address for the root user. That's the destination for the daily security run output, which is where I think you should have been notified of the errors you saw.

Yes, I have email configured for root and yes the daily Security report is where I saw the errors.

By the way, those errors might indicate a problem with the drive, but might also indicate problems with a cable, or a controller. The only way to know for sure it to check everything, step by step. Start with the smartctl output, as suggested, and go from there.

I've already removed the drive and setup an RMA for it so I won't be running smartctl on this drive; but it's a good suggestion for the next time I get errors.

Thank you for bearing with me and all my questions.

- nello

 

[joeschmuck]

It would be nice if all this SMART stuff came pre-configured to be automatically ON and some default testing established and a warning message to ensure you set up email messages. Hey, this could be a feature request. But if some of these folks recall, FreeNAS was never intended for someone who wasn't willing to get into the operations and make the sacrifice to learn it all. It's not a plug-in-play system although everyone would like it to be that. I think it's getting closer to that day by day.

 

[joeschmuck]

Okay, I set this up

I'd setup the Short tests to run at 1AM and the long Tests to run maybe at 1:10AM. This circumvents any issues where a long test takes longer than 2 hours and then you try to start a short test.

 

[Robert Trevellyan]

the daily Security report is where I saw the errors.

Seems like it worked as intended.

I set this up

I suggest switching the scheduled hours for long and short, unless you have other factors in play, e.g. scrubs. Your weekly long tests may not finish in time for your daily short tests, which I believe will preempt them, but only take minutes, not hours.

For what it's worth, I do weekly short SMART self-tests and monthly extended SMART self-tests, but others differ, so it's your call. I'm at the less frequent end of the spectrum. Sometimes people are doing the short tests hourly, which is silly.

 

[danb35]

Sometimes people are doing the short tests hourly, which is silly.

Not only are hourly short tests completely unnecessary, they also mean that any information about the long tests will scroll out of your log within a day. The SMART self-test log only stores 21 entries (which seems a rather odd number to me, but there it is), so after 21 hours the short tests are all that would appear. I suspect the people who have these settings, have them because they've misunderstood how the scheduling window works (and in their defense, it is kind of a busy window).

I do short daily, and long weekly, but recognize that's on the frequent side of "normal".

 

[anodos]

Not only are hourly short tests completely unnecessary, they also mean that any information about the long tests will scroll out of your log within a day. The SMART self-test log only stores 21 entries (which seems a rather odd number to me, but there it is), so after 21 hours the short tests are all that would appear. I suspect the people who have these settings, have them because they've misunderstood how the scheduling window works (and in their defense, it is kind of a busy window).

I do short daily, and long weekly, but recognize that's on the frequent side of "normal".

For what it's worth, I do short every three days and long tests twice per month.

 

[joeschmuck]

I do short daily, and long weekly, but recognize that's on the frequent side of "normal".

What is considered normal? I think that we are defining the normal here and we both test what feels appropriate for our systems. I really think that weekly testing is not abusive to the drive for the amount of usage it gets in my home system. If my system were a highly accessed data server where the drives were being slammed around all the time reading and writing lots of data, I'd reduce the Long test to possibly once a month since I'd expect under normal use under that kind of workload would read or write to almost all the sectors on the drive thus effectively doing what a long test would do anyway with reading the entire surface, however to ensure the entire surface does get read periodically the long test must be run.

So we set the normal here and for a home system, I feel our settings are very reasonable.

 

[solarisguy]

Off-topic?

FreeNAS could be shipping with a short test running weekly

 

[danb35]

I'm using "normal" descriptively. Purely based on what I've seen posted here, short daily/long weekly is about the most frequent I've seen recommended, and short weekly/long monthly about the least.

 

[joeschmuck]

Created a Feature Request to make it a pre-configured option.