I have come across a strange problem that I would like to request some input on.

 

One of my disks (4TB) was showing signs of fatigue (SMART error 187) so I prepped a new one (6TB) and precleared it. It's disk5, on sdl.

 

Followed the instructions on how to replace:

 

1.    Stop the array
2.    Unassign the old drive if still assigned (to unassign, set it to No Device)
3.    Power down
4.    [ Optional ] Pull the old drive (you may want to leave it installed for Preclearing or testing)
5.    Install the new drive
6.    Power on
7.    Assign the new drive in the slot of the old drive
8.    Go to the Main -> Array Operation section
9.    Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt), and click the Start button
10.    The rebuild will begin, with hefty disk activity on all drives, lots of writes on the new drive and lots of reads on all other drives
 

But I get stuck at step 10 as the rebuild doesn't begin at all. GUI becomes unresponsive for some time and then returns without having initiated any rebuild.

 

I can start the array if I set the disk slot to no device. Disk is recognized and shows up with a blue icon for "new drive".

 

Really don't know what to do. Have attached the preclear report and syslog.

 

Hope someone has some words of enlightenment :-)

 

preclear_report_S4D0P7DJ_2017.12.24_23.01.03.txt

tower-syslog-20171228-1910.zip

v6.3.5 doesn't support 4kn disks, you'll need to update to v6.4, currently in pre-release.

Oh, wow. I was fully unaware that the disk was "special" - I thought it was just a regular 6TB drive :-(

 

The disk is run from a DELL H310 crossflashed to IT mode. Will this be a problem for the controller or is the fact that it is "recognized" proof that it will work, once I use 6.4?

 

And how do I go about updating to 6.4 now that the array is degraded? Should I go back to the old 4TB drive, upgrade and then replace to 6TB?

Edited December 28, 20178 yr by t33j4y

3 minutes ago, t33j4y said:

Will this be a problem for the controller or is the fact that it is "recognized" proof that it will work, once I use 6.4?

It's not a problem for the controller, only unRAID pre v6.4

 

You can upgrade with the array degraded:

 

 

Thanks - will look into this. It seems that there are some improvements in 6.4 regarding certificates and encryption that I should probably understand before diving in.

 

Thanks again for the swift response!