July 18, 201312 yr I have a red ball beside disk5. I replaced the SATA cable and made sure all cables were plugged in. It still comes up red I have attached the syslog syslog.txt
July 18, 201312 yr A drive gets a red ball because a write to it failed. Once that happens the red ball won't go away unless you do something like rebuilding the drive from parity. At least that's my understanding.
July 18, 201312 yr Author Can someone confirm this? What is the best way to get my disk5 green again?
July 18, 201312 yr Assuming you know the drive is still good you can follow the procedure under the heading "How do I re-enable a failed disk?" found in the FAQ: http://lime-technology.com/wiki/index.php/FAQ#How_do_I_recover_from_a_hard_disk_failure.3F
July 18, 201312 yr The procedures outlined in the link above [unassigning; rebooting; then re-assigning the drive] will indeed force a rebuild of the disk. But remember that it failed for a reason ... so be sure you check all the cables [unplug them, then reseat them ... or if in a hotswap cage, remove and reseat the drive]. OR --- better yet -- remove the drive, attach it to another PC, and run the manufacturer's diagnostics (extended version) to confirm it's okay. Any doubts? ... replaced the drive !!
July 18, 201312 yr This line in your smart report means that rebuilding on the current disk will likely not work - at least correctly. 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 167 You need to either replace the drive with a new drive that doesn't have pending sectors or run some preclear cycles on it until the number (167) goes to zero. Once you have that you can try to rebuild on the disk again. I would replace the disk however as it has alot of power on hours and some other smart errors (Multi_Zone_Error_Rate and Offline_Uncorrectable) that won't fix themselves with a preclear - for me at least.
July 18, 201312 yr The thing to do is check whether rebuilding the disk resets the pending reallocated sectors to zero. If it does you are probably OK. If not you should consider replacing the disk.
July 19, 201312 yr Rebuild SHOULD clear out the pending reallocations, unless it encounters more after-the-face. The drive will not write to a "pending" sector ... when a write is attempted to a sector marked for reallocation, that is when it's actually reassigned to a spare. A SMART report after rebuild should show zero pendings. HOWEVER, the fact you've had quite a few means there's a good chance the drive has some bad areas and may get worse. While you don't necessarily have to replace it immediately, I'd certainly be sure you have a pre-cleared spare handy ... and check the SMART report for that drive regularly, and if you see further signs of degradation, replace it.
July 19, 201312 yr Rebuild SHOULD clear out the pending reallocations, unless it encounters more after-the-face. The drive will not write to a "pending" sector ... when a write is attempted to a sector marked for reallocation, that is when it's actually reassigned to a spare. A SMART report after rebuild should show zero pendings. HOWEVER, the fact you've had quite a few means there's a good chance the drive has some bad areas and may get worse. While you don't necessarily have to replace it immediately, I'd certainly be sure you have a pre-cleared spare handy ... and check the SMART report for that drive regularly, and if you see further signs of degradation, replace it. The drive will attempt to write to the pending sector. If the write fails then the sector is reallocated and the reallocated sector count goes up and the pending count goes down. If the write succeeds the pending count goes down by one.
July 19, 201312 yr Author Drive rebuild worked. Here is a smart report after the rebuild smart_report_disk5.txt
July 20, 201312 yr Drive rebuild worked. Here is a smart report after the rebuild Looks ok. Keep monitoring the drive; particularly, the pending sector count.
Archived
This topic is now archived and is closed to further replies.