I'm running into a problem adding a new data drive to my array.  I've done some searching and cannot seem to locate a solution.  My apologies if I've missed something.  Out of the gate, let me say that I was  running version 6.0.1 initially, and upgraded to 6.1.9 today to see if that corrected the problem.  It has not.

 

My UnRAID server has 12 drive connections.  It's been running for years, most recently with 1 parity disk, 9 data disks, and 1 cache disk.  I ran out of space, and purchased an additional 3TB Western Digital Red NAS drive.  My UnRAID server has a 3TB parity drive and several other 3TB drives, so compatibility shouldn't be an issue.  Below is what I attempted:

 

-Ran full partiy check.  Passed with no errors.

-Shutdown system and installed new drive in bay.

-Startup system and new drive is recognized with full identifying string.

-Assign drive as Disk 10.

-Check box to allow the drive to clear.

-After drive clears, the Disk 10 slot on the Main menu is empty.

-Click Disk 10's pulldown shows "-3TB (sdb)" instead of the full identifying string.

-Attempting to assign "-3TB (sdb)" simply causes the screen to refresh and the pulldown to show "unassigned" once more.

 

I've attempted reboots and re-clears.  Upgraded to 6.1.9.  Changed SATA cables Nothing seems to help.  Any insight is appreciated.

 

Diagnostics file is too large to attach, so here is a link:  https://www.dropbox.com/s/6uxxblhed1bdmz9/archive-diagnostics-20160615-1704.zip?dl=0

 

Please see Need help? Read me first!, and attach the diagnostics zip.

My apologies.  Had captured it but forgot to attach.  Sadly the full zip file appears too large to attach.  Instead I've added a link to my original post.  Thanks.

As you said, the drive was recognized and initialized without issue.  It responded correctly in every way, and the partition table was read, with one partition found.  But within seconds of starting the clearing, the system began spewing errors about device faults, all on the new drive.  And never once as far as I can see ever changed the error, always device faults.  The error pattern was a little different than I'm used to, so can't say for sure what the fault was.  I have to wonder if this new drive added was one too many for the power supply, or the power rail it's on.  Faulty power might explain the error messages.  Otherwise, it's a defective drive or a defective SATA port (which seems unlikely as it's the very first port on the motherboard).  You might swap ports and cables around, see if that tells you anything.

Thanks for the insight.  I'll switch a few things around and see what happens.  I'm fairly confident it's not a power issue, but one never knows.

After several rounds of testing and hardware swapping, it looks like I just have bad luck and Amazon shipped me a bum drive.  Thanks again for the trouble-shooting help.