itimpi

Sometimes simply rewriting all the bz* type files can help.

Don't forget it can also be power related.

Have you used Apps->Previous Apps to repopulate the docker container binaries? No idea on the VMs as from your description they should not have been affected.

Looking at the syslog this looks more like a connection issue (power or SATA) rather than a disk failure. Connection issues are far more frequent than real disk failures. Doing an extended SMART test is a good indication of it being OK if it passes

The syslog appears to be full of errors in the mover tuning scripts. This suggests to me that you should be asking about those in the support thread for that plugin.

You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.

Licence issues cannot be sorted out on the forum - all we can do is suggest things that might cause problems. You need to contact support to get this resolved. This is overkill for Unraid - Unraid only uses something like 2-4GB of space on the flash drive.

The problem might be that the USB stick you purchased does not have a unique GUID which is a requirement for the licence, so if someone else has a USB drive with the same GUID they could have already started a trial earlier and Unraid does not realise you are somebody different. I would suggest that you contact support giving them the GUID of the drive that you are trying to get a licence for and they should be able to clarify/resolve) your issue.

Do you have your server directly exposed to the internet? You should not do this as Unraid is not sufficiently hardened against attack to avoid you being hacked if you do this. BTW: No log attached - you should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.

Those are all expected - they are used by the Unassigned Devices plugin.

Does not look like you used the -l option as that should have shown more detail about each entry.

Unraid does not 'tie' itself to anything. Most likely thing is that in updating the BIOS it reset the boot options and you no longer have it set to boot from the flash drive and need to reset it to this at the BIOS level.

Not a feature that the plugin supports I am afraid although it is something that could be considered as a future enhancement. i might also think of the ability to provide a list of docker containers that should not be actively running while a parity check is running. This might avoid the need for any scripts and easier to implement robustly. Probably a pause/resume option rather than a stop/restart approach would be best. Having said that if the ‘appdata’ and ‘system’ shares are completely on a pool then the interaction with the parity operation might be minimised or negligible.

The diagnostics is a single zip file - looks like you have posted the contents of the zip file. Maybe your system is being ‘helpful’ and auto-opening the zip file? Please post the single zip file instead as it is not very practical to work with all the individual files you listed.

Agreed, but the way things are going it may soon no longer be possible to get drives of 32GB or less.

That message means that there is something under /mnt that should not be there. Running the command: ls -l /mnt should give a clue as to what is (and therefore what might have done it).

This is not quite true. It can be any size, but the issue is that it needs to be formatted as FAT32, and Windows does not support doing this on drives larger than 32GB. Third party tools such as Rufus CAN do this.

The other feature you get is automated backup of all your settings stored on the flash drive to cloud storage. If you do not want to use this make sure you make a local backup of the flash drive (via the option available by clicking on the boot device on the Main tab) any time you make any non-trivial configuration change.

There is 48MB being used for nginx logs which is excessive. Maybe also worth running ls -l /var/log As it looks like there is a lot of space being used that is not in a sub-folder. Normally the space for logs is set to 128MB which is more than enough in normal use.

If you run the command du -h /var/log it might give a clue as to what is taking up the space.

I never said the cache setting would affect this - just that the setting you had did not match the description of what you thought it did. As I said I have never seen your issue - when I delete folders from my Windows machines they disappear as expected on my Unraid machine. I am not, however, using ZFS so it may be that is relevant in your case.

For this you need to contact support. You can never assume that any thread in the main forum is seen by Limetech as forum support is basically by other Unraid users.

Easiest way is via Dynamix File Manager

We normally recommend that scheduled checks are set non-correcting so that hardware playing up (that you have not yet noticed) does not end up corrupting parity.

Not seen the problem you describe, but this setting means you want files moved TO the cache if possible, not to the array.