itimpi

That is the device name and is not used by Unraid to identify drives (instead Unraid uses the drive serial number). Something else must be going on.

You could delete the config/vfio.cfg file on the flash drive and reboot.

When you restart the array in normal mode that disk should now mount.

Ext4 is not a supported file system type for the main array. It can, however, be mounted using the Unassigned Devices plugin to facilitate copying files off it.

This will be possible when (as expected) the need to have at least 1 drive in the main array is removed. You could also do it now by upgrading the licence and using a dummy flash drive as the required array drive.

You need to distinguish between 'pool' which is a a group of one or more disks that are not part of the main array and 'cache' which is functionality associated with a share (although there is confusion about the fact that for historical reasons people often have a pool called 'cache'), and you can have multiple pools. If you only set up 'primary' storage for a share then there is no caching involved and you can specify whether that primary storage is a pool or the main array. In the scenario you describe above then the primary storage would be the pool you specify and all files for such shares would be on that pool. Many new uses are now going that route. In the future we expect the need to have a dummy usb drive in the Unraid type array will be removed. A multi-drive pool has to be either btrfs or zfs. You can only use xfs on a single drive pool.

You have the file ‘mounts’ which should not be there. You must have something creating it. It is also not normal for the RecycleBin folder to be there - but that may be an artifact of whatever is causing the ‘mounts’ file to appear. There should be nothing manually mounted directly under /mnt. if you are manually mounting anything then it should be under /mnt/addons. If you use Unassigned Devices plugin to mount anything it will appear under /mnt/disks or /mnt/remotes as appropriate.

Yes. There is a known issue with performance when ZFS is used on array drives. This does not apply when ZFS is used in a pool.

They are text files so can be opened and examined easily enough.

They will if you use Apps->Previous Apps to select and install them.

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.