John_M

You are correct to say that the Mover doesn't move duplicate files. However the two items you highlighted are directories. You need to compare their contents in order to determine which is the newer version of each file, assuming that's what you want to do.

The file doesn't exist. You are using a manually defined location, so did you ever create the file in the first place?

Something isn't working. It seems like the smart-one.cfg is being ignored. How about editing file manually? You might need to stop/start the array to make it register.

You're trying to pass your only GPU through to a VM. Are you supplying a ROM file? This thread might help you unbind the Unraid console: Unrelated, but it might cause you problems later with memory corruption, you're overclocking your CPU's memory controller: Speed: 3600 MT/s The spec for four single rank DIMMs is 2933 MT/s. See here:

Power down, reseat (or preferably replace) the SATA cable and check the power cable to the drive while you're there, power up and grab new diagnostics, which will give an indication of the health of the drive, which is currently unknown, as @itimpi pointed out. The disk will remain disabled and emulated and requires manual intervention but not until the state of the drive is known.

Your containers are working in host mode. TCP port mappings are ignored in host mode. You need to ensure they get different IP addresses, which currently isn't the case.

It's a failure of the SATA link. Jun 19 22:43:30 Klingon kernel: ata8: limiting SATA link speed to 3.0 Gbps Jun 19 22:43:30 Klingon kernel: ata8: hard resetting link Jun 19 22:43:35 Klingon kernel: ata8: softreset failed (1st FIS failed) Jun 19 22:43:35 Klingon kernel: ata8: reset failed, giving up It's most likely a cable/connector problem because plugs and sockets are the least reliable link in the controller - cable - drive electronics chain. The cable is fortunately also the cheapest part to replace.

What happens if you configure the system to use Celsius temperatures, instead of Fahrenheit? Settings -> Display Settings -> Temperature Unit, and note the information in the GUI help: I only ever use the Celsius scale and haven't had any problems, except for the fact that at one point the mechanism for updating the smart-one.cfg file was broken. The drives report their temperatures in Celsius so displaying them in Fahrenheit and comparing them with threshold values involves a trivial calculation but there might be some bug there.

If your array has a mix of very small disks and very large ones you should consider how disks are allocated to shares. The default is for all disks to be available to all shares but you might want to change this to reduce the risk of running out of space when writing one of the very large files. The order of the disks in the array and the choice of allocation method might be significant, too. Another thing you might want to consider is moving some of the smaller disks out of the main array and making them into a pool. Using btrfs RAID you can combine their capacities and (unlike the main array) store files that are bigger than the capacity of a single disk. With more information about your use case it might be possible to make more suggestions.

Standards are so good that everyone wants their own, so that's what Microsoft did: See here: https://tldp.org/HOWTO/CDROM-HOWTO/x1186.html#AEN1328 Perhaps Joliet support is not included in the Unraid kernel but it is in the Ubuntu kernel. That would make sense because Unraid is not a general purpose Linux and has a lot of unnecessary options removed. If that's the case then your options would be: re-create your .iso with Rock Ridge enabled; use a different image file format that supports long filenames and mixed case natively; use an Ubuntu VM to mount the .iso file; make a feature request for Joliet support to be included in a future release; investigate the possibility of compiling your own kernel with Joliet support included.

Every additional core you add (even if they are not pinned, and therefore potentially shared with other processes) will bring a performance increase to your VM if the workload can make use of the extra cores. If the workload can't use the extra cores then you'll probably see a slight increase in latency as the cores on one chiplet can't access the L3 cache on the other chiplet. It's a question of balance. Yes, by dedicating an entire chiplet to your VM you have something similar to a 5800X running bare metal. It isn't quite the same because the base and boost core frequencies are different between the 5800X and the 5950X due to the power budget per core being less for the latter, which is only partly offset by the higher binned silicon, and because the resources of the I/O chiplet are shared between the VM and the host.

You can test your network speeds with iperf3. The Windows version is free to download and the Linux version for Unraid can be installed using the Nerd Tools plugin.

Your load average is extremely high and has been for some time. What's running under Java? top - 09:47:24 up 25 days, 29 min, 4 users, load average: 185.08, 179.10, 178. Tasks: 650 total, 3 running, 645 sleeping, 0 stopped, 2 zombie %Cpu(s): 73.8 us, 14.1 sy, 0.0 ni, 0.5 id, 11.7 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15972.7 total, 155.5 free, 13958.3 used, 1858.9 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 306.6 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 11914 nobody 20 0 5822000 2.0g 0 S 700.0 12.6 2461:26 java 28259 root 20 0 748208 23044 0 R 206.2 0.1 102:19.37 caddy 25503 root 20 0 2512 1580 1400 R 100.0 0.0 13958:53 wsdd 5763 root 20 0 2756624 96376 984 S 12.5 0.6 2644:08 shfs

First create your pool. With the VM stopped, copy the image file from its current location to a suitable location on the pool, something like this: mkdir -p /mnt/my-pool/domains/Windows cp --sparse=always /mnt/disks/my-unassigned-disk/domains/Windows/vdisk1.img /mnt/my-pool/domains/Windows then edit the VM configuration to point to the new location. When you've tested it are are happy, delete the image file on the unassigned disk (or keep it as a backup). The action of making a domains directory in the root of your pool creates a user share called domains. You'll want to check that share's properties and make sure it's set to cache:prefer or cache:only so that the mover doesn't move the contents to the array.

I thought it would, but it's nice to have it confirmed.

Post your diagnostics.

In addition to the main array, you can have up to 35 named pools, each with up to 30 disks.

Is the affected card the one that the server uses by default for its own output - the BIOS screen and Unraid boot menu, for example? I don't see the 10700K's iGPU listed in your diagnostics - is it disabled? You could set it as the primary GPU in the BIOS, which should avoid the problem of the GT 710 not detaching.

From the mount(8) man page: What is the origin of your .iso file? Is it Rock Ridge compatible? Using a standard Kubuntu installation image, it works fine for me: root@Pusok:~# mkdir t root@Pusok:~# mount -t iso9660 /mnt/user/isos/kubuntu-20.10-desktop-amd64.iso t mount: /root/t: WARNING: source write-protected, mounted read-only. root@Pusok:~# ls t EFI/ boot/ casper/ install/ pics/ preseed/ README.diskdefines boot.catalog dists/ md5sum.txt pool/ ubuntu@ root@Pusok:~# ls t/casper filesystem.manifest filesystem.size initrd filesystem.manifest-minimal-remove filesystem.squashfs vmlinuz filesystem.manifest-remove filesystem.squashfs.gpg root@Pusok:~# umount t root@Pusok:~# rmdir t I suggest you try the same (or similar) standard file.

Do we know if this is a btrfs bug or a GUI bug?

The GUI includes time spent waiting for I/O so when there's heavy disk usage this is to be expected. You could try stopping some of your Docker containers for a while and seeing if the activity stops. You should be able to isolate the culprit that way. Or you could install the Open Files plugin to see what application is accessing what files. Alternatively, your diagnostics might show what's happening.

There are detailed instructions for replacing your flash device here: https://wiki.unraid.net/Manual/Changing_The_Flash_Device

Yes, sda is indeed your USB flash device. [0:0:0:0] disk SanDisk Ultra 1.00 /dev/sda /dev/sg0 Do you have a backup of its config directory?

I'm not sure why you chose the isolate those four (virtual) cores. The 3700X has eight actual cores, each of which can run two threads, giving 16 virtual cores. For each core you want to dedicate to a VM you need to specify the two virtual cores for maximum efficiency. The GUI helps you with this. For the 3700X you'll see that physical core 0 is represented by virtual cores 0 (labelled "CPU" in the GUI) and 8 (labelled "HT" in the GUI), physical core 1 is represented by virtual cores 1 and 9, and so on, finishing with physical core 7 being represended by virtual cores 7 and 15. So isolating virtual cores 2, 3, 6 and 7 isn't optimal. If you want to isolate two physical cores 2 and 3, you should isolate virtual cores 2, 3, 10 and 11. If you want to isolate four physical cores 2, 3, 6 and 7, you should isolate virtual cores 2, 3, 6, 7, 10, 11, 14 and 15. It is constructed differently, with two core chiplets instead of one but the same principle applies. The 5950X has 16 actual cores, each of which can run two threads, giving 32 virtual cores. Again the GUI helps you when it comes to allocating the pairs of virtual cores. For the 5950X you'll see that physical core 0 is represented by virtual cores 0 (labelled "CPU" in the GUI) and 16 (labelled "HT" in the GUI), physical core 1 is represented by virtual cores 1 and 17, and so on, finishing with physical core 15 being represended by virtual cores 15 and 31. That is not optimal. If you want to isolate four actual cores you need to specify eight virtual cores, such as 2, 3, 4, 5, 18, 19, 20 and 21. If you want to isolate eight actual cores you need to spacify 16 virtual cores and in the case of the 5950X you will get a little bit of extra performance by specifying all the cores on the same chiplet, like this: 8, 9, 10, 11, 12, 13, 14, 15, 24, 25, 26, 27, 28, 29, 30 and 31. The following tables might help 3700X: Physical Virtual Cores Core "CPU" "HT" 0 0 8 1 1 9 2 2 10 3 3 11 4 4 12 5 5 13 6 6 14 7 7 15 5850X: Physical Virtual Cores Core "CPU" "HT" 0 0 16 1 1 17 2 2 18 3 3 19 4 4 20 5 5 21 6 6 22 7 7 23 8 8 24 9 9 25 10 10 26 11 11 27 12 12 28 13 13 29 14 14 30 15 15 31

If your appdata is on the cache and the cache pool is btrfs formatted then you don't need to worry about running out of inodes anyway because the number isn't fixed, which is why the percentage used is meaningless and shows as zeros in the output of df -i.