November 30, 20169 yr One of my unRaid machines has a disk with a little red X -- I don't know how long that has been there I just found it this morning. The disk with the X is the newest HD in the array -- it is a WD 6TB Red and less than 3 months old. I ran both the short and the long test and there are no errors reported. I then tried to rebuild the array by taking the drive offline and then reassigning it as a new drive -- as soon as I start the reconstruction process there is a bunch of errors. Test the drive again just with the short test -- again no errors. What am I doing wrong?
November 30, 20169 yr Check the SATA and power cables to the disks. If that doesn't help post your diagnostics. https://lime-technology.com/forum/index.php?topic=39257.0
November 30, 20169 yr Author The case has 4 trays -- I thought it might be the connection as well so I took the drive out but problem persists. I guess it could be something with connection on that tray. This is the short test results. I'll start the long test === 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: ( 7424) 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: ( 727) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303d) 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 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 099 099 000 Old_age Always - 1143 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 0 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 387 194 Temperature_Celsius 0x0022 119 114 000 Old_age Always - 33 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 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 2 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 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 1143 - # 2 Short offline Aborted by host 90% 1140 - # 3 Short offline Completed without error 00% 1140 - # 4 Extended offline Completed without error 00% 1139 - # 5 Short offline Completed without error 00% 1126 -
November 30, 20169 yr Author Sorry I thought the diagnostics was just the SMART test. I read the link and now I realize it is more. After reading John_M's suggestion I tried the resetting all the connections again even though I had already done that. The drive is 48% reconstructed which is much further into the process then it ever got before. Hopefully it is just a connection issue. If the issues returns I'll post the diagnostics following the instructions in the link provided.
Archived
This topic is now archived and is closed to further replies.