itimpi

The diagnostics shows that there IS a mover process running. However it also shows that you are using the Mover Tuning plugin so you might want to try removing (or disabling) this in case it is causing problems in some way/

I think that in such a configuration with mixed sizes it acts as if all the disks are of the smaller size.

It might be worth looking in the config/shares folder or the config/pools on the flash drive to see if you have any .cfg files that relate to items you no longer use. If so you can delete them. if it is not that, exactly what name are you trying to use? The list of reserved names may have changed.

You have also appear to have over-ridden the defaults for: CT1000MX500SSD1_2114E594BDCD CT480BX500SSD1_1832E15212E7 CT2000MX500SSD1_2308E6B10F78 although this may well not be relevant. it looks like it might be treating the 0 for the warning level as assume the default of 70?

Are you trying to pass any hardware through to the VM? The only reason I can think of why you would get your symptoms is if starting the VM is taking the disks away from Unraid.

If the drive had failed then yes as Unraid would have been unable to write back to the flash drive that it had successfully stopped the array.

you should update to 6.12.3 as it contains a docker related fix that might fix this. Post again if it does not.

Replacing disks is covered 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.

You are going to want to replace disk1 anyway as any drive that fails the Extended SMART test should be replaced.

Have you checked if there are any files in an ‘extras’ folder on the flash drive? As well as not loading plugins I think Safe Mode also does not install any packages from there.

Have you ensured that the flash drive is set up with a single partition and formatted as FAT32 before you try and copy any files to it?

Are you passing any hardware through to the VM? you should post your diagnostics from before you start the BM so we can get a better idea of your setup.

You could try copying (not moving) the data to the good drive and then use the New Config tool to remove the bad drive from the array. The space currently used on disk2 looks about right for the overhead of creating the empty file system ready to receive files.

You have over-ridden the global settings for some of your SSDs. Have you tried setting those to also not generate notifications? it is quite possible you have uncovered a bug as I suspect most people do not disable these notifications but merely set them to values that should not trigger notifications.

You can use the New Config tool which is covered 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 to rearrange your drives.

Yes. Any .fsck files relate to corrupted configuration files

It definitely could as the .fsck files get created during the boot process if corruption is detected on the flash drive, and the error messages look like problems reading from the flash dtive. I would try rewriting the flash drive with a fresh install keeping just the contents of the ‘config’ folder as sometimes rewriting the flash drive helps. If that does not help then you probably need to replace the flash drive.

Have you tried with a fresh install without copying all the of the config folder?

It is quite normal when a 6.xx.0 Unraid release comes out to find that issues surface that were not discovered/mentioned in the rc phase (presumably because a much wider variety of users now install it) and a couple of rapid point releases come out that try and address these issues. At this point these point releases are inherently bug fix releases without functionality change (unless addressing a bug). Only those who specifically want the new functionality and can afford some initial issues as it beds in should rush to upgrade with the 6.x .0 releases. There then tends to be a long period where we only get beta/rc releases aimed at the next major Unraid release as new functionality is added. That is also when you get the latest versions of core Linux components (kernel, samba, docker, kvm etc) incorpirated.

I would suggest updating to the stable 6.12.3 (probably the same as the rc3 release by why take a chance) and posting new diagnostics since you must rebooted to active 6.12.3. Makes sure that the problem is happening at the time the diagnostics are taken.

That makes sense It can always be a bit confusing when it works at 100 Mbps and not 1000 Mbps. I think many people do not realise that you can fall back to the slower speed if any of wires within the cable are not making a proper end-to-end connection as the slower speed requires less working connections.

There have been plenty of reports that writing to ZFS format drives in the main array can be very slow. I have a suspicion that this may be inherent to ZFS and the way it chooses which sector to write to next causing excessive head movement on the parity drive but I am not sure there has been any structured testing to prove this. It would be nice to know for certain as that would mean we would then advise against using ZFS in the main Unraid array, and instead use either ZFS as the most efficient or BTRFS for those who want bit rot detection. ZFS would still have a place in pools where you want maximum performance.

Each transcoded file effectively IS a new file so the behaviour you describe is exactly what Unraid should do. Probably the best thing to do is to make sure the Minimum Free Space for the cache is set to a value that will stop it over-filling, and then when the free space falls below that value Unraid will start by-passing the cache for new files/transcodes.

no. it is never possible to run a proper memory test while an OS is running. These tests need direct access to the hardware.

Any plugin that put items on the dashboard had to be updated to support the 6.12 series of Unraid. In many cases this was done by forking the earlier one so you have to delete the original and find its replacement via the Apps tab.