itimpi

This is not relevant to the main array as in that each drive is an independent file system. I also suspect that it is a legacy requirement and nothing like that is needed on modern systems. ZFS in the main array is know to currently have performance issues. This does not apply to ZFS zpools which are currently the highest performance option with Unraid.

This is not necessary if the share is an Exclusive share. Parity is realtime so any write to the array also causes a write to the parity drive. You may find this section of the online documentation accessible via the Manual link at the bottom of the Unraid GUI useful in understanding how writes to the array are handled. 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.

Those files get created when file system corruption is detected on the flash drive. No idea why it has that modified date though.

That 'df' command shows something strange in that there appear to be lots of mount points of the form /mnt/diskxx/Data. This is is something that I would only expect to see for an Exclusive share - and that can only exist on one drive or pool. Have you done anything to create these? The error message can be explained if Unraid is picking the first one on the list (/mnt/disk11/Data) as that has less than the Minimum Free Space free set for the Data share. The other anomaly is that none of the physical drives /mnt/diskxx seem to have any space used so no idea where the data is actually being stored - it may be in RAM and thus will not survive a reboot.

You should: Disable the Docker service under settings (it needs to be disabled to stop it keeping files open) Run mover to transfer the contents of the 'system' share to the cache (optional) When that completes you might want to confirm that there is now no sign of the 'system' share on disk1 Set the secondary storage option for the 'system' to None Enable the option to use Exclusive shares under Settings->Global Share settings to get the performance advantage of bypassing the Unraid Fuse layer Reenable the Docker service Once this is done then docker will not be keeping disk1 and parity spun up all the time.

Your ‘system’ share has files on disk1. If this includes the docker.img file then even having the docker service started will keep disk1 and parity spun up as writes to any array drive automatically update parity at the same time.

With the current 6.12.x Unraid releases you can also get the performance benefit of bypassing Fuse if a share is only on a single pool by enabling the Exclusive share option.

It is most likely to be something you have configured in a docker container.

The reason that 32GB is mentioned is that the flash drive needs to be formatted as FAT32 and Windows does not support as standard doing this on drives over 32GB. Also Unraid only needs something like 1-2GB on the flash drive so large drives have lots of space that will never be used.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. 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.

It is the other way around. After adding users on the page you show, you add permissions for users on the page for any particular share.

I think it can sometimes just mean there is a borderline block rather than the flash drive going bad. That is why it is always worth rewriting all the bz* type files as it often fixes such an issue. I have had a flash drive work fine for years after rewriting the bz* files.

Are you transferring to a User Share or direct to the drive? Asking as the Fuse layer used to support User Shares can impose that sort of speed limit. If you are transferring to a User Share then if it is all one one device/pool so it can become an Exclusive share (which bypasses Fuse) you can get the same performance as transferring directly to the physical device.

Have you put the licence key file from the old USB into the 'config' folder of the new one? You need to do that to get the licence transfer option.

You need to either set Unraid to an address on the 192.168.1.x network or set a gateway on the 192.168.2.x network.

@denishay This is the first time I have heard of this behaviour so it is probably going to need more information to sort out why it is happening to you .

You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.

UFS Explorer is a last resort when nothing else works and the data is valuable enough to invest in buying that software. The normal handling of Unmountable disks is covered 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. The Unraid OS->Manual section covers most aspects of the current Unraid release.

I am assuming that procedure is NOT what you are doing as you are simply upgrading parity at the moment?

if you are simply rebuilding the parity to larger drives and not using the specialist parity swap procedure then the Parity Check Tuning can be set to pause the process while drives are too hot, and automatically resume it when they cool sufficiently..

You need the latest valid licence to be there, the others should be deleted.

The Parity Check Tuning plugin allows for pausing array operations when drives overheat. I am not sure if currently it works with the specific case of a parity swap during the parity copy phase but it may (I will look into checking it out). Having said that maybe having an external fan to assist the cooling for such an infrequent operation is likely to be both more effective and less hassle.

That should have cleared the corrupt metadata on disk6 that was mentioned at the end of your screenshot. When you start the array in normal mode does the drive mount OK.

Note that ‘unmountable’ is different to disabled (which you must have since the drive is being emulated) and the two states require different actions to clear them. Handling of unmountable drives 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. The Unraid OS->Manual section in particular covers most features of the current Unraid release.

What is set as the source folder? What are the settings for the share holding the source folder?