I bought one of the 200GB Samsung SAS2 SSD drives as part of the BitDeals 4TB group buy several months back. It was installed as a cache drive in my Unraid server since ~mid-August and it failed over the past couple of days. Any ideas on next steps? I believe BitDeals only covers the first 30 days.
Here is the SMART report from the drive and a screen capture from my Unraid server.
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.19.107-Unraid] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: MZ6ER200HAGM/003
Revision: DM0L
Compliance: SPC-4
User Capacity: 200,049,647,616 bytes [200 GB]
Logical block size: 512 bytes
Physical block size: 8192 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5002538475b00c60
Serial number: S18NNWAGB00198
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Mon Oct 12 14:45:02 2020 MDT
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: FAILURE PREDICTION THRESHOLD EXCEEDED: ascq=0x73 [asc=5d, ascq=73]
Percentage used endurance indicator: 0%
Current Drive Temperature: 35 C
Drive Trip Temperature: 58 C
Manufactured in week 28 of year 2015
Accumulated start-stop cycles: 35
Specified load-unload count over device lifetime: 0
Accumulated load-unload cycles: 0
Elements in grown defect list: 0
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 0 0 0 0 2206.843 0
write: 0 0 0 0 0 2645.851 0
Non-medium error count: 0
No Self-tests have been logged
Background scan results log
Status: scan is active
Accumulated power on time, hours:minutes 1610:11 [96611 minutes]
Number of background scans performed: 2, scan progress: 64.11%
Number of background medium scans performed: 2
Protocol Specific port log page for SAS SSP
relative target port id = 1
generation code = 7
number of phys = 2
phy identifier = 0
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 = 0x5002538475b00c62
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:
Received ERROR count: 0
Received address frame error count: 0
Received abandon-class OPEN_REJECT count: 0
Received retry-class OPEN_REJECT count: 0
Received SSP frame error count: 0
relative target port id = 2
generation code = 7
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 = 0x5002538475b00c63
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:
Received ERROR count: 0
Received address frame error count: 0
Received abandon-class OPEN_REJECT count: 0
Received retry-class OPEN_REJECT count: 0
Received SSP frame error count: 0