May 9, 201214 yr I had my server down for a few days and booted it up tonight. I noticed that the drive light was on so went to take a look in the config. I noticed there's a red ball next to the drive. I shut down and rebooted and the drive light is off now but the red ball is still next to the drive. I ran a smart test but not sure what to make of it. I'd appreciate some help. I'm going to shut down the server and recheck the cabling in the meantime. 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 135 135 054 Pre-fail Offline - 97 3 Spin_Up_Time 0x0007 133 133 024 Pre-fail Always - 413 (Average 412) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 164 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 146 146 020 Pre-fail Offline - 29 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 4552 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 231 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 231 194 Temperature_Celsius 0x0002 166 166 000 Old_age Always - 36 (Lifetime Min/Max 21/40) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 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] 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.
May 9, 201214 yr Author I rechecked the wiring and all. Powered back up. Red ball is still there. I have about 1.8TB of data on this 2GB drive. I'm not sure what I should do? Help... Should I run a parity check? Do I first need to use the Trust My Array feature then run the parity check?
May 9, 201214 yr Rebuild the drive: http://lime-technology.com/wiki/index.php/Troubleshooting#How_do_I_re-enable_the_drive.3F
May 9, 201214 yr Author I just want to make sure I'm clear. By rebuild you mean "start a parity-reconstruct of the disk"? Right?
May 9, 201214 yr Author I have another quick question which I'm a little confused on. I started a parity rebuild which is about 25% done. I noticed that all the drives are showing writes on them with no errors. If the parity rebuild is rebuilding drive 9 in my array why is there writes on my other discs? Also should the writes on my rebuilt disc equal the amount of the drive size minus the free space?
May 9, 201214 yr All disk should have a few writes from being mounted. Parity is computed for the entire physical disk.
May 9, 201214 yr I just want to make sure I'm clear. By rebuild you mean "start a parity-reconstruct of the disk"? Right? yes
Archived
This topic is now archived and is closed to further replies.