itimpi

As long as it is configured to access its files via a User Share Plex will not be aware of whether any particular file is currently being cached on a pool or is on the main array.

Whatever you do to try and tweak mover make sure you have set then Minimum Free Space for the pool acting as cache to be larger than the biggest file you expect to cache (the normal recommendation is twice that size to give some headroom). This sets the criteria for when files should start by-passing the pool and going directly to the array. Pools tend to start exhibiting problematical behaviour if they get too full so you want to avoid this. if transferring very large files it is normally better to write them directly to a array drive and bypass the cache altogether.

There is a fundamental assumption built into Unraid that a file only exists in one location at a time, so it can either be on a pool or on the array, not both. Your idea would mean that this assumption would no longer be true which could have all sorts of consequences.

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.

You may find this section useful from the 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.

It is unlikely to make any discernible difference as I am sure even the slower SATA port will have much higher throughput than any HDD can support.

The moment you remove (or add) hardware you should assume that the hardware id’s for passed through hardware are likely to have changed and need redoing. I think you can also sometimes getting them changing after an major OS update due to changes in the kernel level.

There is no realistic way to change the permissions on that script. I do not understand why you want ‘execute’ permission on those files - I would expect it to be a serious security risk.

Normally the modular cables for power supplies come with multiple connectors on the one cable so you do not always need splitters. If you think you need to use SATA->SATA splitters avoid splitting them more than 2 ways.

If you mean the splitters are SATA->4xSATA then they are often not able to handle the current for more that 2 drives without voltage sags which can cause intermittent drive issues. Molex->4xSATA splitters are normally fine with 4 drives.

It should be if you started the array in normal mode rather than Maintenance mode (although performance will be significantly degraded until the parity build completes).

Once a drive is disabled (red 'x') you have to rebuild the drive to clear this: status Stop array Unassign Parity Drive Start array to commit change Stop array Assign parity Drive Start array to rebuild parity drive.

Did you remember to stop the array before trying to change it to xfs?

The automated transfer can be done once per calendar year. For any transfers more frequently than that you need to contact support. i see no reason not to continue using the SanDisk flash drive. I have some that I have used for many years. The only problem with SanDisk is that they are a brand that is one of the more commonly ones counterfeited but if you have a genuine one no reason to suspect there will be a problem with it.

I think you should post the diagnostics so we can check what the actual state is. You do not mention what sort of SMART errors you were getting so we have no idea if they are ones that indicate a likely drive failure or not. Posting diagnostics would allow us to see the SMART reports for all drives. If you have two drives being emulated and two parity drives then it will not actually be doing a parity sync - just a read check of the remaining drives so probably not a lot of point in continuing it.