JonathanM

No. You could do it manually, by setting the share to cache:only or cache:no, depending on where you want to target new files written to the share. Either of those settings will effectively disable mover for the root share, and allow you to manually keep the subfolders of the share on the drive of your choosing, either an array drive or the cache drive. If you don't understand how the array user shares work in relation to the individual disks, then attempting to do this blind will most likely result in irretrievable data loss. Don't attempt without posting for approval the exact commands or procedures you are planning to use.

Click on "Tools" and then "Diagnostics". You have yet to post the requested file.

Can you put a physical bare metal windows machine on that switch and benchmark reads from both servers please?

Perhaps it's a language barrier issue, but you will have to have a physical USB drive with a valid unique GUID to license unraid. That sentence makes me think your host is setting up a virtual drive for you to use, which will not work.

Or handling issues. Maybe your shipper has it out for you and is using your packages as footballs?

Maybe the client is borked and doesn't parse spaces in share names? Try changing the share to TV_SHOWS and see if it changes.

Are you sure you have the correct cable? Are the disks spinning?

Do you have any emails from your server?

Do you have... 1. A diagnostics zip file from a time period with all your current drives? 2. A status email or notification from your unraid server before it crashed?

Another option would be a VPN server on your home network, and connect to it with a VPN client on your phone. A point to point VPN like that makes it appear that your phone is still on your home network.

Given that you see the issue on two different builds, I'm inclined to think it's in your environment, and not under unraid's control. otherwise, there would be huge numbers of others seeing the same thing.

Reading is purely a function of the target data disk speed, no more, no less. Writing is a combination of the target data disk and parity. Increasing the parity speed will only effect writes to multiple simultaneous data disks. Reconstruct write mode changes that equation.

Until you get the temperatures back in the manufacturers acceptable operating range, disable spin down completely. Then at least the temperature variations won't be so bad. Ask @limetech about spinning up extremely cold disks.

I hesitated a good bit before posting this, but I think it needs to be said. I don't believe this is going to work out for your client. I'm not saying you aren't capable of building and configuring a machine that does exactly what you said it needs to do, or that your client won't be able to operate it when first installed. I'm saying that one of two things will happen. Either you will spend a HUGE amount of time keeping it running well, and you or your client will be unhappy with the billing for said time, or your client will use it happily until it quits working because of an update or something stupid, and it will be tossed aside. This is not a set it and forget it type of installation, and remote support will become a huge headache. If you said YOU wanted this system for your house, you were building and maintaining it all, then not a problem. Doing this same thing for a paying client? No way.

Or, just click on the start order column header to sort by start order instead of sorting by some other column. Yeah, it's a pretty heavy feature request. I've already been slapped for suggesting feature creep, so I'll shut up now.

Sounds like a feature request. Add a column to the far left, Start Order, with numbers indicating such. That would allow sorting based on the other columns, as the number would stick with the docker, until such time as the user dragged around the Start Order number in that column. You would be dragging the number to match the docker order you wished, rather than the way it is now where you drag to docker to the slot you want.

Shoot, I meant to point to the post that started the CF the LAST time somebody started using the unreleased project and asking for support. I was trying to give some background. If this fresh batch of folks had actually read back a page or two, all their questions would have been answered instead of posting the same stuff over again.

Do you have cache dirs plugin installed?

Here in the USA, purchase date is the official warranty term, but if you are doing an online RMA, it's a pain to get warranty after the factory date even if you legally still have warranty. Digging out a receipt and getting the manufacturer to honor it isn't worth the hassle most of the time.

Not particularly problematic. Either use the User Scripts plugin, or set things up in the go file on the USB.

Pretty sure this is the wrong place to post about this, it seems to be an issue with your Sonarr settings, not the docker itself. Take a look at Sonarr Settings, Media Management, and make sure you understand what each setting is doing.

compose is already available. https://forums.unraid.net/topic/35866-unraid-6-nerdpack-cli-tools-iftop-iotop-screen-kbd-etc/?do=findComment&comment=653719

If you are asking what I think you are, the answer is no. Perhaps more clarity in the question would help.

Yes. Generally speaking, anything not in /boot ,/mnt/diskX, or /mnt/cache exists only in RAM. There are complications to that statement, but in general it follows.

It's a discount for buying a larger license initially. Each further transaction has an administrative cost associated with it.