Help with Security Run Output

[Easygoer]

I am getting the following kernel log message from the security run output. I am certainly not an expert in FreeNAS and have no idea what it means.
I can only "speculate" that this has something to do with the HDD labelled ada0. Here are the details:

(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 10 00 63 40 8a 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 10 00 63 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 e8 df 96 40 8a 00 00 01 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 e8 df 96 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 e8 df 96 40 8a 00 00 01 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 e8 df 96 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 e8 df 96 40 8a 00 00 01 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 e8 df 96 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 50 e3 97 40 8a 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 50 e3 97 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 50 e3 97 40 8a 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 50 e3 97 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 50 e3 97 40 8a 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 50 e3 97 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 50 e3 97 40 8a 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 50 e3 97 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 d0 f9 97 40 8a 00 00 01 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 d0 f9 97 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 d0 fa 97 40 8a 00 00 01 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 d0 fa 97 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 d0 fb 97 40 8a 00 00 01 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 d0 fb 97 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 d0 fc 97 40 8a 00 00 01 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 d0 fc 97 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 58 65 9f 40 8a 00 00 01 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 58 65 9f 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 58 65 9f 40 8a 00 00 01 00 00
(ada0:ahcich0:0:0:0): CAM status: ATA Status Error
(ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada0:ahcich0:0:0:0): RES: 41 10 58 65 9f 40 8a 00 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
ahcich0: Timeout on slot 18 port 0
ahcich0: is 00000000 cs 00040000 ss 00000000 rs 00040000 tfd c0 serr 00000000 cmd 0004d217
(ada0:ahcich0:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Command timeout
(ada0:ahcich0:0:0:0): Retrying command
ahcich0: AHCI reset: device not ready after 31000ms (tfd = 00000080)
ahcich0: Timeout on slot 18 port 0
ahcich0: is 00000000 cs 00000000 ss 00000000 rs 00040000 tfd 150 serr 00000000 cmd 0004d217
(aprobe0:ahcich0:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ahcich0:0:0:0): CAM status: Command timeout
(aprobe0:ahcich0:0:0:0): Error 5, Retry was blocked

 

[m0nkey_]

Looks like device ada0 has failed / is failing. Recommend you replace it as soon as possible.

 

[Robert Trevellyan]

Yup. If you're lucky it could just be a loose or failing cable.

 

[Easygoer]

Thank you m0nkey_ and Robert_Trevellyan. Your input is much appreciated. Will be replacing the drive on Monday. I think I have some breathing room as I am using RaidZ2.

 

[Easygoer]

A follow up question....If I have not received any emails from my freeNAS server (about kernel log message from the security run output) over the last couple of days, does that mean that my drive is still good?.
I re-secured the cable connections to the drive(s).
So as Robert Trevellyan mentioned could it just be a loose cable?.
Thanks.

 

[SweetAndLow]

Run a smart long test on the drive Ave verify results.

 

[Robert Trevellyan]

could it just be a loose cable?

Could be.

By the way, what model are those Seagate 3TB drives?

 

[Easygoer]

Could be.

By the way, what model are those Seagate 3TB drives?

Model# ST3000DM001

 

[Easygoer]

Run a smart long test on the drive Ave verify results.

Thank You. Will be doing that sometime today.

 

[Robert Trevellyan]

ST3000DM001

That's what I was afraid you were going to say. That model has a reputation for early and sudden failure, so you should develop a plan to mitigate that risk.

 

[Easygoer]

That's what I was afraid you were going to say. That model has a reputation for early and sudden failure, so you should develop a plan to mitigate that risk.[/QUOTE
But the drive in question is the WD30EFRX....so I am really surprised. I had purchased the Seagate drives before I had readup on the WD Red drives. My bad.

So your suggestion would be to slowly upgrade to the WD reds eventually from the Seagate drives?.

 

[Robert Trevellyan]

the drive in question is the WD30EFRX

Yes, I just wanted to warn you of potential trouble in store.

Whether you start a process of gradual replacement (which could be larger drives) or just make sure you have spares on hand is up to you. Either way, this would be a good time to test your backups.

 

[Easygoer]

Yes, I just wanted to warn you of potential trouble in store.

Whether you start a process of gradual replacement (which could be larger drives) or just make sure you have spares on hand is up to you. Either way, this would be a good time to test your backups.

I recall reading somewhere in the posts that if you mix drives of different sizes then when you create the pool, the ZFS pool would be created based on the smallest drive sizes. So if I went with two larger drives (2x4TB), then my present pool size of 18TB (6x3TB) would remain the same instead of going up to 20TB (4x3TB + 2x4TB). I know i will end up getting less space eventually after I take into account the 2 disks for parity (Raid Z2).

 

[Robert Trevellyan]

I recall reading somewhere in the posts that if you mix drives of different sizes then when you create the pool, the ZFS pool would be created based on the smallest drive sizes.

Yes, that's true. I mentioned the possibility of larger drives as a long-term method of growing your pool (by replacing all 6 eventually), if that seems attractive.

The way I think of it is, when I need to replace one of my drives, I may as well get something significantly larger (at least 2x) than what I have now, even if I can't benefit from the extra space right away.

 

[Easygoer]

Yes, that's true. I mentioned the possibility of larger drives as a long-term method of growing your pool (by replacing all 6 eventually), if that seems attractive.

The way I think of it is, when I need to replace one of my drives, I may as well get something significantly larger (at least 2x) than what I have now, even if I can't benefit from the extra space right away.

Thanks Robert. Good point, did not think of it at first. It sure is good to think in those terms for the long term.