[Preclear plugin]

I suspect this is because I have a permanently empty bay which I use for preclearing, then when its complete I move the drive to its 'correct' location.

 

Do you mean that you physically move the drive without shutting down the server?

 

I stop the array, pull the drive, relocate the drive, restart the array.

 

This is because you removed the old drive and the Linux UDEV subsystem reused it's device name. You can easily remove the old instance by clicking the X icon next to the new drive name.

 

So when I hover over the red X, the tooltip says "Stop Preclear" (obviously there isn't one ongoing) and clicking it refreshes the page, but doesn't actually change anything that I can see - I've still no option to start a preclear. Pretty sure by now that Im missing something obvious, but not sure what it is!

 

Is it mounted by Unassigned Devices?

 

I just got some help from gfjardim via PM - my problem was that I was missing the Unassigned Devices plugin - with it I was able to kick off my preclear as I wanted. I'd just like mostly to give thanks to gfjardim for his help here - there wasn't a bug, rather a misunderstanding on my part, and the support I got was the kind of top notch you'd not dare hope for even if you'd parted with a great deal of money. Really above and beyond the call of duty and I am very thankful. Outstanding

 

As a follow up to this, I've established that it does count as a very minor bug - the problem is that the 'stop pre clear' Red X button doesn't clear down the status of a device if you click it in Safari. It works just as intended in Chrome. Just submitting for clarity!

[Preclear plugin]

I suspect this is because I have a permanently empty bay which I use for preclearing, then when its complete I move the drive to its 'correct' location.

 

Do you mean that you physically move the drive without shutting down the server?

 

I stop the array, pull the drive, relocate the drive, restart the array.

 

This is because you removed the old drive and the Linux UDEV subsystem reused it's device name. You can easily remove the old instance by clicking the X icon next to the new drive name.

 

So when I hover over the red X, the tooltip says "Stop Preclear" (obviously there isn't one ongoing) and clicking it refreshes the page, but doesn't actually change anything that I can see - I've still no option to start a preclear. Pretty sure by now that Im missing something obvious, but not sure what it is!

 

Is it mounted by Unassigned Devices?

 

I just got some help from gfjardim via PM - my problem was that I was missing the Unassigned Devices plugin - with it I was able to kick off my preclear as I wanted. I'd just like mostly to give thanks to gfjardim for his help here - there wasn't a bug, rather a misunderstanding on my part, and the support I got was the kind of top notch you'd not dare hope for even if you'd parted with a great deal of money. Really above and beyond the call of duty and I am very thankful. Outstanding

[Preclear plugin]

I suspect this is because I have a permanently empty bay which I use for preclearing, then when its complete I move the drive to its 'correct' location.

 

Do you mean that you physically move the drive without shutting down the server?

 

I stop the array, pull the drive, relocate the drive, restart the array.

 

This is because you removed the old drive and the Linux UDEV subsystem reused it's device name. You can easily remove the old instance by clicking the X icon next to the new drive name.

 

So when I hover over the red X, the tooltip says "Stop Preclear" (obviously there isn't one ongoing) and clicking it refreshes the page, but doesn't actually change anything that I can see - I've still no option to start a preclear. Pretty sure by now that Im missing something obvious, but not sure what it is!

 

Is it mounted by Unassigned Devices?

 

This is it in unassigned devices:

 

 

The tooltip over its blue icon shows "New Device" but it looks as though the only available action is to spin it down. Thank you for replying to my questions, gfjardim - it is very much appreciated.

[Preclear plugin]

I suspect this is because I have a permanently empty bay which I use for preclearing, then when its complete I move the drive to its 'correct' location.

 

Do you mean that you physically move the drive without shutting down the server?

 

I stop the array, pull the drive, relocate the drive, restart the array.

 

This is because you removed the old drive and the Linux UDEV subsystem reused it's device name. You can easily remove the old instance by clicking the X icon next to the new drive name.

 

So when I hover over the red X, the tooltip says "Stop Preclear" (obviously there isn't one ongoing) and clicking it refreshes the page, but doesn't actually change anything that I can see - I've still no option to start a preclear. Pretty sure by now that Im missing something obvious, but not sure what it is!

[Preclear plugin]

A bug report of sorts to raise - I just popped a new disk in (fresh out of a virgin anti static bag) and went to use the plugin.

 

I have previously used it to pre clear another disk, which (perhaps unrelated) was the same make/model/capacity.

 

The disk shows as pre clear having already completed, so there is no option to start it. Similarly in the main unraid dashboard it shows in Unassigned Devices as "Preclear in progress... Preclear Finished Successfully!"

 

I suspect this is because I have a permanently empty bay which I use for preclearing, then when its complete I move the drive to its 'correct' location. This means (again, speculative) that the new drive has come up with the same sdX as the previous successful pre clear, and the plugin thinks its already been dealt with.

 

If I run the old-style preclear_disk.sh script with -l, it does indeed identify this new one as being in need of a pre clear, and this serves as my stopgap method using the old screen approach.

 

Im not sure if a reboot would fix this, and its not a show stopper by any means, but I thought it couldn't hurt to raise it. Thank you for your ongoing efforts, gfjardim