itimpi

You never mention the Minimum Free Space setting which can be relevant in selecting a drive As to the questions: Difficult to answer definitively as it can depend on many factors (such as the disk controller), and what Unraid currently has in RAM at the time in terms of directory information. In ideal conditions only the required drive is spun up. It probably depends on the client. You will definitely get an out-of-space error for the file that does not fit - whether the others then copy will depend on the client (but they should then go to another drive as long as the share settings allow another drive to be selected. Mover works at the individual file level not the folder level. At the point it selects a drive a file size of 0 is assumed (and thus the importance of the Minimum Free space setting). If a file already exists then Unraid will always attempt to overwrite it in situ so you get an out-of-space error. Not quite sure what you meant by Unraid balancing out, but it never moves a file from one array drive to another.

Every array drive in an Unraid system is a self-contained file system that can be independently read on any Linux system.

Reasonably certain this is what will be required.

I would agree as far as disk health is concerned, but using a scheduled monthly parity check has the additional advantage of checking that parity is still in-sync with the data drives as it is possible for them to get out-of-sync for other reasons than just disk issues.

Normally you would post the complete diagnostics.zip file that is downloaded when you request them. If instead of the zip file you are seeing individual files then it probably means that your system is showing the contents of the zip rather than the zip file itself, so you need to find where the zip file has bern put so you can upload it. From your description it sounds as if the parity drive has dropped offline and the system probably needs a reboot/power cycle to get it back but the full diagnostics would allow us to confirm this.

Looks like you missed the last step where you enter the IP address of your Unraid server into the Remote Server field so that the server logs to itself An alternative is to use the option to mirror to flash but this is often not desirable if you want to minimise writes to the flash drive.

You do not normally want an SSD to be in the main array if it also contains HDD as the write performance of the SSD is constrained by the overhead of updating parity.

@TexasDaveSince you have just added some new drives are you sure your PSU is up to driving them? Also, are you using power splitters?

FYI: I think you mean disk1 in the main Unraid array? Just checking as that array is not using RAID5 (and hence the name Unraid). In terms of checking/repairing disk1 then the easiest way to proceed is to do it from the GUI as described here in the online documentation. If you must do it from the command line then you should have used /dev/md1 as the target device since this would preserve parity. Luckily your command was wrong in that it had the wrong target device (it should have been /dev/sdf1) as that would have invalidated parity.

Unless something has changed very recently then your scenario cannot happen! I do not believe that Mover Tuning over-rides the Use Cache setting so it only makes decisions on whether to move a file in the direction designated by the Use Cache setting and never moves them back and forth.

It is important that any dovker spots are configured to create and folders/files on the main array with correct permissions for trouble free working as they can bypass the normal Unraid mechanisms. The New Permissions tool is what is needed when things go wrong. Personally I think this tool would be better renamed to something like Reset Default Permissions - the current naming is a hang-over from when it was a required step when upgrading from Unraid versions prior to Unraid v5.

I have not heard of it creating duplicate files unless you told it to do so (I.e used copy rather than move)when working normally. I guess another possibility might be a system crash while attempting a move as it uses a copy/delete strategy so if the system crashed before the delete part you could end up with the source left behind.

There had to be something else going on as the ‘mv’ command would not create files with the ‘conflicted’ added to the file names. there should be no difference between using ‘mc’ or ‘mc’ commands as long as you make no mistake in the command line for ‘mv’. if you are using any recent version of Unraid then the recommended tool to use is now the Dynamix File Manager (installed as a plugin) as this is Unraid aware and can protect the user from some common mistakes that can cause data loss.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

With only 2GB of RAM the only way to upgrade (or downgrade) is to use the manual method as documented 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.

Follow the process documented 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.

If you are passing a GPU through to a VM then simply do what you would do with a physical PC (e,g. connect its output straight to the TV).

You can pass through a drive in its entirety to a VM. Not sure why it needs to be a cloned drive though.

There is also the fact that Limetech have plenty of new features planned for current Unraid that I could easily taking a few years to come to completion without any distractions like trying to support a new platform.

Not quite sure I understand this? You can download the latest memtest that can test ECC ram from memtest86.com for free. Do you need the Pro feature?

Have you followed the instructions in the online documentation here for manually creating the flash drive under Linux.

One thought is to boot the server off a Linux Live CD and then create the Unraid flash drive from there.

The IP would be changed via the network settings, and the array needs to be stopped to change them

What you have described should not make shares inaccessible. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

At the moment you can have multi-drive btrfs pools supporting a wide variety of raid levels supported by btrfs. In a similar way you will be able to have multi-drive ZFS pools supporting the raid levels that ZFS supports.