I just upgraded one of my servers to version 5.  I have 5 disks in the array plus parity.  I have two unassigned disks, one precleared and one brand new.  I've started the array and everything seems fine.  I want to preclear the new drive but preclear (-l flag) thinks they are all assigned to the array.  I've used the -t flag to check all disks and each time its says its part of the array.  One thing I did notice is the drives (sda, sdb etc) don't have the same letters as before the upgrade.  Could things have become mismatched?  I'm not sure how to troubleshoot this.

 

Any suggestions appreciated.

 

Thanks

 

dave

 

 

First, be CERTAIN that you know which drives are actually assigned within the array ==> print a copy of the Web GUI page so you'll have it handy with no doubts about the serial #'s of the drives.

 

Next, set the array so it does NOT auto-start [settings - Disk Settings - Enable Autostart = No]

 

Then Stop the array, and reboot the system.

 

Now log on to root and the pre-clear script should allow you to preclear ANY disk.  Be CERTAIN you're choosing the one you want, and simply do it.

 

Note:  Be sure you're using the latest version of the pre-clear script.  If any doubt, simply download it again from the bottom of the first post here:  http://lime-technology.com/forum/index.php?topic=2817.0

Unfortunately the preclear script is very tough...

 

I have a new build at home where I did and still do various testing.

Last time I wanted to perform a preclear on the drives of the array because

I did not need the array any more. I also need to have those drives precleared once more.

 

So, I booted the server, did NOT start the array and also did NOT access the GUI but the

drives are still not selectable for preclearing.

Then I studied all documented options for the preclear command but unfortunately

there is no override switch.

Joe L. did a good job to ensure that you can't preclear an assigned drive.

But sometimes there is a need to do so...

 

I'm using the latest preclear version.

 

With v5.0 pre-clear does not correctly recognize the drives in the array until the Web GUI has been accessed at least once.    Joe L is aware of this, but has not released an updated version of the pre-clear script that resolves it.

 

The workaround is simple -- just Start the array; and access the Web GUI.    Then the -l command will correctly list the disks; and pre-clear will refuse to pre-clear an array disk.

 

There IS, of course, a very simple workaround if you want to force a pre-clear on any drive.  BE CAREFUL doing this -- if you accidentally pre-clear an array disk there's no way to recover.    All you have to do is create another flash drive with UnRAID (the free Basic version is fine); put the pre-clear script on that flash drive;  then just boot to that instead of your normal flash drive.    Do NOT assign any disks (or do anything else with the Web GUI) ==> simply run the pre-clear script and do any pre-clears you want to do.    Then, when done, just swap back to your normal flash drive.

 

 

First, be CERTAIN that you know which drives are actually assigned within the array ==> print a copy of the Web GUI page so you'll have it handy with no doubts about the serial #'s of the drives.

 

Next, set the array so it does NOT auto-start [settings - Disk Settings - Enable Autostart = No]

 

Then Stop the array, and reboot the system.

 

Now log on to root and the pre-clear script should allow you to preclear ANY disk.  Be CERTAIN you're choosing the one you want, and simply do it.

 

Note:  Be sure you're using the latest version of the pre-clear script.  If any doubt, simply download it again from the bottom of the first post here:  http://lime-technology.com/forum/index.php?topic=2817.0

 

Thanks for the help Gary.  With this method do I have to wait until the preclear is complete before starting the array and using the server?  Or can I start the preclear and then start the array?  Preclear_disk.sh -v tells me I'm using version 1.13.

 

EDIT:  I'm still having the same problem.  I think I'll use the second option and create a new unraid copy on a different thumb drive.

As you noted, the disadvantage of booting to a different flash drive is that your system isn't usable until the pre-clear finishes and you reboot to your normal flash drive.

 

... but it DOES let you get the pre-clears done 

 

=>  If you happen to have a spare PC, you can obviously do the pre-clears on it using the same extra flash drive.

 

I've just finished a parity check.  Would using the new config utility clear things up for preclear_disk.sh?  I realize I would have to do a new parity sync.

I've just finished a parity check.  Would using the new config utility clear things up for preclear_disk.sh?  I realize I would have to do a new parity sync.

 

Well I did it and it seems to have worked.  The array is doing a parity sync and the new drive is being precleared.  I may not have been so eager to experiment if I didn't have a complete backup of the data on another server. 

 

 

Good to see I'm not the only one who actually backs up my data 

 

You obviously got this done before I had a chance to respond -- but Yes, a New Config will let you reset the configuration; so you can start a pre-clear; then Start the new config and everything will work fine as long as you don't accidentally clear the WRONG disk 

 

 

Yeah I think I checked the serial # at least 7 times.  I'm one of those people who locks the door when they leave the house, knows they locked the door but still has to get out of the car and check it again. 

 

Thanks for you help Gary.

 

ds