Please, let us know how the seller answer to these tests (should you guys ask him) !
If he is willing to switch the bad ones i might grab some.
If he is willing to switch the bad ones i might grab some.
2TB HGST s840 enterprise SAS SED SSD
- Thread starter Silvas
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I'm in communication with the seller. He offered me full return and moneyback (as promised). He told me, that there are a lot drives sold and maybe others are happy with current state of the drives.. I asked, if there is maybe a possibility to exchange bad drives for good ones (if he has - and i think he should have some good in his 80 pieces in stock), but still unanswered..
In the meantime i opened a support case by hgst / wdc and i'm communicating with them, we will see what happens. At least i got a utility (sdmcmd64) special for STEC drives (the drives are sTec and only HGST rebranded, because Hitachi acquired sTec company), which can get more info from the drive. I extracted a support file from one drive and sent it to ghst/wdc suppoort - we will see, what happens. Maybe there is only needed to clear smart error, because the info from this utility gived me good values:
Code:
./sdmcmd64 GetInfo target=gen4sas:Drive7
Results for GetInfo
operationResult = Success
target = gen4sas:Drive7
vendorId = 'STEC'
productId = 'Z16IZF2E-2TBUCZ '
firmwareVersion = 'C23F'
bootLoaderVersion = '2.8.15'
hardwareConfigVersion = '2.8.16'
xRomVersion = ''
usableCapacityInSectors = 3907029168
capacityInGB = 2000 0x7d0
sectorSize = 512 0x200
devicePath = '/dev/sg7'
logicalPath = 'Drive7'
driveType = Gen4Sas
connectType = Lun
serialNumber = 'STM000191BC8 '
wwnn = '5000A72030097D2E'
difLevel = None
supportedSectorSizes = 512,520,524,528
supportedDifLevels = None
supportedDiagnostics = Type1
supportedSanitizeTypes = Erase,Dod,Afssi,Nsa
./sdmcmd64 GetState target=gen4sas:Drive7
Results for GetState
operationResult = Success
target = gen4sas:Drive7
deviceState = Ready
percentDone = 100 0x64
smartReadErrorsRate = 0 0x0
smartReadErrorsExceeded = false
smartWriteErrorsRate = 0 0x0
smartWriteErrorsExceeded = false
smartEccCorrectionRate = 0 0x0
smartEccCorrectionExceeded = false
smartEraseErrorRate = 0 0x0
smartEraseErrorExceeded = false
smartTemperature = 34 0x22
smartTemperatureExceeded = true
smartFreeBlocksPercentage = 100 0x64
smartFreeBlocksPercentageExceeded = false
smartPowerOnHours = 23992 0x5db8
smartPowerCycleCount = 67 0x43
smartPowerBackupConditionFault = false
smartRomCheckFault = false
smartWrongFirmwareFault = false
smartFlashDieMoreThanHalfBadFault = false
smartReadErrorRateThreshold = 10 0xa
smartWriteErrorRateThreshold = 10 0xa
smartEccCorrectionThreshold = 80 0x50
smartEraseErrorRateThreshold = 10 0xa
smartTemperatureThreshold = 65 0x41
smartLowFreepagesThreshold = 10 0xa
estimatedRemainingLifePercentage = 100 0x64
estimatedRemainingLifeThreshold = 5 0x5
estimatedRemainingLifeExceeded = false
highestEraseCount = 13
./sdmcmd64 GetStatistics target=gen4sas:Drive7 level=SinceMade
Results for GetStatistics
operationResult = Success
target = gen4sas:Drive7
level = SinceMade
readCommands = 264937404
readBlocks = 6050839614
writeCommands = 723435938
writeBlocks = 21296922337
eraseCommands = 18446744073709551615
./sdmcmd64 RunDiagnostic target=gen4sas:Drive7 diagnosticType=Type1
Results for RunDiagnostic
operationResult = Success
target = gen4sas:Drive7
root@prox5-1:~/hgst# ./sdmcmd64 RunDiagnostic target=gen4sas:Drive7
diagnosticType=Type2
Results for RunDiagnostic
operationResult = Success
target = gen4sas:Drive7
root@prox5-1:~/hgst# ./sdmcmd64 RunDiagnostic target=gen4sas:Drive7
diagnosticType=Type3
Results for RunDiagnostic
operationResult = Success
target = gen4sas:Drive7
root@prox5-1:~/hgst# ./sdmcmd64 RunDiagnostic target=gen4sas:Drive7
diagnosticType=Type4
Results for RunDiagnostic
operationResult = Success
target = gen4sas:Drive7
root@prox5-1:~/hgst# ./sdmcmd64 RunDiagnostic target=gen4sas:Drive7
diagnosticType=Type5
Results for RunDiagnostic
operationResult = Success
target = gen4sas:Drive7
./sdmcmd64 TestUnit target=gen4sas:Drive7
Results for TestUnit
operationResult = Success
target = gen4sas:Drive7
deviceState = Ready
hasAlert = true
./sdmcmd64 CaptureFieldData target=gen4sas:Drive7 filename=STM000191BC8.bin
Created Capture Field Data file 'STM000191BC8.txt'
CaptureFieldData = Success
target = gen4sas:Drive7
ls -lh STM000191BC8.bin
-rw-r--r-- 1 root root 1.1M Feb 22 17:43 STM000191BC8.bin
Last edited:
allready answered in previous reply - seller offered me full return and moneyback as promised. i didn't still decided..
Code:
hdm manage-firmware --load --activate --file E4Z1.G4-SK04-72R35-YN-v4.0.4.RC11-b1975 --path /dev/sdhHGST/STEC S846 2TB SAS Z16IZF2E-2TBUCZ disks from Ebay
but i'm not sure, that there is not newer firmware, which can be updated by sTec utility sdmcmd.
if i get some info from hgst support, i let you know.
Last edited:
Code:
=== START OF INFORMATION SECTION ===
Vendor: STEC
Product: Z16IZF2E-2TBUCZ
Revision: C23F
Compliance: SPC-4
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Logical block size: 512 bytes
LU is resource provisioned, LBPRZ=0
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5000a72030097d2e
Serial number: STM000191BC8
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Sat Feb 17 16:03:14 2018 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Health Status: FAILURE PREDICTION THRESHOLD EXCEEDED: ascq=0xb [asc=5d, ascq=b]
Percentage used endurance indicator: 0%
Current Drive Temperature: 37 C
Drive Trip Temperature: 65 C
Elements in grown defect list: 0
Code:
=== START OF INFORMATION SECTION ===
Vendor: STEC
Product: Z16IZF2E-2TBUCZ
Revision: C23F
Compliance: SPC-4
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Logical block size: 512 bytes
LU is resource provisioned, LBPRZ=0
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5000a72030097d2e
Serial number: STM000191BC8
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Thu Feb 22 20:27:32 2018 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Percentage used endurance indicator: 0%
Current Drive Temperature: 34 C
Drive Trip Temperature: 65 CSo, theres a chance that the seller is altering the smart values ?
Because althought some of the smart reports are ok, the benchmarks don´t lie that there´s something afoot.
Because althought some of the smart reports are ok, the benchmarks don´t lie that there´s something afoot.
not the seller, i maybe found a magic spell, how to clear the smart error.
i will know more after some benchmarks, which will probably not lie..
some more hardware info:
1) flash memories are TH58TEG9E2HBA89 - Toshiba eMLC 64GB chips
2) there are 36 of the flash chips - 15% overprovisioning?
3) there are 4 supercapacitors type ESHSR-0006C0-002R7 (6 Farrad, 2.7 Volt, price 0.93235euro on 500 pieces)
http://www.nesscap.com/common/downl...=NCE_2017_Datasheet_2.7V6F_REV18_20170613.pdf
ESHSR-0006C0-002R7 Nesscap | Rutronik24 Distributor
1) flash memories are TH58TEG9E2HBA89 - Toshiba eMLC 64GB chips
2) there are 36 of the flash chips - 15% overprovisioning?
3) there are 4 supercapacitors type ESHSR-0006C0-002R7 (6 Farrad, 2.7 Volt, price 0.93235euro on 500 pieces)
http://www.nesscap.com/common/downl...=NCE_2017_Datasheet_2.7V6F_REV18_20170613.pdf
ESHSR-0006C0-002R7 Nesscap | Rutronik24 Distributor
Last edited:
hello,
as i allready mentioned i was in communication with hgst / wdc / sandisk support (thank specially Robert Clarke from Sandisk) and i got following infos:
1)
Bye
Jan
as i allready mentioned i was in communication with hgst / wdc / sandisk support (thank specially Robert Clarke from Sandisk) and i got following infos:
1)
2)
- i got the modified smart utility and it works
- i tested till now first 2 drives and it looks like the max temperature was 82 and 84 grad celsius
- the temperature occured at 23820 to 23822 hour of disk life
I actually plan to replace all supercapacitors with new ones - just for preventing failure (capacitors can be dammaged by the high temperature - accroding to datasheet the max. temperature for them is really 65 grad celsius). if the price of one supercapacitor is only about 1 euro, it will cost not so much and i assume, that the drive durability should be nearly back to the situation before overheating..
Bye
Jan
There are some good news and some bad news:
- good - smart can be cleared by smdcmd utility
- bad - the performance after smart clearing stay bad (nothing changed)
no, changing capacitors can only give the drive more reliabity, but not fix the speed issue.I guessed as much
Perhaps its the capacitors ?
i'm testing something, which can maybe fix the speed issue - stay tuned, i give you more info tomorrow morning..
Jan
not very good :-(
drive was part of PROXMOX/CEPH test cluster and failed today morning without reason.
i removed it, put in another server and scan smart values - i didn't see nothing exceptional.
when failed - there is a LED in drive, which is normally flashing green during normal operation - during fail it was lighting continuously and not flashing - juast as remark, maybe there can be found sme info about led states..
here are smart values from failed drive (read after failure):
and from smartctl
Code:
Mar 2 06:47:27 prox5-2 kernel: [724839.109034] mptscsih: ioc1: attempting task abort! (sc=ffff9fe85c4d0148)
Mar 2 06:47:27 prox5-2 kernel: [724839.109043] sd 7:0:3:0: [sdh] tag#34 CDB: Read(10) 28 00 65 31 b8 20 00 00 80 00
Mar 2 06:47:32 prox5-2 kernel: [724843.580557] mptbase: ioc1: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) cb_idx mptscsih_io_done
Mar 2 06:47:32 prox5-2 kernel: [724843.580720] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff9fe85c4d0148)
Mar 2 06:47:32 prox5-2 kernel: [724843.580730] mptscsih: ioc1: attempting task abort! (sc=ffff9fe85c4d1148)
Mar 2 06:47:32 prox5-2 kernel: [724843.580737] sd 7:0:3:0: [sdh] tag#33 CDB: Read(10) 28 00 65 31 ae a0 00 01 80 00
Mar 2 06:47:36 prox5-2 kernel: [724848.080695] mptbase: ioc1: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) cb_idx mptscsih_io_done
Mar 2 06:47:36 prox5-2 kernel: [724848.080866] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff9fe85c4d1148)
Mar 2 06:47:36 prox5-2 kernel: [724848.080873] mptscsih: ioc1: attempting task abort! (sc=ffff9fe85c4d1d48)
Mar 2 06:47:36 prox5-2 kernel: [724848.080877] sd 7:0:3:0: [sdh] tag#32 CDB: Read(10) 28 00 65 31 ad 20 00 01 00 00
Mar 2 06:47:41 prox5-2 kernel: [724852.580756] mptbase: ioc1: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) cb_idx mptscsih_io_done
Mar 2 06:47:41 prox5-2 kernel: [724852.580883] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff9fe85c4d1d48)
Mar 2 06:47:41 prox5-2 kernel: [724852.580889] mptscsih: ioc1: attempting task abort! (sc=ffff9fe85c4d1548)
Mar 2 06:47:41 prox5-2 kernel: [724852.580895] sd 7:0:3:0: [sdh] tag#31 CDB: Read(10) 28 00 65 31 ab 20 00 00 80 00
Mar 2 06:47:45 prox5-2 kernel: [724857.080902] mptbase: ioc1: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) cb_idx mptscsih_io_done
Mar 2 06:47:45 prox5-2 kernel: [724857.081098] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff9fe85c4d1548)
Mar 2 06:47:45 prox5-2 kernel: [724857.081110] mptscsih: ioc1: attempting task abort! (sc=ffff9fe85c4d0d48)
Mar 2 06:47:45 prox5-2 kernel: [724857.081118] sd 7:0:3:0: [sdh] tag#30 CDB: Read(10) 28 00 65 31 a6 a0 00 01 00 00
Mar 2 06:47:50 prox5-2 kernel: [724861.580933] mptbase: ioc1: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) cb_idx mptscsih_io_done
Mar 2 06:47:50 prox5-2 kernel: [724861.581111] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff9fe85c4d0d48)
Mar 2 06:47:50 prox5-2 kernel: [724861.581121] mptscsih: ioc1: attempting task abort! (sc=ffff9fe85c4d2d48)
Mar 2 06:47:50 prox5-2 kernel: [724861.581129] sd 7:0:3:0: [sdh] tag#29 CDB: Read(10) 28 00 65 31 bb a0 00 00 80 00
Mar 2 06:47:54 prox5-2 kernel: [724866.081117] mptbase: ioc1: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) cb_idx mptscsih_io_donei removed it, put in another server and scan smart values - i didn't see nothing exceptional.
when failed - there is a LED in drive, which is normally flashing green during normal operation - during fail it was lighting continuously and not flashing - juast as remark, maybe there can be found sme info about led states..
here are smart values from failed drive (read after failure):
Code:
Results for GetInfo
operationResult = Success
target = gen4sas:Drive20
vendorId = 'STEC'
productId = 'Z16IZF2E-2TBUCZ '
firmwareVersion = 'C23F'
bootLoaderVersion = '2.8.15'
hardwareConfigVersion = '2.8.16'
xRomVersion = ''
usableCapacityInSectors = 3907029168
capacityInGB = 2000 0x7d0
sectorSize = 512 0x200
devicePath = '/dev/sg20'
logicalPath = 'Drive20'
driveType = Gen4Sas
connectType = Lun
serialNumber = 'STM000190F8F '
wwnn = '5000A7203009711E'
difLevel = None
supportedSectorSizes = 512,520,524,528
supportedDifLevels = None
supportedDiagnostics = Type1
supportedSanitizeTypes = Erase,Dod,Afssi,Nsa
Results for GetState
operationResult = Success
target = gen4sas:Drive20
deviceState = Ready
percentDone = 100 0x64
smartReadErrorsRate = 0 0x0
smartReadErrorsExceeded = false
smartWriteErrorsRate = 0 0x0
smartWriteErrorsExceeded = false
smartEccCorrectionRate = 0 0x0
smartEccCorrectionExceeded = false
smartEraseErrorRate = 0 0x0
smartEraseErrorExceeded = false
smartTemperature = 42 0x2a
smartTemperatureExceeded = false
smartFreeBlocksPercentage = 100 0x64
smartFreeBlocksPercentageExceeded = false
smartPowerOnHours = 24019 0x5dd3
smartPowerCycleCount = 62 0x3e
smartPowerBackupConditionFault = false
smartRomCheckFault = false
smartWrongFirmwareFault = false
smartFlashDieMoreThanHalfBadFault = false
smartReadErrorRateThreshold = 10 0xa
smartWriteErrorRateThreshold = 10 0xa
smartEccCorrectionThreshold = 80 0x50
smartEraseErrorRateThreshold = 10 0xa
smartTemperatureThreshold = 65 0x41
smartLowFreepagesThreshold = 10 0xa
estimatedRemainingLifePercentage = 100 0x64
estimatedRemainingLifeThreshold = 5 0x5
estimatedRemainingLifeExceeded = false
highestEraseCount = 12
Results for GetStatistics
operationResult = Success
target = gen4sas:Drive20
level = SinceMade
readCommands = 31352571
readBlocks = 4138308895
writeCommands = 587547379
writeBlocks = 18776079792
eraseCommands = 18446744073709551615
diagnosticType=Type1
Results for RunDiagnostic
operationResult = Success
target = gen4sas:Drive20
diagnosticType=Type2
Results for RunDiagnostic
operationResult = Success
target = gen4sas:Drive20
diagnosticType=Type3
Results for RunDiagnostic
operationResult = Success
target = gen4sas:Drive20
diagnosticType=Type4
Results for RunDiagnostic
operationResult = Success
target = gen4sas:Drive20
diagnosticType=Type5
Results for RunDiagnostic
operationResult = Success
target = gen4sas:Drive20
Results for TestUnit
operationResult = Success
target = gen4sas:Drive20
deviceState = Ready
hasAlert = false
Created Capture Field Data file 'STM000190F8F.bin'
CaptureFieldData = Success
target = gen4sas:Drive20
Code:
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.16.0-5-amd64] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org
Vendor: STEC
Product: Z16IZF2E-2TBUCZ
Revision: C23F
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Logical block size: 512 bytes
Logical Unit id: 0x5000a7203009711e
Serial number: STM000190F8F
Device type: disk
Transport protocol: SAS
Local Time is: Fri Mar 2 18:19:49 2018 CET
Device supports SMART and is Enabled
Temperature Warning Enabled
SMART Health Status: OK
SS Media used endurance indicator: 0%
Current Drive Temperature: 42 C
Drive Trip Temperature: 65 C
STEC SCSI Smart Data
ID ATTB STATUS CURRENT MAX MIN THRESHOLD
001 READ ERROR RATE OK 000 100 000 010
002 WRITE ERROR RATE OK 000 100 000 010
003 ECC CORRECTION RATE OK 000 100 000 080
004 ERASE ERROR RATE OK 000 100 000 010
009 POWER ON HOURS N/A 24019 65535 000 none
018 POWER CYCLE COUNT N/A 062 255 000 none
194 TEMPERATURE OK 042 127 000 065
196 FREE BLOCKS PERCENTAGE OK 100 100 000 010
224 POWER BACKUP CONDITION OK 000 001 000 001
225 TRANSLATION TABLE REBUILD OK 000 001 000 001
226 ROM CHECK OK 000 001 000 001
227 WRONG FW LOADED OK 000 001 000 001
228 Translation_Table_Rebuild_Cnt N/A 000 255 000 none
229 SEU_Count OK 000 002 000 002
230 Flash_Die_Failure OK 000 001 000 001
233 Pct_Lifetime_Remaining OK 100 100 000 005
STEC SCSI Temperature History Log Page
Current 42 C
Reference 65 C
Max Temp 82 C
Min Temp 26 C
Power-On Hour when Maximum Temperature Occurred 1429341 (minutes)
Total spent Time Over Ref 370 (minutes)
Power-On Hour when Minimum Temperature Occurred 489288 (minutes)
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: 52158077042 0 52158077042 52158077042 52158077042 246295.825 0
write: 0 0 0 0 0 8771.276 0
Non-medium error count: 0
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Foreground long Completed - 24019 - [- - -]
# 2 Foreground long Completed - 24019 - [- - -]
# 3 Foreground long Completed - 24019 - [- - -]
# 4 Foreground long Completed - 24019 - [- - -]
# 5 Foreground long Completed - 24019 - [- - -]
# 6 Foreground long Completed - 24003 - [- - -]
# 7 Foreground long Completed - 24003 - [- - -]
# 8 Foreground long Completed - 24003 - [- - -]
# 9 Foreground long Completed - 24003 - [- - -]
#10 Foreground long Completed - 24003 - [- - -]
Long (extended) Self Test duration: 600 seconds [10.0 minutes]