So my parity drive (8 month old 3 TB WD Red) failed and was disabled.  Luckily I had the drive that appeared to falsely registering as failed before I precleared it from this post...installed but not in the array.

 

https://lime-technology.com/forum/index.php?topic=49917.msg479645#msg479645

 

Both of these drives were purchased last December.  So I stopped the array and swapped the unassigned drive with the parity drive.  Everything seemed fine but then after parity was rebuilt it started doing a parity check and that drive failed.  Then I noticed that the original drive was now registering as being present so I switched them back.  Same thing...rebuild fine and then red x.  So I precleared the second drive and it was going fine until it finished the post read and it said preclear not successful

 

================================================================== 1.15b

=                unRAID server Pre-Clear disk /dev/sdb

=              cycle 1 of 1, partition start on sector 1

=

= Step 1 of 10 - Copying zeros to first 2048k bytes            DONE

= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE

= Step 3 of 10 - Disk is now cleared from MBR onward.          DONE

= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4      DONE

= Step 5 of 10 - Clearing MBR code area                        DONE

= Step 6 of 10 - Setting MBR signature bytes                    DONE

= Step 7 of 10 - Setting partition 1 to precleared state        DONE

= Step 8 of 10 - Notifying kernel we changed the partitioning  DONE

= Step 9 of 10 - Creating the /dev/disk/by* entries            DONE

= Step 10 of 10 - Verifying if the MBR is cleared.              DONE

= Disk Post-Clear-Read completed                                DONE

Disk Temperature: 37C, Elapsed Time:  22:31:00

========================================================================1.15b

== WDCWD30EFRX-68EUZN0  WD-WCC4N3LNL2EC

== Disk /dev/sdb has NOT been precleared successfully

== 0000000052D89000 - 7F 0000000052D89001 - 7D 0000000052D89002 - A6 0000000052D89003 - 1A 0000000052D89004 - 19 0000000052D89005 - DE 00000

00052D89006 - 63 0000000052D89007 - 07 0000000052D89008 - 8E 0000000052D89009 - 39

============================================================================

** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

          Seek_Error_Rate =  100    200            0        ok          0

No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.

0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.

0 sectors are pending re-allocation at the end of the preclear,

    the number of sectors pending re-allocation did not change.

0 sectors had been re-allocated before the start of the preclear.

0 sectors are re-allocated at the end of the preclear,

    the number of sectors re-allocated did not change.

root@Tower:/usr/local/emhttp#

 

I've attached the SMART test.

 

I'm curious because I just spent the past week installing dockers for Sonarr, Transmission and then the PVR I'm working on...started with TVheadend but couldn't get EPG working so switched to MythTV, and now all these issues.  Is it possible something else is going on or do I just have some bad luck on these two hard drives.  Been using 1, 1.5, & 2 TB greens pretty much carefree for about 6 years but recently decided to upgrade some aging disk with 3 TB Reds with the plan of cycling out the Greens.

tower-smart-20160825-1706.zip

SMART report is empty, disk probably dropped offline, check/replace cables/enclosure and post a new one.

Should have checked the log before I uploaded.  I'll repost this evening when I get home.  That's odd though that it went through nearly 24 hours of pre-clearing the drive and no one entered the room where they could have bumped the case yet a cable issue?

 

EDIT:  I tried to run a SMART test on the other disk but Unraid has it set to disable with a red x so it won't run the test.  I feel like something else must be wrong since it rebuilds parity just fine but then goes out the same place each time.  I loose cable would be more random as to when the errors occurred I think.  Also pre-clear seemed to be fine until the final post read check.

SMART report is empty, disk probably dropped offline, check/replace cables/enclosure and post a new one.

 

Here you go Johnnie.  Thanks for your time.

tower-smart-20160830-1959.zip

SMART looks fine, there are a few errors on the log but they look firmware related.

 

If you have it post the syslog from when the disk redballed, if not try a new rebuild and post the complete diagnostics (includes all SMART reports, syslog, etc) if it fails again.

Started over with the 2nd drive.  Ran SMART test with no errors and it's currently rebuilding parity.  Started last night so it should be done by the time I get home.  I'll post up everything after that. 

Update

 

I had already started a RMA with the first drive since it was the second time I've had an alert in the last few months.  I did the advance method so the new drive arrived over the weekend.  It's currently pre-clearing.  I did notice that the "new" drive was a refurbished drive, is that common for warranty replacements?

 

As for the Parity drive...it pre-cleared and rebuilt parity without issue this time and the extended SMART came back with no issue, so I'm counting that one as no issue for now.  I did notice something to keep track of.  somehow through the growth and evolution of my system the parity drive ended up being connected through a SATA expansion card.  I will work at getting that moved to an onboard slot after I get the new drive pre-cleared.  All the drives that have had errors in the past year were coincidentally connected through the card.  Of course the were also coincidentally all the WD-Reds.  I've never had issue with the older Greens that are still being used in my server.