inh Posted May 11, 2014 Share Posted May 11, 2014 I started a long SMART test on a 3TB WD green drive yesterday. It said it should finish in 483 minutes. I waited that long before checking again, but it hadn't finished. I then tried to run a short test, and it said that another test was in progress with 10% remaining. Now, 14 hours after trying to start a short test, it STILL says 10% remaining. Here is the output when I pull a report: RT 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 200 200 051 Pre-fail Always - 1 3 Spin_Up_Time 0x0027 147 145 021 Pre-fail Always - 9633 4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3001 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 076 076 000 Old_age Always - 17804 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 195 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 48 193 Load_Cycle_Count 0x0032 124 124 000 Old_age Always - 229003 194 Temperature_Celsius 0x0022 126 110 000 Old_age Always - 26 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] And the output of trying to start a short self test, which hasn't changed in 14 hours: === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Can't start self-test without aborting current test (10% remaining), add '-t force' option to override, or run 'smartctl -X' to abort test. I'm concerned it got to a really trashed portion of the drive or something and is taking forever to pick through it, or maybe the SMART test just got hung up on something. Any ideas? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.