Not sure where to report this but I found that running preclear with the -l option before I precleared a new disk told me that all the disks were available to preclear rather than just the unallocated ones.

 

I am using unRaid 5.0 rc15a and preclear 1.13

 

I went ahead anyway as I was very sure which disks were the new ones (triple checked and fingers crossed) but did some digging while the preclear was running. I think the problem lies with changes to the structure of /config/disk.cfg but thats as far as I can go.

 

Was the array started at the time?  I have seen this being the case if the array is not yet started.

Was the array started at the time?  I have seen this being the case if the array is not yet started.

 

I must admit I would prefer it if the script could determine what disks were configured even when the array was not yet started, but I expect that there is some technical reason why this is not being done.

Yes the array was started.

Yes the array was started.

Strange then - certainly not seen that behaviour on my system.

 

I guess we need to wait to wait to see if Joe L. has an idea what might cause this behaviour.

Apologies itimpi, it looks like you were right.

 

I've just tried to repeat the problem by running in another screen session and the -l option reports just the two disks I was expecting. It must be that the array wasn't started when I tried last time, I'd had the machine on and off a few times to put the disks in and the array must have been off.

 

When the preclear finishes I'll try and repeat what I saw the first time and post the results.

 

The array does not have to be started for pre-clear to show the correct disks.  If you saw all of them, something else was wrong.    But at least all's okay now.

 

Hopefully Joe L will review this -- he may have some insight into why you saw all of the disks the first time.

 

The array does not have to be started for pre-clear to show the correct disks.  If you saw all of them, something else was wrong.    But at least all's okay now.

 

Hopefully Joe L will review this -- he may have some insight into why you saw all of the disks the first time.

 

there are two files examined to determine assigned drives:

/boot/config/disk.cfg

and

/var/local/emhttp/disks.ini

 

Additionally, any disk that is "mounted" is not a candidate.

 

Temporary file is used to group the disks that are in use. That temp file is under /tmp

/tmp/preclear_assigned_disks1

 

All I can think of is that /tmp was not writable (at least one add-on package changed the permissions of /tmp, causing all kinds of problems) or the disk.ini file had not yet been written to the file-system. 

 

Joe L.