itimpi

Perhaps you started a copy which you quick;y aborted and the folders got created ready to receive file before the abort.

If the rebuild process has passed the point for the sector then both the drive and parity are updated accordingly. If the rebuild has not reached that point then parity is update parity to apply the change later. From a user perspective the system acts all the time as though you were writing to the disk in a normal manner. The only downside to writing to the array while is a rebuild is in progress is that both the write and the rebuild adversely affect each others performance while they are running at the same time.

You can use any method you like (including the ‘mv’ command). Parity will be maintained regardless of the method used.

The disk selection is done at a lower level than mover runs at. It is done at the driver level and at the point the file is created, and at that level the final size of the file is not known. Mover itself has no knowledge of what drive in the array the file will end up using.

The easiest thing to do is to reboot after removing the plugin to get the driver removed. Not sure if it is possible to remove the installed driver dynamically without a reboot.

Your ‘system’ share seems to have content on disk4. If this is the docker.img or libvirt.img giles then simply having the docker or VM services running respectively will keep this drive spinning as the services keep their respective files open.. Any writes to this drive would then also keep the parity disk spinning.

It might be worth trying downloading the zip file for the release from the Limetech site and extract all the bz* type files over-writing the ones on the flash.

Either order will work. The rebuild process simply makes the physical drive have identical contents to the emulated drive.

Not sure what you mean by this? If you add a disk to a parity protected array (that is not already pre-cleared) then Unraid will Clear it by writing zeroes to every sector specifically so that parity is not affected.

You do not mention what you need that was previously in Nerd Pack and what is not working as a result.

The correct handling of unmountable 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. This applies whether it is happening to an actual physical drive or to an emulated one (which is what you will have is the drive is shown as disabled with a red ‘x’). A format is never the correct answer if you want to keep any data. In the case of an emulated drive then we always recommending trying the check/repair before attempting a rebuild. The reason is that since a rebuild only makes a physical drive match the emulated one if for any reason the repair went badly you will at that point still have the physical disable drive available untouched to use as an alternative for data recovery purposes.

If you want to re-use an existing disk then you need to make Unraid ‘forget’ about it by: setting it to Unassigned start the array to commit that change stop the array This 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.

Unraid will find a user share folder regardless of whether it is on an array disk or a pool. These will show under /mnt/user at the Linux level. You will also find another view of the same folder on a physical device such as /mnt/poolname or /mnt/disk#

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread as that will let us see how all your shares are set up and where they files for them are currently located.

You should read the help built into the GUI for the Use Cache setting. That will point out that it is the Prefer setting that gives the behaviour you want.

You say that you issued a format command on disk15 before trying to rebuild it? You would have got a big warning NOT to do this unless you were prepared to lose the disk contents! The format would have created an empty file system on the emulated disk15 and updated parity to reflect this so a rebuild would just end up with an empty disk as all a rebuild does is make a physical disk match the emulated one. Do you still have the original disk15 untouched as if it has not completely failed it could be the best chance of recovering the contents.

Unraid will only try to read the SMART data if thinks the drive is NOT spundown. You probably have something else trying to read or write to the array that is causing the drives to spin up immediately after a spindown.

it looks like those diagnostics are taken shortly after booting. If this is correct, can you post new diagnostics after the speed issue has manifested itself so e can see if anything relevant is being logged?

One disadvantage of using a RAID controller is that it normally means that Unraid cannot monitor a disk's SMART attributes and thus warn you about issues that are reported via SMART.

That almost certainly means the error is from a plugin. You may have to go through a trial-and-error process to identify the culprit.

You can if you want but there is no need to as the plugin still functions as it has on earlier releases. The plugin provides more extensive capabilities than the built-in support but if you do not use any of these extra options then less reason to keep it.

With the File Integrity plugin you want to exclude any folders where the files are being continually updated. Ideally it should be used for files that once written are rarely changed.

It is probably worth mentioning that 4GB is now the minimum recommended RAM for running Unraid without issues. The RAM needed for all functionality to work reliably has been creeping up as more function is added so when loaded into RAM at boot more space is used by the OS.

Have you checked that any vfio bindings are still correct? Either of the OS or the Bios upgrades could lead to them changing IDs

@tTownTom have you checked the permissions at the Linux level on the share and the files in it? There have been a number of reports of permissions being wrong for network access and it only showing up after upgrading. it might be worth posting your system’s diagnostics zip file to your next post in this thread to see if anyone can spot something there.