Hey, so i rebuild my server (MB and added RAM)

 

While doin so i was multiple times restarting server adding things and testing and so on.

 

At some point i might have startet the array without a disk (i guess cable got loose).

 

I would suggest adding some sort of "ARE YOU REALLY SURE YOU WANT TO START THE ARRAY WITH DISK(S) MISSING" when clicking start array. - or a checkbox.

 

I was on mobile and i didnt see that there was a disk missing...

Edited November 30, 20187 yr by nuhll

I added a confirmation checkbox before starting the array when a disk is missing.

Available in next version.

 

3 minutes ago, bonienl said:

I added a confirmation checkbox before starting the array when a disk is missing.

Does that include missing cache pool devices? It would be great if they are included in the warning.

Made another update which adds a confirmation checkbox when a cache disk is missing.

13 minutes ago, bonienl said:

Made another update which adds a confirmation checkbox when a cache disk is missing.

Thanks, I feel that's important especially since if autostart is enable the array would still autostart with a cache member missing, unlike an array disk.

Ah, my update addresses a missing cache device when the array is stopped and the user tries to start thru the GUI.

It requires an update to emhttp to prevent autostart when a cache device is missing. Something only @limetech can do.

17 minutes ago, bonienl said:

It requires an update to emhttp to prevent autostart when a cache device is missing. Something only @limetech can do.

I suspected that, hope Tom can change that when possible, even with single device cache there can be issues, for example if the user is using the default /mnt/user paths for the docker and libvirt images and they are on cache, if the array starts without it new images will be created on the array disks and can then cause confusion, but mostly for multiple devices cache it can cause issues with the pool.

Thanks for the fast response and work!

6 hours ago, johnnie.black said:

I suspected that, hope Tom can change that when possible, even with single device cache there can be issues, for example if the user is using the default /mnt/user paths for the docker and libvirt images and they are on cache, if the array starts without it new images will be created on the array disks and can then cause confusion, but mostly for multiple devices cache it can cause issues with the pool.

 

Yes we can fix that.  This will be included in a larger change that also addresses this one:

 

On 12/1/2018 at 11:03 AM, bonienl said:

Made another update which adds a confirmation checkbox when a cache disk is missing.

Just noticed there's a bug here, with v6.6.6 Start button is not inhibited and still works and the array starts without clicking the checkbox.

 

10 minutes ago, johnnie.black said:

Just noticed there's a bug here, with v6.6.6 Start button is not inhibited and still works and the array starts without clicking the checkbox.

Thanks, corrected for the next version.