itimpi

Have you made sure the 'EFI folder on the flash drive does not have a trailing '-' character? This is needed if booting in UEFI mode which may be all a new board supports.

I would suggest you just plug it in and use the Unassigned Devices plugin to manage mounting it as required. You could also have script to handle the backups automatically triggered when you plug it in.

You are meant to click on disk2 on the Main tab and select the Check item from that dialog. The idea is to see if the file system for the 'emulated' disk2 can be repaired to make its content available again for later rebuilding onto a replacement drive.

You should take the diagnostics at the point you are seeing the problem.

From the examples you provided then a value of 2 would keep shows on the same drive. Note that you may need to manually move some of them to another drive to free up space at the moment as Unraid will never move files/folders between drives - any changed settings only apply to new files/folders.

This is almost certainly a hardware problem. We can probably confirm this if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread taken after this happens again. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs.

If there is anything being done for this it would be at the underlying Linux level which is where Unraid inherits its XFS support from, not specifically at the Unraid level.

Unexpected reboots are almost invariably hardware related. Heat could be a cause, but other issues such as insufficient power are common. Unfortunately if the reboot IS hardware related then there is typically nothing logged to give the reason. The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

Yes. Unraid has to update each drive to say it has been successfully unmounted.

That almost certainly means that the drive has the 3.3v issue mentioned earlier. Does the new PSU have any molex connectors? If so then the easiest solution is using a molex->sata adapter to power the drives as the molex connector does not have a 3.3v pin.

Have you checked for the 3.3v issue? If not that then one would think the drives have failed. If it IS the 3.3v issue, then an alternative to taping over the problem pin is to use a molex->sata adapter to power it as that does not have a 3.3v pin.

I wonder if the disks that are not being seen suffer from the 3.3v issue (google it for more info)? How are they powered?

The iperf results show that you have a network issue limiting speed in one direction (although not sure why) so this is what needs fixing .

/mnt/user is used for all User share paths and includes a consolidated view of files in a User Share whether they are on the array or any pool. /mnt/cache is a physical device so only shows files that are on that specific device.

This suggests the problem might well be network related and nothing to do with SMB.

If you can see both licences online and can download the licence file for the one you are NOT using then simply create a new Unraid flash drive and put the licence file into the 'config' folder on the flash drive. When you boot off that drive Unraid will detect the licence does not match the GUID and take you into the licence transfer process. Make sure that you get the correct licence file as the transfer blacklists the GUID the licence was originally associated with and you do not want to do this for the licence you are actively using. As was mentioned you can also contact support to help with the licence transfer.

Not sure what you think using /23 is going to give you? Cannot see the Use Case where it would be useful.

To get mover to do what you want you need: Primary storage=cache Secondary storage=array Mover direction = cache->array If a share only has primary storage and no secondary storage then mover ignores it.

Not sure if ZFS allows mismatched drives to be used if you want the full capacity to be used (i.e. E. TB) but I think not although @JorgeB would be the best for confirming this. BTRFS does with the ‘Single’ profile although you have no redundancy with the Single profile - but that may be OK for your needs?

If you try to reset it to zero then Unraid will automatically set it to a value based on % of disk size. You can set it to a very small non-zero value to avoid this. However it seems unlikely that value is relevant unless you were filling up the drive enough to get to that limit.

Since you have no parity drive the settings->Scheduler->Parity Check runs as a read check. Ideally the dialog would change to reflect that only a read check will be run but it does not

Try using the Dynamix File Manager built into Unraid 7 instead.

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

As has been mentioned a few times the best thing to do (if at all possible with your hardware) is to pass through your GPU to the VM and then run Unraid via a browser session within the VM.