TheRefugee

I'm not certain of the correct terminology for containers/docker/images. Do I have my ports set up properly so each container is operating independently? I have multiple containers because I was told that rutorrent can only handle 3,500-6000 torrents before the webgui stops working properly. I don't have nearly that many now but I separated TV, Movies and books into their own container because it is not out of the question that I would start to push the upper limits of what rutorrent can handle.

Is this expected behavior? I have several instances of this docker and when I update one, this immediately shows on the others. When I update the remaining instances, nothing gets pulled and they update without issue. Curious as to what is going on. Otherwise, the docker works great and all work wonderfully.

I will be able to shut down and move my 8TB disks onto the motherboard tonight and I will start the parity check tonight as well. To clarify the order of operations: 1. Shutdown 2. Move 8TB disks and SSD onto motherboard, leaving 4TB disks on the SAS2LP 3. Power On, start array 4. Parity check Does that look correct? No other restart is necessary after getting the array to start up after moving the disks around? Just wanted to clarify because I wasn't sure if you were assuming I can hot swap and then do a restart. edit: My server has been up since the last parity check. Powering down to switch the disks will be the first time the server has been offline since the last 5 error parity check.

Currently, 6 data drives (4 x 4TB and 2 x 8TB) and 2 parity drives (2 x 8TB) are on the SAS2LP with the Samsung SSD being the only drive connected to my motherboard. I have 6 total motherboard ports I can connect drives to so moving the 2 parity 8TB drives, 2 data 8TB drives and the SSD to the motherboard will work. Is this the preferred option? Do I need to write down which cables are connected to which drives beforehand? Does switching which drives are connected to which port interfere with my array being recognized or is it irrelevant?

My server isn't up all the time so it almost certainly was rebooted between those dates. It's rare for my server to be up for more than a month at a time. Longest I have gone is 45 days, irrc.

I often get exactly 5 parity errors during my parity checks and it is past time to diagnose the problem. I have had my share of unclean power shutdowns that I have mitigated but I want to be prepared for the next time it happens. Are there any steps I should take before executing my next parity check that will help me narrow down what could be causing the issue? Obviously, I will include the diagnostic zip file but are there any specific logging settings that should be enabled to catch my specific problem? Note: in my system log, there are recurring power failure warnings. I have a portable room a/c that triggers my UPS to kick on for 2 seconds before returning to normal operation. I am guessing there is a drop in voltage but the lights in my room don't dim and all other appliances operate normally. Hopefully, this isn't a problem and the UPS is just doing its job protecting my NAS. syslog.txt

You're a saint. Problem fixed.

Getting this error after update when trying to add/remove labels. I have 3 instances of this container running but this is a new behavior.

From https://wiki.archlinux.org/index.php/RTorrent How do I go about starting a screen for rtorrent inside docker? /etc/systemd/system/rtorrent.service [Unit] Description=rTorrent After=network.target [Service] Type=forking KillMode=none User=rtorrent ExecStartPre=/usr/bin/bash -c "if test -e %h/.rtorrent_session/rtorrent.lock && test -z `pidof rtorrent`; then rm -f %h/.rtorrent_session/rtorrent.lock; fi" ExecStart=/usr/bin/screen -dmfa -S rtorrent /usr/bin/rtorrent ExecStop=/usr/bin/bash -c "test `pidof rtorrent` && killall -w -s 2 /usr/bin/rtorrent" WorkingDirectory=%h Restart=on-failure [Install] WantedBy=multi-user.target ------------------------------------------------------------------------------------------------------------------------------------------------- /etc/systemd/user/rtorrent.service [Unit] Description=rTorrent After=network.target [Service] Type=forking KillMode=none ExecStart=/usr/bin/screen -dmfa -S rtorrent /usr/bin/rtorrent ExecStop=/usr/bin/killall -w -s 2 /usr/bin/rtorrent WorkingDirectory=%h [Install] WantedBy=default.target

Thanks for taking the time to respond. To be clear, my entire array wasn't effected, only my Movie share. The torrent didn't have a path, I didn't select "don't add torrents name to path", it just so happened to contain a single file. Fortunately my TV and Music shares are separated into their own shares so those remain intact. In the future, I am absolutely going to disable the delete all option; for my own utilization, I can't imagine a practical use case where the delete all accomplishes anything that the regular Delete Data option wouldn't. As per your suggestions: 1. I plan to keep torrents seeding long term so my cache really only pulls duty for appdata. 2. Disabled 3. Looking at my plexpy data, 1710 movies got wiped (ouch) but I have ~980 of them backed up on a remote server; I have started the 3.5 mb/s slog to recover those and the others will be recovered over time. I resorted to taking screen shots of my plexpy library data so I can have a list of files; don't want to miss any on my rebuild. I think I will end up biting the bullet and building a local back up because rebuilding from a remote server is a bit ridiculous at my download speeds lol. 4. I use CA backup but I'm not sure what good it would do me for recovering my plex metadata since I will slowly rebuild my library with new additions sprinkled in. So any time I refresh my plex library, they will get cleaned out; I think it will be the least hassle to rebuild bit by bit.

I think this is what I did My share, "mnt/user/Movies/" contained a file that was not in its own folder, "/mnt/user/Movies/movie.title.2016.mkv" as opposed to "/mnt/user/Movies/movie.title.2016/movie.title.2016.mkv" When I selected delete data (all) with the impression that it would delete all data associated with that single torrent file, rutorrent instead deleted the entire directory. Any confirmation of my missteps would be greatly beneficial to my understanding of what went wrong.

Thanks for taking the time to try and push me in the right direction. I greatly appreciate it. Regardless of how this shakes out, I will be reevaluating my storage solutions; time to have a local backup. I'm mostly upset about my Plex library and the countless hours curating movie posters, backgrounds, and alphabetical/chronological series order. I have a backup of my Plex metadata so maybe the Plex forums will have some solutions for preserving that data once backup is complete....in 6 months lol

I have a little less than half of it backed up on a remote server and the other half can be recovered from third party sources but if I can recover the data locally that would be the vastly more convenient option. Nothing critical like family photos has been permanently lost. Backing up/re-downloading ~30TB of data at 3MB/s is something I would like to avoid if possible.

From my previous usage of ruTorrent, there are 2 options when removing a torrent. One only removes the torrent file and leaves the data and the other option removes the torrent file and the corresponding data of that single torrent file. 1. Array was stopped within minutes of the "delete Data (All)" operation. Tower still powered on though. 2. XFS 3.I am a total novice so I am not going to do anything on my own until further instruction. 4. I can only hope! From my complete lack of knowledge and uneducated opinion, after manually deleting the "Zero Bytes" file from my mac/smb share finder window AND THEN returning to the rutorrent webGUI and selecting the "Delete Data (All)" option on a single torrent, the plugin couldn't see the file and then deleted the entire folder. FWIW, the file was not in it's own folder but placed directly in the share (/mnt/user/Movies/title.2016.mkv/". To be perfectly clear, I don't want to blame binhex's rtorrent docker because I am admittedly a novice user and I find it hard to believe it wasn't complete user error.

After hash checking a torrent file returned 0%, I deleted the file showing "Zero Bytes" on my mac finder/smb and then selected Delete Data (All) option in the rtorrent webGUI and every single file in the share was deleted.