SOLVED CAM Errors

Status
Not open for further replies.

gareththered

Cadet
Joined
Sep 8, 2017
Messages
2
My dmesg shows the following (extract):

Code:
(ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 a0 9e 50 40 5d 01 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: 40 (UNC )
(ada0:ahcich0:0:0:0): RES: 41 40 b0 9e 50 40 5d 01 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 a0 9e 50 40 5d 01 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: 40 (UNC )
(ada0:ahcich0:0:0:0): RES: 41 40 b0 9e 50 40 5d 01 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 a0 9e 50 40 5d 01 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: 40 (UNC )
(ada0:ahcich0:0:0:0): RES: 41 40 b0 9e 50 40 5d 01 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 a0 9e 50 40 5d 01 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: 40 (UNC )
(ada0:ahcich0:0:0:0): RES: 41 40 b0 9e 50 40 5d 01 00 00 00
(ada0:ahcich0:0:0:0): Retrying command
(ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 a0 9e 50 40 5d 01 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: 40 (UNC )
(ada0:ahcich0:0:0:0): RES: 41 40 b0 9e 50 40 5d 01 00 00 00
(ada0:ahcich0:0:0:0): Error 5, Retries exhausted



However, smartctl -a /dev/ada0 shows no errors. I've ran a short and a conveyance test on the disk and no errors are shown.

This is on a Proliant Microserver Gen8 with 2 x 3TB and 2 x 1TB Western Digital disks. The error refers to one of the 3TB disks. FreeNAS is running with 12GB RAM.

Should I be worried about the messages, given that there are no SMART errors?
 

m0nkey_

MVP
Joined
Oct 27, 2015
Messages
2,739
Welcome to the forums :)

This is typically indicative of a bad cable (SATA or power). If smartctl is not showing any errors and you're running regular short and long SMART tests then it's the most likely cause.
 

Nicholas

Dabbler
Joined
Dec 31, 2013
Messages
13
Hi all, think i have the same problem here.
Could you please tell me how to run the smartctl check?

Thanks in advance.
66cca40cb088d8ac814556ce9751d57e.jpg


Enviado desde mi Nexus 5X mediante Tapatalk
 

m0nkey_

MVP
Joined
Oct 27, 2015
Messages
2,739
Hi all, think i have the same problem here.
Could you please tell me how to run the smartctl check?
Have you tried doing the same? Replace the cable for ada1. Also, suggest you create your own thread instead of hijacking this one.
 

Nicholas

Dabbler
Joined
Dec 31, 2013
Messages
13
Have you tried doing the same? Replace the cable for ada1. Also, suggest you create your own thread instead of hijacking this one.
yes i've tried replacing the sata cable, but didn't worked.
So i'd like to discard the faulty disk option.

Enviado desde mi Nexus 5X mediante Tapatalk
 
Status
Not open for further replies.
Top