itimpi

You can install them with existing settings via Apps->Previous Apps

Fix now available. Please confirm that it works as expected.

Thanks - that allowed me to see the error and will issue a fix. Has a || (logical OR) when I needed | (binary OR). The issue was specific to the case where backup was running.

I would not bother with these logs unless the issue occurs with the just posted release. If it does they would be very welcome

I agree, but it would be nice to know going forward whether firing this when needed should be the responsibility of plugins that need it, and if so they can then be updated to no longer need the workaround. Perhaps many people will not need the workaround anyway if they have a plugin (such as my Parity Check Tuning plugin) that issues this as part of its install process as the update_cron command is not plugin specific - it should pick up all cron jobs that any plugin has waiting to be activated.

You will still get an Unclean shutdown message if it WAS an unclean shutdown with the 2023-09-05 release but at least it should now be genuine. It is also now more prominent as it happens earlier in the start up sequence and is flagged as an alert (red) notification. Again this is only an informative message but I think it adds value as users will at least know if they have a shutdown issue if they get it when not expecting it. I might make the notification point to the part of the online documentation about troubleshooting unclean shutdowns if you click on it to help people find that. Any thoughts on that? I have currently disabled the message that indicates Unraid (not the plugin) is going to start an automatic parity check. I think that it would now be valid if you get it but I want to do more testing first and since it was only ever meant to be just an informative message disabling it does no harm.

A system restarting itself is abnormal. Do you have the system set to automatically start as soon as power is applied? I would also carefully check things like the fans in case you are getting a thermal related crash/reboot. The diagnostics only show what happened after the reboot and I did not spot anything obvious there. I would suggest things to try are: Enable the syslog server with the mirror to flash option set so that you get a syslog that covers the reboot (it will be in the 'logs' folder on the flash drive. Try booting in Safe mode to see if that changes things. You have a lot of things being installed via plugins so it is possible one of them is causing a problem.

There is also the possibility of a plugin that wants cron entries to be added to run this as part of installing the plugin (I know I do this for the Parity Check Tuning plugin). Not sure whose responsibility it should be to run this, but it would never cause problems to run it redundantly and maybe plugins should not rely it being part of the start up sequence as I can see the 6.13 release needing significant changes to the start up sequence.

I think that you could also use the Manual upgrade method (although it is getting a bit tight with a 1GB flash drive).

There is also the fact that on systems where it behaves itself I think the USB Creator tool can also partition and format drives larger than 32GB to FAT32?

Thought it was worth pointing out that I have made the 2023-09-05 release available which should stop incorrect detection of unclean shutdowns. Not sure, though, if there is not some other lingering problem that still needs resolving.

An alternative is to use a third party utility such as Rufus to format the drive as it can format drives larger than 32GB to FAT32 so then there is no wasted space (although as mentioned this is probably not relevant with Unraid).

Make sure you are on the latest release of the parity.check.tuning plugin. If you have it delete the 'parity.check.tuning.paused' file in the plugins folder on the flash drive. Looks like the plugin somehow has missed the fact the check has finished in your case although the latest version may fix this. If you continue to have problems after that then please enable the 'Testing' mode logging in the plugins settings and post your diagnostics after the problem has occurred so I can check out why.

This sounds like a UPS issue as there is no way the server should instantly lose power.

As I said it is easy to restrict incoming connections to whatever you want. There was no mention of what services those users should be able to access as restricting those may have implications.

I do not understand - are you saying that you want users on your local LAN to access the internet ? As I said it is easy to restrict incoming connections FROM the internet to what you want them to access.

You will typically configure the relevant User Shares to use the pool.

It is quite easy to make sure they can only get to your server, or specific IP addresses inside your LAN. what you do not mention is what control you want to have over what on your server can be accessed. For example the simplest solution might allow access to the Unraid GUI - would you be happy with that?

What time did the backups finish? To look at why I would need the testing mode logging to be activated in the plugin settings covering that period and the resulting diagnostics posted.

I wonder if you got an unclean shutdown (or the plugin erroneously thought one had happened) as that would stop anything being restarted.

At the moment the performance of ZFS when used in the main array is worse than the other options for file system type. Not sure when/if a fix for this will be available.

Not quite sure what point you are trying to make? The diagnostics includes the current syslog from RAM. The only time I would expect to see a need to post a syslog separately is when it is one resulting from the syslog server.

Are you sure? I am sure it used to. I will have to check this out again.

The only part of the USB drive that really matters is the ‘config’ folder and all its contents as that is where all user settings are stored. However most people seem to like having the Unraid system files as well.

In which case you will not get a spurious notification from the Parity Check Tuning plugin 😊