Burn in test error

[Dave Hob]

Hi

I am running this burn in test, following the tutorial on this forum

The hdd is a 3TB WD30EFRX Nas 2.0. Believe it or not it is a brand new disk that I bought a few years back and didn't get a chance to put together a system with yet.

The exact model is: WD30EFRX-68EUZN0

When I run badblocks command after about 1h I get this error on one of the drives every second pretty much that creates probably tens of thousands of errors on it:

Mar 8 05:20:13 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 06 0e 00 00 01 00 00
Mar 8 05:20:13HRetrying(da5:mps0:0:5:0): CAM status: SCSI Status Error
Mar 8 05:20:1343HCAM st(da5:mps0:0:5:0): SCSI status: Check Condition
Mar 8 05:20:139;43HSCSI(da5:mps0:0:5:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 8 05:20:13;43HRetry(da5:mps0:0:5:0): Retrying command (per sense data)
Mar 8 05:20:1425H(da5:m (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 09 47 00 00 01 00 00 length 131072 SMID 364 terminated ioc 804b loginfo 31110d01 scsi 0 state c xfer 0
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 09 47 00 00 01 00 00
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): CAM status: CCB request completed with an error
Mar 8 05:20:14;25H (da5:mps0:0:5:0): Retrying command
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 09 47 00 00 01 00 00
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): CAM status: SCSI Status Error
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): SCSI status: Check Condition
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): Retrying command (per sense data)
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 0b 16 00 00 01 00 00 length 131072 SMID 168 terminated ioc 804b loginfo 31110d01 scsi 0 state c xfer 0
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 0b 16 00 00 01 00 00
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): CAM status: CCB request completed with an error
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): Retrying command
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 0b 16 00 00 01 00 00
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): CAM status: SCSI Status Error
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): SCSI status: Check Condition
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): Retrying command (per sense data)
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 0c 7c 00 00 01 00 00 length 131072 SMID 759 terminated ioc 804b loginfo 31120303 scsi 0 state c xfer 0

Is this just a bad drive? Am I missing anything?

I bought over the years 10 brand new drives of the same model 4 are Nas 3.0 and 6 are Nas 2.0

So far out of out of 7 I opened and installed in the system, one was "dead" (assumed since the system just doesn't see it) and this one is giving this errors at badblocks command.

I am running this on a Dell Poweredge T410 with HBA 200 flashed to it mode. (2 CPUs and 32GB ECC Ram)

Side question, is there any major risk on using the Nas 3.0 and Nas 2.0 together in the same dev pool?

Thank you

 

[demon]

What does:

Code:

smartctl --all /dev/da5

say? It seems to be isolated to that drive. It could be a drive issue or a connection issue, but SMART info from the drive should be able to clarify what sort of problem it is.

 

[Dave Hob]

I ran the smartctl --all /dev/da5 and pasting the result:

smartctl 7.0 2018-12-30 r4883 [FreeBSD 11.3-RELEASE-p6 amd64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD30EFRX-68EUZN0
Serial Number: WD-WMC4N0D4CXUY
LU WWN Device Id: 5 0014ee 65a2001cc
Firmware Version: 82.00A82
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Mar 9 12:07:47 2020 PDT
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: (39360) 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: ( 395) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x703d) 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 100 253 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 200 200 021 Pre-fail Always - 5000
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 6
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 - 27
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 - 6
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 0
194 Temperature_Celsius 0x0022 126 115 000 Old_age Always - 24
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 - 18
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 Extended offline Interrupted (host reset) 30% 23 -
# 2 Extended offline Completed without error 00% 7 -
# 3 Short offline Completed without error 00% 0 -

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.

I am realizing that there is a problem with that drive caddie spot, since that caddie will not recognize any of the Nasware 2.0 drives and it's giving me this issue with this Nasware 3.0 drive.

I am using this 2 cables:
M400M
P215M

from H200 to the backplane that came with the t410

Any suggestions to figure out what is wrong with this? Since it's 6 caddies, 2 cables and only 1 spot that is creating issues.

Thank you

 

[Dave Hob]

also noticed this alert on freenas gui:

Device: /dev/da5 [SAT], not capable of SMART self-check.

and I inserted the drive again in the caddie and ran a smartctl -t long on it and got this error in /var/log/messages:

Mar 9 12:01:31 freenas mps0: SAS Address from SATA device = d2625437ebeadc96
Mar 9 12:01:32 freenas da5 at mps0 bus 0 scbus0 target 5 lun 0
Mar 9 12:01:32 freenas da5: <ATA WDC WD30EFRX-68E 0A82> Fixed Direct Access SPC-4 SCSI device
Mar 9 12:01:32 freenas da5: Serial Number WD-WMC4N0D4CXUY
Mar 9 12:01:32 freenas da5: 600.000MB/s transfers
Mar 9 12:01:32 freenas da5: Command Queueing enabled
Mar 9 12:01:32 freenas da5: 2861588MB (5860533168 512 byte sectors)
Mar 9 12:01:32 freenas da5: quirks=0x8<4K>
Mar 9 13:02:32 freenas collectd[37033]: Traceback (most recent call last):
File "/usr/local/lib/collectd_pyplugins/disktemp.py", line 66, in read
temperatures = c.call('disk.temperatures', self.disks, self.powermode, self.smartctl_args)
File "/usr/local/lib/collectd_pyplugins/disktemp.py", line 66, in read
temperatures = c.call('disk.temperatures', self.disks, self.powermode, self.smartctl_args)
File "/usr/local/lib/python3.7/site-packages/middlewared/client/client.py", line 500, in call
raise CallTimeout("Call timeout")
middlewared.client.client.CallTimeout: Call timeout
Mar 9 13:02:33 freenas (pass5:mps0:0:5:0): ATA COMMAND PASS THROUGH(16). CDB: 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 length 512 SMID 501 Aborting command 0xfffffe000137e190
Mar 9 13:02:33 freenas mps0: Sending reset from mpssas_send_abort for target ID 5
Mar 9 13:02:33 freenas (pass5:mps0:0:5:0): ATA COMMAND PASS THROUGH(16). CDB: 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 length 0 SMID 706 terminated ioc 804b loginfo 31130000 scsi 0 state c xfer 0
Mar 9 13:02:33 freenas mps0: Unfreezing devq for target ID 5

Thank you

 

[demon]

The drive seems to think it's seeing CRC errors. I'd suspect a cabling issue. I don't see any other error indications, so I'd see if you can replace the affected cable. I had a similar issue while building my own NAS, and had to replace the SAS cables as well.

 

[Dave Hob]

The drive seems to think it's seeing CRC errors. I'd suspect a cabling issue. I don't see any other error indications, so I'd see if you can replace the affected cable. I had a similar issue while building my own NAS, and had to replace the SAS cables as well.

Thank you for your feedback. As soon as the the badblock finishes on the other 5 drives will check on the cables and see if I can figure out something

Will follow up

 

[Dave Hob]

Looks like the connector to the backplane was damaged on that caddie, so that was causing the drive to error

Thank you for your help!

 

[demon]

Ah, yeah, that sounds like it might explain it.