CAM Status & Scsi Status errors

[mothball]

I have begun to experience a consistent errors of the following nature:

Code:

Jun 16 12:14:31 12Colonies (da7:mps0:0:8:0): READ(10). CDB: 28 00 05 22 15 30 00 00 08 00
Jun 16 12:14:31 12Colonies (da7:mps0:0:8:0): CAM status: SCSI Status Error
Jun 16 12:14:31 12Colonies (da7:mps0:0:8:0): SCSI status: Check Condition
Jun 16 12:14:31 12Colonies (da7:mps0:0:8:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected)
Jun 16 12:14:31 12Colonies (da7:mps0:0:8:0): Retrying command (per sense data)
Jun 16 12:14:35 12Colonies (da7:mps0:0:8:0): READ(10). CDB: 28 00 93 8b bf 98 00 00 08 00
Jun 16 12:14:35 12Colonies (da7:mps0:0:8:0): CAM status: SCSI Status Error
Jun 16 12:14:35 12Colonies (da7:mps0:0:8:0): SCSI status: Check Condition
Jun 16 12:14:35 12Colonies (da7:mps0:0:8:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected)
Jun 16 12:14:35 12Colonies (da7:mps0:0:8:0): Retrying command (per sense data)
Jun 16 12:14:38 12Colonies (da7:mps0:0:8:0): READ(10). CDB: 28 00 5b 96 16 78 00 00 08 00
Jun 16 12:14:38 12Colonies (da7:mps0:0:8:0): CAM status: SCSI Status Error
Jun 16 12:14:38 12Colonies (da7:mps0:0:8:0): SCSI status: Check Condition
Jun 16 12:14:38 12Colonies (da7:mps0:0:8:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected)
Jun 16 12:14:38 12Colonies (da7:mps0:0:8:0): Retrying command (per sense data)
Jun 16 12:14:47 12Colonies (da7:mps0:0:8:0): READ(10). CDB: 28 00 93 83 83 18 00 00 08 00
Jun 16 12:14:47 12Colonies (da7:mps0:0:8:0): CAM status: SCSI Status Error
Jun 16 12:14:47 12Colonies (da7:mps0:0:8:0): SCSI status: Check Condition
Jun 16 12:14:47 12Colonies (da7:mps0:0:8:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected)
Jun 16 12:14:47 12Colonies (da7:mps0:0:8:0): Retrying command (per sense data)
Jun 16 12:41:05 12Colonies smartd[3437]: Device: /dev/da7 [SAT], ATA error count increased from 14 to 47
undefined

i found a similar post from a few years ago that requested the person run the following tests
zpool status
smartctl -a
smartctl -x
sas2flash

i am attaching the results of these test to the posts

the drive was recently replaced with a new fresh from the box 4tb Hitachi Deskstar NAS. So drive failure doesnt seem to make a whole lot of sense to me. Has anyone experienced this problem with failing SAS/ SATA server backplanes?

thanks
Scott

 

[Chris Moore]

Please provide hardware details, following the guidance:
https://www.ixsystems.com/community/threads/forum-guidelines.45124

 

[Chris Moore]

Code:

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     PO-R--   100   100   016    -    0
  2 Throughput_Performance  P-S---   100   100   054    -    0
  3 Spin_Up_Time            POS---   100   100   024    -    0
  4 Start_Stop_Count        -O--C-   100   100   000    -    2
  5 Reallocated_Sector_Ct   PO--CK   100   100   005    -    0
  7 Seek_Error_Rate         PO-R--   100   100   067    -    0
  8 Seek_Time_Performance   P-S---   100   100   020    -    0
  9 Power_On_Hours          -O--C-   100   100   000    -    6
 10 Spin_Retry_Count        PO--C-   100   100   060    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    2
192 Power-Off_Retract_Count -O--CK   100   100   000    -    2
193 Load_Cycle_Count        -O--C-   100   100   000    -    2
194 Temperature_Celsius     -O----   139   139   000    -    43 (Min/Max 25/47)
196 Reallocated_Event_Count -O--CK   100   100   000    -    0
197 Current_Pending_Sector  -O---K   100   100   000    -    0
198 Offline_Uncorrectable   ---R--   100   100   000    -    0
199 UDMA_CRC_Error_Count    -O-R--   197   197   000    -    47

The UDMA_CRC_Error_Count fault is usually a cabling problem, not a drive problem. It is always best to ask first.

 

[Chris Moore]

Code:

pool: virgon
state: ONLINE
scan: resilvered 949G in 0 days 03:46:23 with 0 errors on Sun Jun 16 01:41:10 2019
config:
NAME                                            STATE     READ WRITE CKSUM
virgon                                      ONLINE       0     0     0
raidz1-0                                    ONLINE       0     0     0
gptid/047f14fe-5a0c-11e6-a314-4ccc6a03f387  ONLINE       0     0     0
gptid/64958d6b-8ff2-11e9-a2f5-4ccc6a03f387  ONLINE       0     0     0
gptid/060dafef-5a0c-11e6-a314-4ccc6a03f387  ONLINE       0     0     0
gptid/08566760-5a0c-11e6-a314-4ccc6a03f387  ONLINE       0     0     0
gptid/09fbdb1e-5a0c-11e6-a314-4ccc6a03f387  ONLINE       0     0     0
errors: No known data errors

RAIDz1 is not suggested with 4TB drives. You should read these resources:

Slideshow explaining VDev, zpool, ZIL and L2ARC
https://www.ixsystems.com/community...ning-vdev-zpool-zil-and-l2arc-for-noobs.7775/

Overview of ZFS Pools in FreeNAS from the iXsystems blog:
https://www.ixsystems.com/blog/zfs-pools-in-freenas/

Terminology and Abbreviations Primer
https://www.ixsystems.com/community/threads/terminology-and-abbreviations-primer.28174/

Why not to use RAID-5 or RAIDz1
https://www.zdnet.com/article/why-raid-5-stops-working-in-2009/

 

[mothball]

thanks Chris appreciate the feedback - when you see this type of error could it be the backplane hardware failing or is it it the actual cable?

FreeNas Box
MSI 970A-G43 PLUS
AMD FX 8320 8 core processor
16 gb ram
9 hard drives of various sizes and models
SANDISK 16gb USBKEY Drive boot device
Recommended LSI HBA adapter

 

[Chris Moore]

thanks Chris appreciate the feedback - when you see this type of error could it be the backplane hardware failing or is it it the actual cable?

FreeNas Box
MSI 970A-G43 PLUS
AMD FX 8320 8 core processor
16 gb ram
9 hard drives of various sizes and models
SANDISK 16gb USBKEY Drive boot device
Recommended LSI HBA adapter

Not to say it is impossible to be in the backplane, but I have most often seen it in a cable. Usually physical damage to a cable. I had one that got pinched and only affected one of the four lanes in a SAS forward breakout cable.

 

[mothball]

thanks - i think cabling is probably old enough to deserve a refresh and if it still occurs it would seem to indicate it could be the backplane as the culprit

 

[Chris Moore]

thanks - i think cabling is probably old enough to deserve a refresh and if it still occurs it would seem to indicate it could be the backplane as the culprit

You might try unplug and re-plug the cables first. If the system has been running for a long time, sometimes the connections become 'loose' over time. It might be worth a try.

 

[mothball]

Follow up if you don't mind - i determined it was the case backplane - swapped for new cables and changed a drive and still had the same problem. I happened to have an under used Supermicro case so I swapped all the drives into this case and voila no more cam/scsi errors. But a new issue has cropped up it seems that the Samba shares i created are not visible over the network, FTP works, the Emby Server I have loaded work. I keep getting this message:

Code:

 smbd dnssd_clientstub ConnectToServer: connect()-> No of tries: 1

Any sense of what could be going on here?

 

[Chris Moore]

Any sense of what could be going on here?

Still on the same system board / network controller?

 

[mothball]

actually - I left my the existing board in the new case in place, it contains an MSI 970 GAMING MB, AMD FX-6100 6 core processor, and Killer E2205 Gigabit LAN controller - 16gb ram.

I reinstalled the latest version of freenas FreeNAS-11.2-U4.1 when i migrated the disks over. Usually i don't have any problem with Samba shares simply using the default settings, setting up the shares and configuring the service. they are all set on guest mode /no login as they serve media streaming for the home network (firewalled)... Funny thing - i was able to access the shares via VLC app on my Amazon Fire cube earlier - have to double check if it was smb or ftp though - clearly i am not able to access via my windows boxes or my ubuntu boxes...

if i need to i can swap to the motherboard from the bad case - i was trying the save myself some time...

thanks for the help btw...