All drives must have the following:

• SMART overall-health self-assessment test result: PASSED
  
• Current Pending Sector RAW_VALUE of zero
  

Ok, the drive has finished rebuilding, and array is now all green, I then did a SMART test in unmenu and the current pending sector and Offline_Uncorrectable are still 1 and not Raw Value Zero.  Do I need to power down and power back up for this to change?  Do I perhaps need to do something with the jumper?

I made a mistake. Not Offline_Uncorrectable. I corrected it to Current Pending Sector.

The pending sector must be resolved before progressing.

 

 

stop array & unassign drive

start the array and stop the array.

 

Run pre-clear on the drive. See here: http://lime-technology.com/forum/index.php?topic=2817.0

 

The pre-clear can be repeated until the Current Pending Sector RAW_VALUE is zero.

 

Can you RMA this drive? It may have to be replaced.

After the rebuild it is still showing the Current Pending Sector of 1 (Disk 1: WARNING - Current_Pending_Sector it is now 1 (warning threshold is 1))

 

I also shut down the server, booted it  up and the smart report still shows the Current Pending Sector as 1.  Is there anything I should do?  Maybe try removing the 7-8 jumper and setting it to 4k aligned and rebuilding again, or perhaps pre-clearing that drive somehow?

 

I cannot RMA since this drive has been running in my Unraid since I first set it up back on 4.5, not sure if we should do something with the jumpers before doing any pre-clear on the drive, would that help at all?

 

Run pre-clear on the drive. See here: http://lime-technology.com/forum/index.php?topic=2817.0

 

The pre-clear can be repeated until the Current Pending Sector RAW_VALUE is zero.

 

Yes. Run pre clear. Changing the jumper will not improve performance in any way.

Ok, I will do that now,  per your instructions it says to stop array and then run pre-clear, I absolutely must have my array stopped and not accessible while running the preclear?    Would it be at all possible to stop array, unassign drive start array and then do the preclear on sdc so I have access to my array while it preclears?  (I figure it will take a long time)

Yes. But the array will be unprotected from a disk failure until the drive is rebuilt.

Ok, I have array started but disk unassigned but all of a sudden my unmenu died, and I was going to use the mymain to track the status of the preclear.  I have absolutely no idea why unmenu just died, it seems to be running when I ran:

 

root@Tower:/boot/unmenu# ps -ef | grep awk

root    18688 18684  0 20:21 pts/0    00:00:00 awk -W re-interval -f ./unmenu.awk

root    19101  7703  0 20:22 pts/0    00:00:00 grep awk

 

root@Tower:/boot/unmenu# netstat -an | grep 8080

tcp        0      0 192.168.0.160:8080      192.168.0.200:50687    ESTABLISHED

 

I cannot think of anything that would have caused it, I went into pkg manager shortly before SSHing into Tower and everything seemed okie dokie and then right before I try the preclear I cannot get it to come up.  I was wanting to use it to monitor progress on it, which is why I have not started the preclear yet.  Any ideas or commands I can use to diagnose why in the world it is not coming up?

 

The regular tower is coming up just fine at http://tower/main.htm for example

Ok, finally finished the preclear, and I think it was a success.  I am currently rebuilding the drive and now the Current_Pending_Sector Raw Value is Zero which I think was the goal.  But I still have Offline_Uncorrectable value of 1, so I am not sure if that is ok, or if it will prevent me from upgrading to 5.0 still and I need to pre-clear some more times.

 

If not then am I good to give it a shot to attempt the upgrade to 5.0 after my drive rebuilds?  Also is UnMenu compatible with 5.0 or is it just a 5.x thing?

 

Don't worry about offline uncorrectable. It should not go down. Current_Pending_Sector is one to watch.