What next.  i have been reading through all the trouble shooting information.  Based upon the info I am reading, I don't think the drive is bad.  So I am providing my extended smart report.  I would like an expert to look at it and advise.  To provide a little info.  I had a hard shutdown of the unraid server and now I have one disk that is redballed.  I am not sure why or what I should do next.  I have checked all power connections and nothing felt loose.

 

I really appreciate any help recovering from this issue

Bill

smart.txt

What next.  i have been reading through all the trouble shooting information.  Based upon the info I am reading, I don't think the drive is bad.  So I am providing my extended smart report.  I would like an expert to look at it and advise.  To provide a little info.  I had a hard shutdown of the unraid server and now I have one disk that is redballed.  I am not sure why or what I should do next.  I have checked all power connections and nothing felt loose.

 

I really appreciate any help recovering from this issue

Bill

That drive has 1462 current pending sectors.  I personally wouldn't trust it.

I appreciate the feedback.  So I have a new 3tb wd red to replace it (my parity is a 3tb).  Should I install the new drive, pre clear it then replace the failed drive or is it ok to take the new drive as is and replace the failed drive.  I am running unraid 5.05.

 

Thanks for the help

So I am going to go ahead an preclear the disk.  It is a 3tb WD Red.

 

is this still the current preclear command to run for Unraid 5.05

 

preclear_disk.sh -A /dev/sdc (sdc being the new disk).

 

How do I run this command with the screen option in putty under telnet?  In case my wife reboot the computer I am running preclear from.

 

Thanks

Bill

The -A switch has no affect on drives >2.2TB. You might run it with the -v switch to make sure you have the latest version, 1.15.

 

Do you have screen installed? It is not built-in.

So I precleared the 3tb WD red drive.  I ran into an issue.  I have thought of a solution and want to make sure that my solution is valid and safe.

 

I have a 3tb Toshiba Drive as a parity drive.

I had a 2tb WD green data drive go bad.  So I bought a 3tb WD red drive as it's replacement.

 

On to the problem

 

Unraid thinks the 3tb WD Red is bigger than the 3tb Toshiba drive.

 

Here is my proposed solution

I have a 2tb cache drive.  Unassign the Cache drive.  Reassign it as a replacement for the Bad Data drive.  Let the array rebuild the drive.  Upon completeion, run a parity check.  As long as that is good, replace the parity drive with the 3tb WD Red.  Allow it to rebuild the parity drive.  Run a parity check.  Replace the a 2 TB drive with the Toshiba 3tb drive.  Then finally reassign the cache drive.

 

Thoughts

 

Thanks ahead of time for any feedback

Bill

See here: http://lime-technology.com/forum/index.php?topic=10866.0

Unraid thinks the 3tb WD Red is bigger than the 3tb Toshiba drive.

See here: http://lime-technology.com/forum/index.php?topic=10866.0

It is very important to find out WHY the toshiba is smaller, so you can keep it from happening again, and figure out if any of your other drives have a HPA. I wouldn't proceed with any drive swapping until that mystery is solved. Other than that, your solution sounds good to me. After the Toshiba is out of the array, you can remove the HPA from it and move on. Keep in mind any time you mess with the drive size it will appear as a different drive to unraid, so you will effectively be erasing it, so don't mess with HPA removal on current array drives.

The Toshiba does have HPA detected on it.  SO what I have done so far is:

 

Reassigned the cache drive to replace the bad drive.  Let the disk be rebuilt.  Next I am going to get into the bios and see about disabling hpa.  Then I am going to remove the parity drive and replace it with the WD red.  I will then follow the described procedures to remove the hpa partition. 

 

Once the hpa has been removed, should I preclear the 3tb disk again?

 

Thanks for all the help

Bill

First STOP HPA or it may infect additional disks. BIOS need to default to an off state. Otherwise when the CMOS battery dies HPA will affect 1 or more disks leading to data loss.

I think the reason I am not seeing it on the other disks is because they are attached to a Supermicro AOC8.  I have not confirmed this but the Seagate might've been the one I had to attach to the mobo sata port. Any way I am getting ready to receive a M1015 and expander.  I then will move my physical unraid back to my esxi server but first I have to get past these issues.

 

Bill