Error (benign?) in log when writing to disk

[paradoxiom]

I keep getting this spamming my log when transferring files to my external bay using CIFS, like so:

Code:

Aug 22 18:15:01 OrbitalHub autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "OrbitalHub/Jails@auto-20150822.1815-1d"
Aug 22 18:21:51 OrbitalHub smbd[34710]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to fetch record!
Aug 22 18:22:05 OrbitalHub smbd[34707]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionslimitingfactor (ipv4:192.168.1.180:58888) closed connection to service HubShare
Aug 22 18:24:53 OrbitalHub     (da3:mps0:0:6:0): WRITE(16). CDB: 8a 00 00 00 00 01 85 67 c7 c8 00 00 01 00 00 00 length 131072 SMID 108 terminated ioc 804b scsi 0 state c xfer 0
Aug 22 18:24:53 OrbitalHub (da3:mps0:0:6:0): READ(10). CDB: 28 00 d3 f9 cf 50 00 01 00 00
Aug 22 18:24:53 OrbitalHub (da3:mps0:0:6:0): CAM status: SCSI Status Error
Aug 22 18:24:53 OrbitalHub (da3:mps0:0:6:0): SCSI status: Check Condition
Aug 22 18:24:53 OrbitalHub (da3:mps0:0:6:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Aug 22 18:24:53 OrbitalHub (da3:mps0:0:6:0): Retrying command (per sense data)
Aug 22 18:24:54 OrbitalHub (da3:mps0:0:6:0): WRITE(16). CDB: 8a 00 00 00 00 01 85 69 41 c0 00 00 01 00 00 00
Aug 22 18:24:54 OrbitalHub (da3:mps0:0:6:0): CAM status: SCSI Status Error
Aug 22 18:24:54 OrbitalHub (da3:mps0:0:6:0): SCSI status: Check Condition
Aug 22 18:24:54 OrbitalHub (da3:mps0:0:6:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Aug 22 18:24:54 OrbitalHub (da3:mps0:0:6:0): Retrying command (per sense data)
Aug 22 18:25:10 OrbitalHub     (da3:mps0:0:6:0): WRITE(16). CDB: 8a 00 00 00 00 01 85 8f eb b8 00 00 01 00 00 00 length 131072 SMID 554 terminated ioc 804b scsi 0 state c xfer 0
Aug 22 18:25:10 OrbitalHub (da3:mps0:0:6:0): WRITE(16). CDB: 8a 00 00 00 00 01 85 8f eb b8 00 00 01 00 00 00
Aug 22 18:25:10 OrbitalHub (da3:mps0:0:6:0): CAM status: SCSI Status Error
Aug 22 18:25:10 OrbitalHub (da3:mps0:0:6:0): SCSI status: Check Condition
Aug 22 18:25:10 OrbitalHub (da3:mps0:0:6:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Aug 22 18:25:10 OrbitalHub (da3:mps0:0:6:0): Retrying command (per sense data)
Aug 22 18:25:10 OrbitalHub (da3:mps0:0:6:0): READ(10). CDB: 28 00 d3 fa 40 60 00 01 00 00
Aug 22 18:25:10 OrbitalHub (da3:mps0:0:6:0): CAM status: SCSI Status Error
Aug 22 18:25:10 OrbitalHub (da3:mps0:0:6:0): SCSI status: Check Condition
Aug 22 18:25:10 OrbitalHub (da3:mps0:0:6:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Aug 22 18:25:10 OrbitalHub (da3:mps0:0:6:0): Retrying command (per sense data)

Bigger log here

When reading files from the drive in the bay with the errors, those messages don't appear - also when playing those files in Plex, no errors, only when writing to that specific drive in the bay. It doesn't happen when writing to any of my other drives, just the one in that external bay.

I thought it might be a power issue so I bought a cheap Corsair PSU and used that, but I still get the messages.

https://imgur.com/a/QIfbv#0

Pictures showing the external drive bay and the PSU powering it.

 

[dlavigne]

Were you able to find an answer for this?

 

[SweetAndLow]

Hardware and freenas version

 

[danb35]

Hardware and FreeNAS version are in OP's sig:
Base - HP ProLiant Gen8 MicroServer
CPU - Xeon E3-1230 v2 @ 3.3GHz
RAM - 2x 8GB Kingston DDR3 1600MHz ECC DIMM
OS - FreeNAS 9.3

Granted, it doesn't give the exact FreeNAS build number, but at least the base version is there.

 

[SweetAndLow]

well at one point this user was using nightly builds and running the p20 firmware. I suspect it's related to that so I wanted to know what they have configured right now.

 

[paradoxiom]

well at one point this user was using nightly builds and running the p20 firmware. I suspect it's related to that so I wanted to know what they have configured right now.

the same, and still experience the same when writing files to that drive bay

 

[Robert Trevellyan]

Precisely what hardware is between the mobo and the drive in question?

What do SMART tests and logs show for that drive?

 

[paradoxiom]

HP Gen8 -> IBM M1015 Card -> Icy Dock (DataCage Classic MB454SPF-B)

The drive is alone in the bay in a single zpool. It has been scrubbed twice I think and 0 errors found, as for smart tests/logs, what/where/how exactly should I perform these tests and get the results? I mean, all the drives including that one have smart enabled and have scheduled short and long smart tests, 6 short schedules tests per month and 1 long.

 

[SweetAndLow]

I vote that the icydock is bad. Can you try removing it to see if things get better.

 

[paradoxiom]

I vote that the icydock is bad. Can you try removing it to see if things get better.

If you mean that particular dock, it's not, I had another one prior and I returned it for a replacement because I thought it was bad but the error persisted.

 

[Robert Trevellyan]

how exactly should I perform these tests and get the results?

If scheduled tests are running, then just use smartctl at the command-line to get the logs, preferably via SSH so it's easier to copy/paste (or you can redirect it to a file). Paste the output between CODE tags to preserve formatting.

 

[paradoxiom]

da3 is the drive in the Icy Dock

Code:

[root@OrbitalHub] ~# smartctl -a /dev/da3
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p25 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD60EFRX-68MYMN1
Serial Number:    WD-WX21D45C7ZSV
LU WWN Device Id: 5 0014ee 2b6d67556
Firmware Version: 82.00A82
User Capacity:    6,001,175,126,016 bytes [6.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5700 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Sep 11 17:33:33 2015 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                ( 4604) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 700) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x303d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   199   197   021    Pre-fail  Always       -       9008
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       24
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       716
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       24
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       22
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       814
194 Temperature_Celsius     0x0022   120   115   000    Old_age   Always       -       32
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       30
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%       700         -
# 2  Short offline       Completed without error       00%       580         -
# 3  Short offline       Completed without error       00%       437         -
# 4  Short offline       Completed without error       00%       317         -
# 5  Short offline       Completed without error       00%       198         -
# 6  Short offline       Completed without error       00%        78         -
# 7  Extended offline    Completed without error       00%        67         -

SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

 

[SweetAndLow]

You have some kind of communication problem between your controller and disk. I still think it's the dock thing you have and you should remove it.

 

[Robert Trevellyan]

OK, nothing obviously wrong with the drive. A drive can be flaky and show nothing in SMART, but assuming that's not the case, it has to be, uh, something else.

I know you're on your 2nd cage, but it's either that, or the data cable, or power.

EDIT: or the mobo, I guess. I'm with @SweetAndLow as far as what seems most likely.

 

[paradoxiom]

OK, nothing obviously wrong with the drive. A drive can be flaky and show nothing in SMART, but assuming that's not the case, it has to be, uh, something else.

I know you're on your 2nd cage, but it's either that, or the data cable, or power.

The cable is a simple, new, SAS cable (this exact one) no obvious creases or breaks in the cable, and I use an identical one in the other port on my M1015.

I thought it was power too, which is why I bought an extra PSU to power the Icy Dock as you can see in the image album from the first post.

The backplane on the dock is quite simple, the SAS cable just plugs directly into it like so. This is before I purchased the extra PSU to power it.

You have some kind of communication problem between your controller and disk. I still think it's the dock thing you have and you should remove it.

If I remove the dock I lose the HDD that is in there and the data on there.. I kind of need it. I mean, it's full of 6TB of data.

Do either of you understand or can interpret those errors from my first post at all or are we all just playing the guessing game here?

Like I said in the first post, it only happens when transferring files *to* the drive, copying them back over or reading from it eg; playing a Plex file from it, no errors like that in the log.

Anyway like I say, the drive is almost full now and I still get that error filling my log when I transfer files to it, but so far it seems to be a harmless error as everything else with it works fine.

I thought it might have something to do with using v20 of the IBM M1015 firmware (IT-Mode) and not v16 but I wouldn't know anything about that.

 

[Robert Trevellyan]

I thought it was power too, which is why I bought an extra PSU to power the Icy Dock as you can see in the image album from the first post.

The links in your first post didn't work for me.

If I remove the dock I lose the HDD that is in there and the data on there.

You should be able to at least test it without the dock by connecting the bare drive, with some kind of cooling airflow directed at it.

Do either of you understand or can interpret those errors from my first post at all or are we all just playing the guessing game here?

In the time I've spent in these forums, both lurking and later participating, I've seen enough threads discussing CAM status errors to be confident of the diagnosis. It's also pretty explicit at times, e.g. SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)

 

[Arwen]

My vote would be the cable and disk chassis.
They are both internal models, used externally.

That said, it should work. But I have seen in other cases where a cable picks up
noise in one direction only. Read traffic uses transmitters from the drive and one
pair of wires in the cable. Write traffic uses transmitters from the HBA and a
different pair of wires in the cable.

So, as a test, use one of the following;

• Shorter cable
• Different chassis
• Different HBA
• eSATA port

 

[paradoxiom]

My vote would be the cable and disk chassis.
They are both internal models, used externally.

That said, it should work. But I have seen in other cases where a cable picks up
noise in one direction only. Read traffic uses transmitters from the drive and one
pair of wires in the cable. Write traffic uses transmitterss from the HBA and a
different pair of wires in the cable.

So, as a test, use one of the following;

• Shorter cable
• Different chassis
• Different HBA
• eSATA port

Yeah I don't have most of those things so I guess I'll just leave it since there's no problem actually happening and nobody even knows what the errors mean anyway and are just guessing still.

Thanks for trying to help anyway.

 

[Arwen]

Yeah I don't have most of those things so I guess I'll just leave it since there's no problem actually happening and nobody even knows what the errors mean anyway and are just guessing still.

Thanks for trying to help anyway.

Sorry, I did not realize you needed an more complete definition for this error;

SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)

From what I can tell, (and having close to 33 years experience with SCSI), is that the SATA, (aka SCSI), bus reset
due to signal failure. Meaning too much noise on the line, (can't tell in which direction without more study), casued
a packet to fail. Since the protocol is designed for retries, (both reads and writes can be retried easily), the packet is
retried successfully another time.

If single packet, (aka disk blocks), gets too many retries, then you get an un-recoverable read or write error. Even
with good disks. But in your case, if you don't get too many, then you can ignore it. Statistically you will likely get
an un-recoverable error eventually. How easily you can manually recover, I don't know.

On rare occasions this can be due to a mis-match between Host Bus Adapter card's firmware and OS driver.