Not sure why that should have broken as nothing has changed there for some time, but it is very difficult to test that option on my system as my drives never overheat so it is always possible that something slips through.
If you can enable the Testing mode of logging in the plugin settings then get diagnostics at a point where you think the check should have been paused but it has not I should be able to see why it has not paused.
Note that pre-clearing drives before adding them is optional - it is only required if you want to stress test the drive before adding it. Regarding pre-clear then if you search in the apps tab for it then you want the version that is an add-on to the Unassigned Devices plugin.
Windows will not format drives larger than 32GB to FAT32 but you can use a drive larger than 32GB if you use a 3rd party utility such as Rufus to format it to FAT32 (with MBR partitioning).
Note that you can already go way over the 30 drive limit if you use pools. That limit only applies to the main array in the current release and even that is likely to. change in a future Unraid release.
Yes. I would start by downloading the OS Zip files to get the flash drive bootable and then afterwards extract the backup files on top of the flash drive contents to get your settings etc in place.
If you copy your existing .key file into the config folder on the new flash drive then you will get taken through the licence transfer process as described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release. If you still encounter problems then contact support.
You have several shares that are set to not use the cache but actually have files on the cache (appdata, data, system) - is this intentional?
typically one wants the appdata and system shares to be on the cache for best performance.
Yes - mover will not overwrite duplicates as in normal operation this should not happen.
you need to decide which copy is the more recent (probably the cached ones) and then manually delete any duplicates off the relevant drive. Make sure you go directly to a drive and not via a User Share as if you go via the User Share you are quite likely to delete the wrong copy. After doing this mover should then start working as expected.
Emulation works at the physical disk sector level and has no idea of file systems. It thus protects against a disk physically failing. In this case the problem is at the file system level and needs fixing using software that is file system aware.
Yes it is - but doing it via the GUI ensures the correct device name is used. The name can vary according to the Unraid release being used and whether you are using encryption or not. The GUI automatically gets this right.
If you click on the drive on the Main tab then there is an option for checking or repairing as described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.
That is a frequent error message. At this point Unraid has already failed to mount the drive so using the -L option is the standard next step. At the very worst it will only affect the most recent file(s).
@SpencerJ It might be worth adding 'unmountable' to the list of keywords that get a link as it seems to be a very frequent issue at the moment in the forum
If you are not sure what you are doing then you should DHCP for setting the addresses of the servers rather than using static addresses. You can then use your router to always give a consistent address to each interface.
If you must use static addresses then eth1 must be set to an address that is not already in use on your network. The address your screenshots show is the address of your router.
In theory anything really private should be removed. The contents of the zip file are all text files so you can decide for yourself if you are happy eith the anonymisation process.
It is difficult to answer your question without more information about your system. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread so we can see more about your hardware and also how you have things configured.
Not sure what confuses you? One plugin is about backing up the working data for your docker containers, and the other is about updating the binaries. As such they are independent of each other.