itimpi

Have you tried hovering your mouse over the icon for the drive?

If you have the Mover Tuning plugin installed then you can try removing that as it often seems to stop mover from working correctly for some reason.

They can actually safely be deleted if those shares are no longer being used.

It is limited by the 'virtual' NIC speed which I believe is typically around 10Gb so in practise that is normally not the limiting factor.

If you click on the Settings icon for a particular drive under UD then it is a toggle there. It needs to be set as otherwise UD will take control of the drive stopping the Libvirt Hotplug USB handling it.

I have never bothered with 9pMode as I always get better performance going via a network share.

To achieve what you want you need: Split Level = automatically Split any Level Allocation Method = Fill up Minimum Free Space = 10GB + size of largest file to be transferred.

Have you tried running an iperf3 test between the two machines to check what network speed you are getting in each direction? On the Unraid side are you writing to the parity protected array or to a pool device? If the array then that is about the maximum speed you will get because of the way Unraid handles writes to the array as described here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.

According to your screenshot it IS being emulated as the emulated disk has mounted and appears to have plenty of data on it. What makes you think it is not emulated?

Not sure if it would work, but at the very least it would think it was a new disk as the size is one of the things recorded about a disk when it is added to the array.

I would suggest that you contact support giving the GUID for the new flash drive and they should be able to help you.

Appears some DOS end-of-line characters have crept into the .page files and this is upsetting the underlying language translation sub-system. Just made sure that all files have Linux style end-of-line characters and am now checking to see if this rectifies the issues. EDIT: Just pushed an update that corrects the EOL issue as it fixes the problem on my test system. Please confirm if it fixes it for you as well. The effect of the problem was that the plugin was functioning in terms of its background tasks, but the Settings page was not displaying.

Just reproduced that on one of my test environments - will look into why it is happening

I have just pushed an update with the most notable changes being: - Now improves handling of custom scheduling being used for increment pause/resume times - Set most notifications to be at normal (green) priority. The ones left at 'warning (orange) and error (red) level are ones where the user really wants to take notice of them. I would welcome any feedback if this is an improvement or suggestions for changing the priority of specific notifications. Hopefully I have not broken anything, but please report any anomalies that are spotted.

If you want to pass the USB drive through to the VM have you made sure the Passed Through flag is set for that drive in its UD Settings?

The problem will be that Unraid sets the start sector for the partition on the drive differently for SSD and HDD so the available space is not actually the same.

I thought that XFS would tick all these boxes, and it has been around forever as well.

I suggest that you contact support then as they should be able to sort things out for you. They tend to be reasonably responsive even at weekends.

@Kilrah's suggestion might just work. The steps involved would be. Use Tools-> New Config. I would suggest selecting the option to retain all current assignments Return to the Main tab and correct the data drive and parity drive assignments to what they should be Tick the Parity is valid checkbox to avoid Unraid trying to recalculate parity. You still get a warning as that does not take into account the fact that the check box was ticked. Start the array to commit these assignments. I would expect the problem drive to show as unmountable but ignore that for now. Stop the array. Unassign the disk you incorrectly assigned to parity earlier Start the array and this disk should now be emulated. Whatever now shows up on the emulated disk would be what you would end up with if you attempted to rebuild into a physical drive. It is possible the disk will still show as 'unmountable' but it still might be possible to repair its file system. I would suggest that at this point you stop and take diagnostics and post them here so we can see the current state of things. Keep the disk you have just removed intact at this point just in case the UFS Explorer type route is still needed.

have you put the new licence file into the config folder on the flash drive and also rebooted to activate it?

What do you think it will add to have ext4 support in the array/pools? You can already read/write ext4 via Unassigned Devices.

Probably did nothing wrong as there appear to have been problems recently at the Unraid end in the automatic replacement. You should contact support giving them the GUID of the replacement flash drive you want to use.

Your only chance that I can think of will be to see if file recovery software such as UFS Explorer on Windows can recover anything.

This is described in the User Shares section of the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release.

What file system type did you use for the SSD? I would suggest that you start by using Tools->New Config and set up the array as you want it to end up. You could then simply mount the SSD using the Unassigned Devices plugin and copy its contents back to the array. For this the Dynamix File Manager plugin would probably be the easiest to use. If you want to maximise speed do this before assigning the parity drive to the array. Alternatively you could configure the SSD as a pool, and then for the shares you want to end up on the array set Primary storage as the SSD, secondary storage as the array, and mover direction to be ssd->array. This would have the advantage that shares you want to permanently live on the SSD for performance reasons (e.g. appdata, system) there would be nothing to do. This gets you back up and running with your data intact almost immediately.