![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
-
Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
How to test a new HDD/SSD
- Thread starter llmercll
- Start date
Good place to start is to download the software from the manufacturer, like WD or Seagate. Normally they offer some kind of diagnostics test you can run to verify all sectors are good. There some programs like HD Tune that will do a quick or slow level scan and check for bad sectors. The slow scans will take 1-4 hrs depending on size of drive. I'd start with that. Run that test couple of times and see what you get.
When you get a new drive always check and save the SMART values so you can compare later on. In windows crystaldiskinfo is a good choice. In Linux there is smartctl.
First thing to check is power on hours value to see if drive is new or used or if refurbished how much use will give you an idea of what to expect failure wise.
After recording initial values, you should stresstest. In Linux use badblocks or a badblocks based script like:
http://lime-technology.com/forum/index.php?topic=2817.0
In WIndows you could do a full format or "zero" using various tools. But do this a few times, one pass is not enough.
There is a dos based tool called hdat2 that has more advanced options.
After stess testing recheck SMART values and compare to initial records.
I personally think manufacturer's tools are crap and only show the basic or obvious errors.
First thing to check is power on hours value to see if drive is new or used or if refurbished how much use will give you an idea of what to expect failure wise.
After recording initial values, you should stresstest. In Linux use badblocks or a badblocks based script like:
http://lime-technology.com/forum/index.php?topic=2817.0
In WIndows you could do a full format or "zero" using various tools. But do this a few times, one pass is not enough.
There is a dos based tool called hdat2 that has more advanced options.
After stess testing recheck SMART values and compare to initial records.
I personally think manufacturer's tools are crap and only show the basic or obvious errors.
I have lost more data due to my stupidity than to HDD/SSD defects.
I no longer test my drives. A quick format and I am good to go.
The Linux & badblocks has worked great for me.
I usually do 4 full pass in write mode on every new HDD to burn-in. (multiple days on big TBs HDD btw)
The HDD that pass it have performed greats fro me. Otherwise I ship it back/exchange.
It's a life saver for your data, at this time the quality of HDD is atrocious, you'll be a fool or simply don't care about your data if you simply install, quick format it and move your data over
I usually do 4 full pass in write mode on every new HDD to burn-in. (multiple days on big TBs HDD btw)
The HDD that pass it have performed greats fro me. Otherwise I ship it back/exchange.
It's a life saver for your data, at this time the quality of HDD is atrocious, you'll be a fool or simply don't care about your data if you simply install, quick format it and move your data over
D4rkn3ss
2[H]4U
- Joined
- Jun 30, 2010
- Messages
- 2,618
wd dlgdiag for win. it says its for wd drives but it works flawlessly for everything else too.
You'll note that everyone here is talking about how to test HDDs. SSDs are a whole different sport and I don't think you would test them the way you do HDDs at all, but I'd like to hear comments from the guys who set them up for enterprise use about how they test them, if at all.
Thanks a lot for the continued replies everyone, I really appreciate it =)
Badblocks on linux seems to be the most recommended way to stress test an HDD. I don't have linux installed, however, so I think I will make an umbutu bootable CD and do it through that.
As for checking smart and running smart tests and surface tests, I've found HDtune and Gsmartcontrol to be my favorite programs. I believe Gsmartcontrol uses smartctl, which is a highly recommended linux program, so that is always nice. I figure between running a surface test on hdtune, smart tests on gsmartcontrol, and the windows chkdsk /r, I can have all my bases covered if I ever need to check the health of a drive once it's populated with data.
The advice to take a screenshot of my smart data when the drive is new was very helpful as well.
Badblocks on linux seems to be the most recommended way to stress test an HDD. I don't have linux installed, however, so I think I will make an umbutu bootable CD and do it through that.
As for checking smart and running smart tests and surface tests, I've found HDtune and Gsmartcontrol to be my favorite programs. I believe Gsmartcontrol uses smartctl, which is a highly recommended linux program, so that is always nice. I figure between running a surface test on hdtune, smart tests on gsmartcontrol, and the windows chkdsk /r, I can have all my bases covered if I ever need to check the health of a drive once it's populated with data.
The advice to take a screenshot of my smart data when the drive is new was very helpful as well.
D4rkn3ss
2[H]4U
- Joined
- Jun 30, 2010
- Messages
- 2,618
so you decided to ignore my tip and go with all this crap instead huh, well, be happy then.
you can install smartmontools for windows
http://sourceforge.net/projects/smartmontools/files/
install it and it installs a shortcut in windows menu that goes right to the command line
This particular drive has 3.7 yrs of uptime and is failing.
http://sourceforge.net/projects/smartmontools/files/
install it and it installs a shortcut in windows menu that goes right to the command line
Code:
smartctl 6.3 2014-07-26 r3976 [x86_64-w64-mingw32-win8] (sf-6.3-1)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green
Device Model: WDC WD20EADS-00R6B0
Serial Number: WD-WCAVY0333985
LU WWN Device Id: 5 0014ee 202d9659a
Firmware Version: 01.00A01
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Mon Oct 26 01:16:33 2015 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Disabled
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
ATA Security is: Disabled, frozen [SEC2]
Wt Cache Reorder: Unknown
=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.
General SMART Values:
Offline data collection status: (0x85) Offline data collection activity
was aborted by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 245) Self-test routine in progress...
50% of test remaining.
Total time to complete Offline
data collection: (42360) 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: ( 482) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303f) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 200 200 051 - 14002
3 Spin_Up_Time POS--K 148 147 021 - 9566
4 Start_Stop_Count -O--CK 098 098 000 - 2547
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 100 253 000 - 0
9 Power_On_Hours -O--CK 056 056 000 - 32673
10 Spin_Retry_Count -O--CK 100 100 000 - 0
11 Calibration_Retry_Count -O--CK 100 100 000 - 0
12 Power_Cycle_Count -O--CK 099 099 000 - 1362
192 Power-Off_Retract_Count -O--CK 200 200 000 - 57
193 Load_Cycle_Count -O--CK 200 200 000 - 2486
194 Temperature_Celsius -O---K 118 111 000 - 34
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 41
198 Offline_Uncorrectable ----CK 200 200 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 1
200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 14
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 6 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa0-0xa7 GPL,SL VS 16 Device vendor specific log
0xa8-0xb7 GPL,SL VS 1 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xc1 GPL VS 24 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 19
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 19 [18] occurred at disk power-on lifetime: 27326 hours (1138 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 62 07 fd 40 00 Error: UNC at LBA = 0x006207fd = 6424573
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:02:01.267 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:02:01.266 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:58.048 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:58.048 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:54.818 READ FPDMA QUEUED
Error 18 [17] occurred at disk power-on lifetime: 27326 hours (1138 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 62 07 fd 40 00 Error: UNC at LBA = 0x006207fd = 6424573
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:58.048 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:58.048 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:54.818 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:54.818 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:51.588 READ FPDMA QUEUED
Error 17 [16] occurred at disk power-on lifetime: 27326 hours (1138 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 62 07 fd 40 00 Error: UNC at LBA = 0x006207fd = 6424573
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:54.818 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:54.818 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:51.588 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:51.588 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:48.358 READ FPDMA QUEUED
Error 16 [15] occurred at disk power-on lifetime: 27326 hours (1138 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 62 07 fd 40 00 Error: UNC at LBA = 0x006207fd = 6424573
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:51.588 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:51.588 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:48.358 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:48.358 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:45.138 READ FPDMA QUEUED
Error 15 [14] occurred at disk power-on lifetime: 27326 hours (1138 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 62 07 fd 40 00 Error: UNC at LBA = 0x006207fd = 6424573
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:48.358 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:48.358 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:45.138 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:45.138 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:41.908 READ FPDMA QUEUED
Error 14 [13] occurred at disk power-on lifetime: 27326 hours (1138 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 62 07 fd 40 00 Error: UNC at LBA = 0x006207fd = 6424573
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:45.138 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:45.138 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:41.908 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:41.908 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:38.679 READ FPDMA QUEUED
Error 13 [12] occurred at disk power-on lifetime: 27326 hours (1138 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 62 07 fd 40 00 Error: UNC at LBA = 0x006207fd = 6424573
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:41.908 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:41.908 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:38.679 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:38.678 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:35.449 READ FPDMA QUEUED
Error 12 [11] occurred at disk power-on lifetime: 27326 hours (1138 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 62 07 fd 40 00 Error: UNC at LBA = 0x006207fd = 6424573
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:38.679 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:38.678 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:35.449 READ FPDMA QUEUED
ef 00 02 00 00 00 00 00 00 00 00 00 00 00:01:35.449 SET FEATURES [Enable write cache]
60 00 08 00 08 00 62 00 07 00 f8 40 00 00:01:32.219 READ FPDMA QUEUED
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 32497 -
# 2 Short offline Completed without error 00% 32219 -
# 3 Short offline Completed without error 00% 32036 -
# 4 Short offline Completed without error 00% 31903 -
# 5 Short offline Completed without error 00% 31806 -
# 6 Short offline Completed without error 00% 31394 -
# 7 Short offline Completed without error 00% 31165 -
# 8 Short offline Completed without error 00% 30781 -
# 9 Short offline Completed without error 00% 30670 -
#10 Short offline Completed without error 00% 30516 -
#11 Short offline Completed without error 00% 30385 -
#12 Short offline Completed without error 00% 29895 -
#13 Short offline Completed without error 00% 29106 -
#14 Extended offline Completed without error 00% 20640 -
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.
SCT Status Version: 2
SCT Version (vendor specific): 258 (0x0102)
SCT Support Level: 1
Device State: DST executing in background (3)
Current Temperature: 34 Celsius
Power Cycle Min/Max Temperature: 23/36 Celsius
Lifetime Min/Max Temperature: 34/41 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: 0/60 Celsius
Min/Max Temperature Limit: -41/85 Celsius
Temperature History Size (Index): 478 (28)
Index Estimated Time Temperature Celsius
29 2015-10-25 17:19 35 ****************
30 2015-10-25 17:20 35 ****************
31 2015-10-25 17:21 35 ****************
32 2015-10-25 17:22 34 ***************
... ..( 22 skipped). .. ***************
55 2015-10-25 17:45 34 ***************
56 2015-10-25 17:46 35 ****************
... ..( 2 skipped). .. ****************
59 2015-10-25 17:49 35 ****************
60 2015-10-25 17:50 34 ***************
... ..( 9 skipped). .. ***************
70 2015-10-25 18:00 34 ***************
71 2015-10-25 18:01 33 **************
... ..( 5 skipped). .. **************
77 2015-10-25 18:07 33 **************
78 2015-10-25 18:08 34 ***************
... ..( 6 skipped). .. ***************
85 2015-10-25 18:15 34 ***************
86 2015-10-25 18:16 35 ****************
87 2015-10-25 18:17 35 ****************
88 2015-10-25 18:18 34 ***************
... ..( 60 skipped). .. ***************
149 2015-10-25 19:19 34 ***************
150 2015-10-25 19:20 35 ****************
... ..( 55 skipped). .. ****************
206 2015-10-25 20:16 35 ****************
207 2015-10-25 20:17 34 ***************
... ..( 36 skipped). .. ***************
244 2015-10-25 20:54 34 ***************
245 2015-10-25 20:55 35 ****************
... ..(151 skipped). .. ****************
397 2015-10-25 23:27 35 ****************
398 2015-10-25 23:28 34 ***************
... ..( 15 skipped). .. ***************
414 2015-10-25 23:44 34 ***************
415 2015-10-25 23:45 35 ****************
416 2015-10-25 23:46 35 ****************
417 2015-10-25 23:47 34 ***************
... ..( 20 skipped). .. ***************
438 2015-10-26 00:08 34 ***************
439 2015-10-26 00:09 35 ****************
... ..( 4 skipped). .. ****************
444 2015-10-26 00:14 35 ****************
445 2015-10-26 00:15 36 *****************
446 2015-10-26 00:16 35 ****************
... ..( 7 skipped). .. ****************
454 2015-10-26 00:24 35 ****************
455 2015-10-26 00:25 34 ***************
... ..( 5 skipped). .. ***************
461 2015-10-26 00:31 34 ***************
462 2015-10-26 00:32 35 ****************
463 2015-10-26 00:33 34 ***************
... ..( 39 skipped). .. ***************
25 2015-10-26 01:13 34 ***************
26 2015-10-26 01:14 35 ****************
27 2015-10-26 01:15 35 ****************
28 2015-10-26 01:16 35 ****************
SMART WRITE LOG does not return COUNT and LBA_LOW register
SCT (Get) Error Recovery Control command failed
Device Statistics (GP Log 0x04) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 0 Command failed due to ICRC error
0x0002 2 0 R_ERR response for data FIS
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0005 2 0 R_ERR response for non-data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
0x000a 2 2 Device-to-host register FISes sent due to a COMRESET
0x8000 4 112081 Vendor specificThis particular drive has 3.7 yrs of uptime and is failing.