O, darn... Any idea why?also they don't work with HBA LSI 2008/2308
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
O, darn... Any idea why?also they don't work with HBA LSI 2008/2308
Sorry if it wasn't clear from the post, I intend to keep the disks and update the firmware on all of them, I only have 5 though, so i don't know if it is really a trustworthy sample size for results.@RTM -- You plan to update and test and roll out or r eturn?
Thank you for your diagnostics and I'm VERY glad I didn't get these drives.
root@ubuntu:/home/wazzy# hdm scan
[0000000000000000]
Device Type = ATA Device
Device Path = /dev/sda
UID = 0000000000000000
Alias = @ata0
Model Name = NETLIST SSD128GB-002
[5000A72030098033]
Device Type = SCSI Device
UID = 5000A72030098033
Alias = @scsi0
Vendor Name = STEC
Model Name = Z16IZF2E-2TBUCZ
Parent Device Type = MegaRAID Controller
RAID Controller ID = 0
RAID Device ID = 12
Results for scan: Operation succeeded on 2 of 2 devices.
root@ubuntu:/home/wazzy# hdm generate-report --uid 5000A72030098033
[5000A72030098033]
Device Type = SCSI Device
UID = 5000A72030098033
Alias = @scsi0
Vendor Name = STEC
Model Name = Z16IZF2E-2TBUCZ
Serial Number = STM000191EC9
Firmware Version = C22F
Capacity = 2000398934016
Parent Device Type = MegaRAID Controller
RAID Controller ID = 0
RAID Device ID = 12
Sector Count = 3907029168
Sector Size = 512
Metadata Size = 0
DIF Level = None
Protection Interval = 1
Multipath Support = true
SAS Port 1 Width = Narrow (1x)
SAS Port 1 Physical Link Rate = 6 Gb/s
Device Status = Device Status Unknown
Life Gauge = 100
Data Units Read = 21138439280
Data Units Written = 5089297789
Host Read Commands = 148678244
Host Write Commands = 720755257
Percentage Used = 0
Temperature = 59
Temperature Threshold = 65
Results for generate-report: Operation succeeded.
root@ubuntu:/home/wazzy# hdparm -tT /dev/sdb
/dev/sdb:
Timing cached reads: 17860 MB in 2.00 seconds = 8938.07 MB/sec
Timing buffered disk reads: 1454 MB in 3.00 seconds = 484.21 MB/sec
root@ubuntu:/home/wazzy# dd if=/dev/zero of=/dev/sdb bs=8k count=100k;
102400+0 records in
102400+0 records out
838860800 bytes (839 MB, 800 MiB) copied, 1.92176 s, 437 MB/s
I got a lot of 6 drives:
=== 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: 42 C
Drive Trip Temperature: 65 C
Elements in grown defect list: 0
I think - according to hddtune tests (see my posts) - the reported SMART error is a real error with big impact to drive random access performance. I got one drive in my batch which has no SMART issues and i have done some comparison between "good" and "bad" drive results..Fifth, I updated the firmware on one of the disks in the hope that it might clear the SMART issue that @Toddh has seen with smartctl, that I am also seeing. It did not make any difference, however my belief is that the error is not correct. From HGST's support site you can download the HGST Device Manager tool (you need it to update firmware anyway), it can also show some SMART data including a wear level indicator, which shows very little use (0% used or 100% remaining - forgot the actual term they used). I realize that this does not guarantee that there is not some issue with the disks, but again it is my personal belief that it is most likely just an issue with smartctl/smartmontools.
Sixth, I get a lot of weird SMART related logs again indicating "predictive failure" (or something like this), again I am not sure if this is just bad SMART parsing or an actual error. In the coming time I will put some data on the system, hopefully that will be a good way to determine whether it is a real issue or not.
i did - see my posts. even i have one good drive and results from both - good and bad ones..Could you please share some CDI or Hard Disk Sentinel screens with us RTM ?
Thanks.
okay, some more tests and infos:
"Good" drive:
- a difference in random access can be found between "good" and "bad" drive
- the above info tell us, i think, that the SMART status isn't only some missinterretation of readed values, but the drive is at least slowed down in random access
- slowed down random access can be the ground for long time, that takes a drive formatting
"Bad" drive:
All tests and reports are available here: HGST/STEC S846 2TB SAS Z16IZF2E-2TBUCZ disks from Ebay
Bye
Jan