itimpi

The parity drive shows quite a lot of reallocated sectors so is a bit suspect.  Which was the other drive that had a thumbs down?  You can acknowledge the SMART error by clicking on the icon and then Unraid will only tell you again about if it changes.

The New Config option is on the Tools menu.   No idea where you have seen a reference to a Utils menu or initconfig as Unraid has never had such a thing.

The reason that SSDs are not recommended in the main array are:
Trim is not supported Write performance is not going to be very good if you also have HD in the array. what you CAN do is use a thumb drive to satisfy the requirement of at least 1 drive on the array, and then use the other drives in pools.    These can be BTRFS with current Unraid and the 6.12 release adds ZFS as an option for pools.   These can be multi-drive pools with various RAID options available if you want them to be redundant.

Have you actually tried a different cable?    It only takes one of the wires in a cable to be faulty for the link speed to downgrade to 100Mb

Not sure this is something the Unraid developers can fix as they just include in Unraid the Linux KVM subsystem that they do not develop   I think in practice this is really going to be up to the KVM developers to fix.   If they can get it to work reliably on the Linux kernels that Unraid uses it should also start working reliably on Unraid.

I would suggest asking the author of the app (if he is willing to tell you).  I do not think there is anything officially documented that gives this information.

Exactly how did you do this?   The steps should have been:
Stop the array Set the parity1 slot to Unassigned Start the array to commit that assignment change After that you can if you want then add the old parity drive as a new data drive following the standard procedure for adding a drive as documented in the online documentation.
 
You cannot do both changes these in one step.

When you ran the previous correcting check then all sectors 'fixed' are added to the error count even though they should perhaps not be considered as errors so in that sense the count at the end is normally the number of sectors 'fixed'.
 
You should now run a non-correcting check to confirm that all errors have been corrected.   You could run another correcting check, but if so this to time expect the count to be 0 unless new sectors needing correcting were found.

Have you checked that Settings->Unassigned Devices->SMB Security is not set to No as this would stop it being visible on the network?  If so you probably want the 'Public' settings.

You do NOT want an Unraid server to be in the DMZ as it is not hardened against attacks from the web.  Doing so almost inevitably leads to your server being hacked.
 
For remote access to the Unraid GUI from the web you should use either the MyServers plugin or use a VPN (Unraid has the WireGuard VPN Server built in).
 
If you want to run a web site then open just the ports for that through your router and make sure the web site is secured.

A rebuild will put on the replacements disk exactly what is showing on the emulated drive before starting the rebuild.  If the emulated drive is showing as unmountable then the rebuilt one will be as well.   You do not create a new file system on the disk being rebuilt because the rebuild process is going to restore exactly what was on the emulated drive.
 
You can attempt a repair on the emulated drive before starting a rebuild.  At that point you still have the original disabled disk unchanged in case it was just a glitch that caused it to be disabled which gives you extra recovery options.

The New Config is about resetting array drive assignments 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..

Have you made sure you have no plugins that are incompatible with 6.12 and break the dashboard as mentioned in the release notes?
 
A quick way to check is to boot in Safe Mode and see if you still have the problem.

Most likely culprit is a docker container with that as one of the configured paths

Your screen shot shows you have the SMB Security Export option set to No which means it is not available via the network.

That file is definitely corrupt.    You can get the default one from a zip download of the relevant Unraid release.      However the fact it is corrupt in the first place makes me wonder about other files on the flash drive and whether the flash drive is having problems.    Do you have a recent backup of your flash drive?

Disk1 has a LOT of reallocated sectors and the number has tripled since your screenshot.   I would think it is time to replace that drive.

I can see the mount failing in the syslog, but not why.   It says that partition 1 does not have a valid file system on it so skips over that and then tries to mount partition 2 as NTFS but that fails.
 
I wonder if it does not like some of the characters in the mount point name?   It might be worth simplifying this name to be sure and sticking to alphanumerics to see if that helps.  Otherwise it could simply be a problem with the NTFS file system that you are trying to mount so have you checked it in a PC?
 
Nothing else to suggest I am afraid.

No unfortunately you would not be able to do that.
 
it will be remembered that the old drive had a trial licence on it and in your scenario that would have expired so would no longer be able to run Unraid so it would end up blacklisted just as it does after a licence transfer.
 
another possibility that might be worth considering is a USB adapter that fits internally on a motherboard header so your existing USB drive can be internal to the case?

It would have done that if you had the correct Use Cache=Yes setting.   Unfortunately you configured it do exactly the opposite.    The help built into the GUI for the Use Cache setting might have helped explain how the setting option interacts with mover.

I suspect that your problem is your very restrictive Split Level setting.   In the event of contention between settings the Split Level one always wins which means it can over-ride Allocation method (and Minimum Free Space) forcing files to specific drives.    This is a point made in the Split Level part of 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.

As a general rule of thumb it is reasonable to assume that any drive that cannot complete the extended SMART test is a candidate for replacement.    Looking at that drive it has quite a few reallocated sectors and several pending sectors which are also warning signs.
 
FYI:  The diagnostics includes SMART reports for all drives so no need to include it separately, although it can be a good idea to mention which drive it is to assist anyone trying to help you.

Yes, you cannot have a share named the same as a physical device or pool.

One way to achieve that would be to set the Split Level on the Media share to 1.    You then create the Media folder (if it does not already exist) on each drive and folders for the next level down on the disk you want them to be on.   The Split Level setting will then constrain them to the disk on which you have created the second level folders.  
 
You could also use level 0 for Split Level (manual management) and it would achieve a similar result.   This may be more intuitive?

Chances you will the torrent failing with ‘out of space’ errors.    Once a drive has been selected for a file Unraid will never change its mind and will generate an error if the file does not fit.  
 
In your stated case it might make a difference if you have the torrent client set to allocate all the space for files from the outset or not and what you have set as the Minimum Free Space setting for the cache as to whether any part of the torrent will overflow to the main array.