New unraid server, drive errors on refurbished drive

Hi all,

I just set up my first unraid server last weekend, supplemented with 3 refurbished 6TB drives from Bitdeals. One of the drives has uncorrectable errors which I have never experienced before, is this drive toast? I am past the 30 day warranty provided by bitdeals as it took me a while from when I purchased the drives to when I was able to actually build the server and get everything up and running. Shame as I’m sure I would have been able to return the drive if I set up my server faster. Below is the SMART report for the drive, how urgent is it that I replace it?

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: HGST
Product: HUS726060AL5210
Revision: A907
Compliance: SPC-4
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is fully provisioned
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000cca255241e10
Serial number: K1GMVSND
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Sat May 8 23:52:14 2021 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
Read Cache is: Enabled
Writeback Cache is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature: 42 C
Drive Trip Temperature: 85 C

Manufactured in week 34 of year 2016
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 21
Specified load-unload count over device lifetime: 600000
Accumulated load-unload cycles: 1242
Elements in grown defect list: 295

Vendor (Seagate Cache) information
Blocks sent to initiator = 6815695278964736

Error counter log:
Errors Corrected by Total Correction Gigabytes Total
ECC rereads/ errors algorithm processed uncorrected
fast | delayed rewrites corrected invocations [10^9 bytes] errors
read: 0 35 0 35 14277417 90717.953 69
write: 0 24986 0 24986 1505197 104462.134 163
verify: 0 0 0 0 1387747 0.000 0

Non-medium error count: 0

Self-test execution status: 100% of test remaining
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)

1 Background long Self test in progress … - NOW - [- - -]

Long (extended) Self-test duration: 47432 seconds [790.5 minutes]

Background scan results log
Status: scan is active
Accumulated power on time, hours:minutes 12063:53 [723833 minutes]
Number of background scans performed: 60, scan progress: 27.35%
Number of background medium scans performed: 60

when lba(hex) [sk,asc,ascq] reassign_status

1 11908:39 00000000029f3c28 [3,11,0] Require Write or Reassign Blocks command
2 11908:39 00000000029e1db8 [3,11,0] Require Write or Reassign Blocks command
3 11908:39 000000000298d0b0 [3,11,0] Require Write or Reassign Blocks command
4 11908:38 0000000001a9fff8 [3,11,0] Require Write or Reassign Blocks command
5 11908:38 00000000019fbe38 [3,11,0] Require Write or Reassign Blocks command
6 11908:38 00000000019eca40 [3,11,0] Require Write or Reassign Blocks command
7 11908:37 0000000000bc9eb8 [3,11,0] Require Write or Reassign Blocks command
8 11908:37 0000000000bc9eb0 [3,11,0] Require Write or Reassign Blocks command
9 11908:37 0000000000afbf60 [3,11,0] Require Write or Reassign Blocks command
10 11908:37 0000000000a993e0 [3,11,0] Require Write or Reassign Blocks command
11 11469:08 00000000058db0e8 [3,11,0] Recovered via rewrite in-place
12 11469:08 00000000058db0e0 [3,11,0] Recovered via rewrite in-place
13 11469:05 0000000001aeadb8 [3,11,0] Recovered via rewrite in-place
14 11469:04 0000000000bcac48 [3,11,0] Recovered via rewrite in-place
15 11469:04 0000000000b35cf0 [3,11,0] Recovered via rewrite in-place
16 11469:04 0000000000ae0c40 [3,11,0] Recovered via rewrite in-place
17 11469:04 0000000000ae0c38 [3,11,0] Recovered via rewrite in-place
18 11469:04 0000000000a9e648 [3,11,0] Recovered via rewrite in-place
19 11469:04 0000000000a918f0 [3,11,0] Recovered via rewrite in-place

Protocol Specific port log page for SAS SSP
relative target port id = 1
generation code = 1
number of phys = 1
phy identifier = 0
attached device type: SAS or SATA device
attached reason: power on
reason: unknown
negotiated logical link rate: phy enabled; 6 Gbps
attached initiator port: ssp=1 stp=1 smp=1
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000cca255241e11
attached SAS address = 0x500605b005f80e60
attached phy identifier = 1
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0
relative target port id = 2
generation code = 1
number of phys = 1
phy identifier = 1
attached device type: no device attached
attached reason: unknown
reason: power on
negotiated logical link rate: phy enabled; unknown
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000cca255241e12
attached SAS address = 0x0
attached phy identifier = 0
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0

How far past? Have contacted them to ask?

Original order date was March 17th. The order shipped March 29th. Is it worth contacting Bitdeals?

They’re not a vendor like a Newegg. It’s always worth it to ask.

I’ll give it a shot then. Will post back here when I hear back!

I sent an email to Bitdeals on 5/9 but have not heard back yet:

“A few months ago I ordered (3) 6TB SAS HDDs (order #MBP2418) which were delivered on April 5th 2021. I finally had the time to set up my server and test the drives last week and discovered that one of the drives has uncorrectable errors. I’ve attached the SMART report from unraid. I have missed the 30 day warranty on my order by a few days, however I was wondering if Bitdeals may consider replacing the drive or providing me a refund for just that drive. If so please let me know, I would greatly appreciate it.”

@BitDeals would you be able to check and see if anyone can respond to my email? Thank you.

I will forward your request to them and make sure that you get an RMA. Don’t worry too much about the time frame.

1 Like

Thank you, appreciate it!!