itimpi

Assuming the fix works you can always add it to the config/go file on the flash drive to make it persistent.

Not unless you added it! The standard diagnostics only include the RAM copy of the syslog, not the one mirrored to flash.

that would not be the culprit as it comes from the bz* type files that are on the flash. The only thing I could think of that could be 6.12.x specific would be code installed by a plugin but you say you get the same problem when booting in Safe Mode which avoids loading plugins.

You may find it easier to do a Manual downgrade.

You need to contact support if you have a license problem. if the email had an attached licence file then this should be placed in the ‘config’ folder on the flash drive.

When you have set up the replacement cache dtive then changing the mover direction will cause the files to be moved to the new cache drive.

You need to set the cache as the primary storage; the array as the secondary storage; and the mover direction as cache->array to get the files moved to the array.

What makes you think it is not running? It would exit almost immediately because it appears you do not have anything due to be moved.

This is not true - I use encrypted disks without using https (SSL)

The release notes for the 6.12.0 release described the new naming for the share settings and how they map to the old naming. With the settings you have you should just disable the docker and vm services under Settings and then start Mover manually from the Main tab. You need to disable the services as they keep files in the ‘system’ share open which will stop them being moved. When the files have been moved you can reenable the services. At that point if all the files are on the cache you can set the secondary storage to No. You might also want Exclusive mode access (also defined in the release notes) for maximum performance. It is not normally necessary to have the isos share on the cache but it does no damage.

possible I guess. Might be a bug then in the Dynamix File Manager not correctly handling Exclusive shares.

You are being protected against the fact that moving files between a physical device and a User Share in the same command can lead to data loss so this option is not allowed by Dynamix File Manager. Instead try moving it from the ‘downloads’ User Share to the /Media User Share. If you must use the physical cache drive as the source then you need to select a physical target drive as well.

should not need the docker.img file to be anywhere near that size unless you have a container writing files internally to the image that should better be mapped to an external location.

Even they should come back with default settings as long as User Shares are enabled under Settings->Global Share settings.. You then need to check each one in turn to make sure you are happy with the settings.

Remove the -n and if it asks for it add -L. Hopefully after that the drive will mount when the array is started in normal mode with content intact.

You should be able to upgrade your current flash drive if you used the Manual Update process as it does not need space for the previous release.

That would have happened if you tried to pass the NIC hardware through to a VM.

Not completely, but you can start the array in Mainenace mode rather than normal mode.

It looks like you have it bound to vfio which hides it from Unraid. Try deleting or renaming the cpnfig/vfio.cfg file on the flash drive if you want Unraid to see it and then reboot the system.

Yes - it has to be 2 steps. Which one you do first is up to you.

You cannot do a rebuild and an add at the same time - it yas to be done in 2 steps. howrver the add does not involve a rebuild. If the disk has been orecleared then it is added in immediately as a disk that is all zeroes does not affect parity. It would then show as unmountable after the add and you need to format it at thst point to the desired file stsem (which only takes a few minutes) to get it ready to use. If the new disk is not pre-cleated then when it is added Unraid will first clear it to be all zeroes before it is then made ready to be formatted.

Petsonally just having capitalization differences is likely to be too confusing i would think.

One thing that can be done now is start thinking of ‘cache’ as a capability of a pool rather than a pool type. It is not helped by the fact that at the mome t the default name for a pool still seems to be ‘cache’. Perhaps it should be changed to ‘pool’ or somethibg like that. I do agree that a better name for the Unraid array that is more type oriented (such as the UnArray’ suggestion, or perhaps simply ‘hybrid’) would be a good idea. It will become much more important when we can have multiple arrays of the type of the current main array, and everythibg starts getting treated as a pool.

You should not assume anyone from Unraid sees any particular forum thread as the forums are primarily for community support. Youbneed to go via Unraid contact support if you want to guarantee they see your issue.

That implies you got an unclean shutdown before the reboot. If you continue to get this then you may find this section of the online documentation to be of use.