deuxcolors Posted December 24, 2016 Share Posted December 24, 2016 Hey y'all! As a gift I was given a brand new 3TB hard drive. It is currently going through pre-clear. I'm debating which drive I want to swap out. I've got a 3TB whose SMART status is showing end of life, or I can swap one of the 2TB drives and gain an additional 1TB in the array. Let me know what you think, I've included the SMART report of the 3TB drive for those curious. Cheers. smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-1CH166 Serial Number: Z1F4KLNA LU WWN Device Id: 5 000c50 065eab30a Firmware Version: CC49 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Sat Dec 24 18:38:50 2016 CET 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 See vendor-specific Attribute list for marginal Attributes. 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: ( 575) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 314) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 120 099 006 Pre-fail Always - 237615080 3 Spin_Up_Time 0x0003 092 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 109 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 16 7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail Always - 27346366 9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 10776 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 84 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 094 094 000 Old_age Always - 6 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 031 031 000 Old_age Always - 69 190 Airflow_Temperature_Cel 0x0022 066 037 045 Old_age Always In_the_past 34 (255 255 40 24 0) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 61 193 Load_Cycle_Count 0x0032 070 070 000 Old_age Always - 61351 194 Temperature_Celsius 0x0022 034 063 000 Old_age Always - 34 (0 20 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 6232h+17m+05.454s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 293056072034 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 52236754466 SMART Error Log Version: 1 ATA Error Count: 6 (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 6 occurred at disk power-on lifetime: 10552 hours (439 days + 16 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 3d+16:49:56.782 READ DMA EXT 25 00 40 ff ff ff ef 00 3d+16:49:56.746 READ DMA EXT 25 00 80 ff ff ff ef 00 3d+16:49:56.642 READ DMA EXT 25 00 40 ff ff ff ef 00 3d+16:49:56.577 READ DMA EXT 25 00 60 ff ff ff ef 00 3d+16:49:56.566 READ DMA EXT Error 5 occurred at disk power-on lifetime: 10552 hours (439 days + 16 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 3d+16:49:48.651 READ DMA EXT 25 00 58 ff ff ff ef 00 3d+16:49:48.607 READ DMA EXT 25 00 58 ff ff ff ef 00 3d+16:49:32.924 READ DMA EXT 25 00 40 ff ff ff ef 00 3d+16:49:32.918 READ DMA EXT 35 00 10 ff ff ff ef 00 3d+16:49:32.917 WRITE DMA EXT Error 4 occurred at disk power-on lifetime: 10501 hours (437 days + 13 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 1d+13:28:22.558 READ DMA EXT 25 00 40 ff ff ff ef 00 1d+13:28:22.530 READ DMA EXT 25 00 20 ff ff ff ef 00 1d+13:28:22.525 READ DMA EXT 25 00 10 ff ff ff ef 00 1d+13:28:22.523 READ DMA EXT 25 00 10 ff ff ff ef 00 1d+13:28:22.519 READ DMA EXT Error 3 occurred at disk power-on lifetime: 10501 hours (437 days + 13 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 1d+13:28:12.307 READ DMA EXT 25 00 40 ff ff ff ef 00 1d+13:28:11.926 READ DMA EXT 25 00 40 ff ff ff ef 00 1d+13:28:11.896 READ DMA EXT 25 00 10 ff ff ff ef 00 1d+13:28:11.882 READ DMA EXT 25 00 10 ff ff ff ef 00 1d+13:28:11.871 READ DMA EXT Error 2 occurred at disk power-on lifetime: 10479 hours (436 days + 15 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 c0 ff ff ff 4f 00 15:27:05.419 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 15:27:05.419 READ FPDMA QUEUED 60 00 c0 ff ff ff 4f 00 15:27:01.412 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 15:27:01.412 READ FPDMA QUEUED 60 00 c0 ff ff ff 4f 00 15:27:00.855 READ FPDMA QUEUED SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 4444 - # 2 Short offline Completed without error 00% 3042 - # 3 Short offline Completed without error 00% 2322 - # 4 Short offline Completed without error 00% 1588 - # 5 Short offline Completed without error 00% 841 - 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. Link to comment
JorgeB Posted December 24, 2016 Share Posted December 24, 2016 I would replace it, disk has 10776 power on hours, there were read errors when it had 10552, 10501 and 10479 hours, so recently and more than once. Link to comment
garycase Posted December 24, 2016 Share Posted December 24, 2016 Agree => that's a fairly low # of hours, but the error history clearly shows the drive is deteriorating. No reason to take a chance with it. On the other hand, it depends on how badly you need additional space in the array => if you really need the extra 1TB you could replace one of the 2TB drives; and then look for a good sale on 3TB units to buy another one and replace the 3TB drive you asked about. It doesn't have any pending sectors; and only a few reallocated sectors -- so it IS still "good" to some extent => but I would NOT use it for much longer. The best approach is to replace the 3TB drive; and THEN buy another drive to add more space in the array. Link to comment
deuxcolors Posted December 24, 2016 Author Share Posted December 24, 2016 No rush on adding the extra TB, so I'll go ahead and swap out the bad 3TB drive. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.