CAM status: SCSI Status Error

Status
Not open for further replies.

Cougar014

Explorer
Joined
Oct 30, 2016
Messages
57
Hi guys,

About once a week i recieve the email (posted below) from the daily security run output.
I am just wondering if this is something bad and really is hurting my system or if it is just a timeout which doesn't hurt that much?
I believe it is an error from one of the boot drives, but I am not 100% sure.
I have 2 SSD's in a mirror setup as boot drive for Freenas.

I was hoping that the last update from about 2-3 weeks ago would fix something about this, but I got unlucky and just received one once again.

Most of this stuff happens overnight.

Can someone please shine a light on this about what to do with it?

Thanks in advance,

Email:
freenas.local kernel log messages:
(da1:mpr0:0:5:0): WRITE(10). CDB: 2a 00 02 1b 16 40 00 00 18 00
(da1:mpr0:0:5:0): CAM status: SCSI Status Error
(da1:mpr0:0:5:0): SCSI status: Check Condition
(da1:mpr0:0:5:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
(da1:mpr0:0:5:0): Retrying command (per sense data)
(da1:mpr0:0:5:0): WRITE(10). CDB: 2a 00 02 1b db 10 00 00 08 00
(da1:mpr0:0:5:0): CAM status: SCSI Status Error
(da1:mpr0:0:5:0): SCSI status: Check Condition
(da1:mpr0:0:5:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
(da1:mpr0:0:5:0): Retrying command (per sense data)

-- End of security output --
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,996
Power down your box and replace the SATA cable for da1. (use the drive serial number to identify da1) See if this helps. If not, swap to a different power connector.

Next time you have a question, please follow our forum rules and post the FreeNAS software you are using and your hardware specs. Thankfully your problem is typically just a cable issue.
 

Cougar014

Explorer
Joined
Oct 30, 2016
Messages
57
Thanks for the answer.
I have it on a 4-sata connector mini-SAS cable on a 2 HDD setup. I will try to switch da1 to another connector and see if this will fix the issue.
Sorry about the limited information, i will keep it in mind!
 
Status
Not open for further replies.
Top