itimpi

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.

It is mentioned at the top level of the documentation link

I would suggest you contact support giving them the details. They tend to be quite responsive.

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.

That suggests a problem with the flash drive. The original diagnostics posted did not show a problem, but new ones might.

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).

Have you tried booting in Safe Mode to eliminate any plugin being the cause of this?

@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.

Have you tried running the repair from the GUI so you get the correct device name?

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 means you have something configured (probably a docker container) that explicitly references disk1. This needs correcting.

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.

If they are both HBA then it is just a case of re plugging the drives.

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.

It is a Licencing issue I believe.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread taken after the problem has occurred.

The IP4 address you have assigned to eth0 is wrong. You have assigned the address of your router which will mess things up.

In this special case you should not need to do anything as the parity disk is mirroring the data drive, so if the data drive is missing it will simply 'emulate' the missing disk1. When you get the replacement for disk1 you can then follow the standard process for rebuilding a failed drive. There is a significant chance that disk1 has not actually failed but was simply disabled due to a write failing caused by an external factor such as the SATA or Power cabling. However the drive is not showing up in the diagnostics - is it physically still in the machine?