I was hoping someone could help me out with the results of this smart test.
This is a brand new drive that I got on Thursday.
Drive passes a single pass destructive badblocks test, but is extremely slow. FreeNAS gui showing around 5MB transfer speeds during the test and it took around 60 hours to do a single pass.
This drive is basically being put in a laptop that I replicate to daily, just so I can grab and go if needed. I also have an off site backup strategy.
Here is the smart test log:
Oddly enough it had nearly 25 power on hours when I received the drive and had a ton of load cycles. the drive was sealed though.
Edit: im going to say this guy is junk. I did a test copy and its writing at 355kbps lol...
This is a brand new drive that I got on Thursday.
Drive passes a single pass destructive badblocks test, but is extremely slow. FreeNAS gui showing around 5MB transfer speeds during the test and it took around 60 hours to do a single pass.
This drive is basically being put in a laptop that I replicate to daily, just so I can grab and go if needed. I also have an off site backup strategy.
Here is the smart test log:
Code:
[root@BackupNAS] ~# smartctl -a /dev/ada0 smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p28 amd64] (local build) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Samsung SpinPoint M9T Device Model: ST1500LM006 HN-M151RAD Serial Number: S326J9CDC21839 LU WWN Device Id: 5 0004cf 20c1b46ff Firmware Version: 2BC10001 User Capacity: 1,500,301,910,016 bytes [1.50 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 2.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Nov 8 16:15:58 2015 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (18120) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 302) minutes. SCT capabilities: (0x003f) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 099 099 051 Pre-fail Always - 1374 2 Throughput_Performance 0x0026 055 055 000 Old_age Always - 16604 3 Spin_Up_Time 0x0023 088 087 025 Pre-fail Always - 3898 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 153 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 106 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 2 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 588 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 062 000 Old_age Always - 31 (Min/Max 19/38) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 2 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1934 SMART Error Log Version: 1 ATA Error Count: 44977 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] 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 44977 occurred at disk power-on lifetime: 101 hours (4 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 00 00 00 40 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 18 9f 18 9f 18 f0 18 9f 10:54:18.685 RECALIBRATE [RET-4] 00 02 00 00 00 00 00 00 00:02:32.685 NOP [Reserved subcommand] [OBS-ACS-2] 61 02 80 00 1f 98 40 00 00:02:32.716 WRITE FPDMA QUEUED 61 02 80 80 1e 98 40 00 00:02:32.716 WRITE FPDMA QUEUED 61 02 80 00 1e 98 40 00 00:02:32.716 WRITE FPDMA QUEUED Error 44976 occurred at disk power-on lifetime: 101 hours (4 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 00 00 00 40 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 18 9f 18 9f 18 f0 18 9f 10:54:18.685 RECALIBRATE [RET-4] 00 02 00 00 00 00 00 00 00:02:32.684 NOP [Reserved subcommand] [OBS-ACS-2] 61 02 80 80 d4 97 40 00 00:02:32.685 WRITE FPDMA QUEUED 61 02 80 00 d4 97 40 00 00:02:32.685 WRITE FPDMA QUEUED 61 02 80 80 d3 97 40 00 00:02:32.685 WRITE FPDMA QUEUED Error 44975 occurred at disk power-on lifetime: 101 hours (4 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 00 00 00 40 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 18 9f 18 9f 18 f0 18 9f 10:54:18.685 RECALIBRATE [RET-4] 00 02 00 00 00 00 00 00 00:02:32.684 NOP [Reserved subcommand] [OBS-ACS-2] 61 02 80 00 aa 97 40 00 00:02:32.685 WRITE FPDMA QUEUED 61 02 80 80 a9 97 40 00 00:02:32.685 WRITE FPDMA QUEUED 61 02 80 00 a9 97 40 00 00:02:32.685 WRITE FPDMA QUEUED Error 44974 occurred at disk power-on lifetime: 101 hours (4 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 00 00 00 40 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 18 9f 18 9f 18 f0 18 9f 10:54:18.685 RECALIBRATE [RET-4] 00 02 00 00 00 00 00 00 00:02:32.684 NOP [Reserved subcommand] [OBS-ACS-2] 61 02 80 80 f5 96 40 00 00:02:32.684 WRITE FPDMA QUEUED 61 02 80 00 f5 96 40 00 00:02:32.684 WRITE FPDMA QUEUED 61 02 80 80 f4 96 40 00 00:02:32.684 WRITE FPDMA QUEUED Error 44973 occurred at disk power-on lifetime: 101 hours (4 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 00 00 00 40 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 18 9f 18 9f 18 f0 18 9f 10:54:18.685 RECALIBRATE [RET-4] 00 02 00 00 00 00 00 00 00:02:32.682 NOP [Reserved subcommand] [OBS-ACS-2] 61 02 80 00 7d 96 40 00 00:02:32.683 WRITE FPDMA QUEUED 61 02 80 80 7c 96 40 00 00:02:32.683 WRITE FPDMA QUEUED 61 02 80 00 7c 96 40 00 00:02:32.683 WRITE FPDMA QUEUED SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 105 - # 2 Short offline Completed without error 00% 58 - # 3 Offline Completed without error 00% 0 - # 4 Offline Completed without error 00% 0 - SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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.
Oddly enough it had nearly 25 power on hours when I received the drive and had a ton of load cycles. the drive was sealed though.
Edit: im going to say this guy is junk. I did a test copy and its writing at 355kbps lol...
Last edited: