trurl

Do you mean healthy as not being disabled, or healthy as in not showing any SMART warnings? You should click on each WD Red drive you have and enable notifications for these SMART attributes: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 266 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 33

Post diagnostics from SAFE mode

Related thread:

Best way to clear logs is to reboot. Reboot and post diagnostics. Also setup Syslog Server:

The only difference between eSATA and SATA is the connector on one end of the cable. If you have a free SATA port you can get a SATA > eSATA cable

Doesn't look like you did this

This is what I do. They also automate finding downloads.

Do you have krusader installed? Or even easier, do you know how to use the builtin mc (Midnight Commander)? Best to work with appdata directly on the server rather than over the network.

Run an extended SMART test on it, maybe replace it first.

Which you should also test for by trying that single stick in another slot if the test fails.

yes But having answered all that I agree with @Energen generally.

In disk order starting with cache

When working directly with the disks, cache is never involved (unless cache is one of the disks you are working directly with, of course).

By posting diagnostics of course

Edit the mapping and change the Access Mode

You should start your own thread with more details about your specific problems and your diagnostics.

Multiple disks on one connection is going to be a serious bottleneck for parity checks, rebuilds, etc. All disks must be accessed simultaneously for those. And as noted, USB is a bad idea anyway.

Do you mean you were testing whether to use the USB box? I would say it failed.

Did the short SMART test ever complete? I would replace. Do you know how?

Some of that might be connection issues, but there are these mixed in: Jul 28 18:29:04 vault kernel: ata6.00: cmd 25/00:28:a8:08:72/00:03:06:00:00/e0 tag 5 dma 413696 in Jul 28 18:29:04 vault kernel: res 51/40:17:b0:09:72/00:02:06:00:00/e0 Emask 0x9 (media error) Also, this SMART attribute is something to watch out for on WD Reds, in fact, I have it added to the notifications for those disks I have: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 266 Do you have a replacement?

Let's just leave docker out of it for now. We can talk about that in more detail later. We need to get into the details of rebuilding, etc. As already mentioned, you can't use 2TB parity with 4TB data drives. I don't see any point in buying a 2TB drive.

FTFY

Sounds like your question is more about how to use rutorrent docker. You can go directly to the correct support thread for any of your dockers by simply clicking on its icon and selecting Support. Perhaps if you read some on that thread your answer is already there.

Dockers are isolated, but it is possible for them to map the same shares, or to communicate in other ways, such as on the virtual network with API keys. I use transmission instead of ruTorrent. Probably you just need to map the same shares. Post your docker run for each as explained at this very first link in the Docker FAQ: