IndianaJoe1216

This solved it. I had a sata power splitter on those SSD's. They came in a 2 pack and I swapped to the 2nd one and haven't had issues since then. Thanks!

Recently I have been having issues with my cache disks. All of my docker services stop and then I see a large number of btrfs errors on one of the disk logs. In order for it to be seen again I have to shut down the server open the lid disconnect the sata cables, reconnect and it is fine for a random amount of time before it happens again. It's usually at least a day. I have attached my diagnostics file. I am running a Dell R720 with all 8 bays filled with 20TB Exos drives. My cache disks are connected to the onboard sata ports (they are only 3gbps). I tried using an extra Mini-SAS port but it was causing issues with my disk in slot 0 for some reason and I am wondering if this is the same issue. It appears that the SSD is losing power thus losing connectivity, but am not skilled enough at reading the diag reports to be able to tell. Thank you! diagnostics-20230412-1516.zip

So I think the UDMA CRC errors on both disks is due to me swapping the disks between the slots to check if it was an issue with that specific disk. The mini-sas cable does not break out to SATA on those drives There are 8 slots total and 4 on each SAS cable but those 2 SAS cables come together into a single connector and plug into the motherboard in a weird double sas connector. I really don't want to replace the backplane on this bad boy but I am starting to think that might be the issue.

I recently swapped out the drives in my R720 for Exos 20TB drives and redid the configuration. When rebuilding the parity my parity disk 1 (slot 0 on the server) goes into a disabled state and shows 1024 errors in the errors column. It looks like the device is disconnecting randomly. I have reseated the PERC H310 (flashed to IT mode) as well as the mini-sas cables to no avail. I have attached my anonymized diagnostics file for reference. Any suggestions would be appreciated. nas-diagnostics-20230227-1300.zip

I have have been using Lancache for quite awhile now and it's been working great for me. I even have it running through Pihole and that is working well as well. I am having one issue that I wanted to check on though. My initial download speeds are terrible. Typically less than 30mbps. My server has a 10G NIC to my main switch and I have 1gbps line speed. Disabling lancache, I can typically run in the 700+ mbps range. The lancache documentation says to add a second IP to your docker container but I have been unable to find any documentation on how to do that within Unraid. If someone could point me in the right direction I would really appreciate it.

I am getting the same errors as well and have specified UUID as well as leaving it set to "All"

I am having the same issue. It's pegging my server at 100% CPU usage since the update. Doesn't seem to be CPU specific as I am running a Ryzen 1800X while you're on a Xeon. @binhex Wondering if this is widespread and most haven't auto updated yet? Edit: @jademonkee I just did a force update of the container and it appears to have settled down.

Want to bump this again to see if anyone else is seeing this. Binhex's docker is by far the best one out there but for some reason I CANNOT get autotools to work consistently. Anyone have any ideas on places to check?

Going on a couple years with my Unraid build and it just keeps getting better. Keep up the good work!

Parity rebuild in progress! Thanks for all your help! 25TB free is a BEAUTIFUL sight!

There are 3 shares that are written to the most often (which are the only 3 on those drives) and when I started the first copy I went ahead and adjusted the shares to exclude the 2, 1.5TB disks. Yeah good call on add the other drives during the new config process, but I have 2 Exos enterprise drives on the way and I want to swap my parity drives out with those after I rebuild which unfortunately means rebuilding several more times so I am looking at ways to minimize the damage there, but that's still TBD. Wow I am an idiot. Since I am rebuilding anyways I could just do a new config and pull the parity drives at the same time since they are going to be rebuilt anyways. That would allow the new drives to be rebuilt as parity and I could add the current ones to the array no problem.

Does using unbalance matter vs command line especially if I can verify? Also, once the copy is completed and validated what's the process for removing the disks? At this point the data on the disks is on the 1.5TB and the 10TB in the array so the parity would reflect that so I can't just pull the disks and leave those slots empty. That means I would have to do a new config and then rebuild parity?

Unbalance actually has a verify stage after the copy is finished that runs a rsync -rcvPR -X. I was looking at the command syntax you sent over and since the 2nd line is -narcv wouldn't that just be a dry run because of the -n? Thanks for all the tips. It's showing me that I need to read the rsync syntax and I'm wanting to get more familiar with the Linux command line now as well. Without this I would have tanked my server somehow. :)

I am actually copying one of the 1.5TB's over to the 10 right now using the Unbalance plugin as I've moved directories before that way and was successful. I was going to see how that goes before moving to command line that way I don't have to take the dockers down. Unbalance is using rsync -avPR -X so I'm doing some more digging into rsync to learn a little about the different flags available. That is extremely helpful. Common sense tells me that a move is faster than a copy, but that makes perfect sense when you throw in the extra drive activity.

Good call on the copy! Not incredibly experienced with the Linux command. The data on the drive is all technically "Live" because it's mostly media for my Plex container and part of my caAppdata Backup lives there as well.

I just thew in a 10TB drive that is completely empty so theoretically, I could move the entire contents of the 4 and the 2, 1.5 drives onto the 10 and still have room to spare. Could I think just remove the other 3, unassign them and rebuild?

My full array currently has 12 drives in it (2, 10TB Parity Drives and 10 data drives. 5, 4TB drives, 2, 8TB drives, 2, 1.5TB drives and a single 10TB). I am wanting to get 2 more 10TB drives and replace some of the older smaller, pre-fail drives in the array. Specifically the 1.5TB drives and a VERY old HGST 4 TB drive that I would like to remove. Is it possible to do this? I can pull 2 drives at once and still rebuild since I have 2 parity drives right? I would think it would be a long process of pull the 4TB replace with a 10TB and rebuild and then do the same with the 1.5TB drives? Of course doing a pre-clear etc prior to, but as long as the original drives are still good and available there isn't really much risk in doing so is there? Thanks,

Gonna bump this up as I didn't get any feedback and it sounds like maybe this was something @binhex was looking to fix by switching to rtorrent-ps. It seems like the gui and it's tasks just hang after awhile.

Hello, just want to start by saying that this is by far the best torrent docker that I have come across and has been a life-saver. I am having an issue that I was hoping to get some support on or see if anyone else is having the same problem. I use a combination of Autotools, the unpack feature and Ratio Groups to automatically label new torrents, move them to a folder once the download is complete and then remove them after a certain period of time. When a torrent is added by either Sonarr or Radarr it gets a label of either TV or Movie. Pretty standard stuff. The path to that item is /data/Torrents/Download/TV or /data/Torrents/Download/Movie and once completed I have the auto move set to move the torrent to /data/Torrents/Complete/TV or /data/Torrents/Complete/Movie respectively. Once completed if there is anything that needs to be unpacked that is completed at that time as well. The downloaded item then remains on my server in that folder for 2 weeks and is removed regardless of the seed ratio (this is completed via ratio groups.) When I initially set this up it worked just fine. I tested it multiple times and everything went swimmingly. The problem I am having now is the all of my docker containers are automatically shut down every night for the CA Backup Plugin to run and backup all of my configs. For some reason after that plugin runs all of the features mentioned above stop working and won't start again until I go and stop and restart the container, but everything that should have happened between then doesn't. It will remove old downloads after I restart usually, but anything added after the plugin runs won't get assigned a RatioGroup, Nothing gets auto unpacked or moved to the correct folder when complete. I don't see anything in the logs that would cause this and there shouldn't be anything in the rtorrent.rc file that needs to be edited for this either. Is anyone else having this issue or know of a fix?

When adding a torrent to rtorrent via sonarr or radarr should that download be following the autotools setup in the rtorrent UI? For some reason, my sonarr and radarr downloads do not go into the appropriately labeled folders they go into the top level "Download" Folder. It's fine if I manually add a torrent file to the watched folder, but not if an item is added via sonarr or radarr. I can set the download directory in the sonarr and radarr setup just didn't know if it is expected for those to not follow autotools.

Does anyone have issues with rtorrent stopping torrents after some time with Sonarr/Radarr hardlinking. It looks to me like rtorrent may be losing access to the files inside the incomplete folder after the hardlink is completed. Not sure if that is exactly what is happening though. Is there a log somewhere I can review to verify this behavior?

Ah yes, that is the issue. I discovered that config file right as you were posting this. Tested and restarted and all is working now. Thank you!

Anyone else have issues with this container automatically switching the default download directory? I want the download location to be /data/Torrents but every time the docker restarts (Every morning because of backups) it switches back to /data/incomplete. This causes an issue in Windows because Windows sees both incomplete and Incomplete and I can't see any files in either folder. Sonarr and Radarr are also denied access to that folder as well so they can't post-process anything from the incomplete folder. Any help would be greatly appreciated.

Thanks Frank, I ended up completely wiping my cache drive and setting it up as xfs instead of btrfs and restoring my apps from a backup. Things are working a lot better now from the docker app standpoint but from a windows SMB share view I still have to finagle things a lot to be able to move/delete files. I have even created a new unraid user that matches my PC username and password and am still having issues. Any ideas how I can correct this without having to go to tools and use the new permissions tool all the time?

I have some files on my cache drive that I am unable to delete. I have tried deleting them through SMB and Krusader and neither can actually remove them from the drive. My cache is currently full so I need to remove them from the drive to free up some space. I followed Spaceinvaderone's video on creating a root share through SMB. That worked to an extent but I have to run the new permissions tool every time there is a new file and since I have been doing that I cannot delete these files from my cache. Any ideas? I was able to delete the files through the Unraid Terminal using the rm -r command on the suspect folders but my permissions I believe are still a mess. Any way to get those straightened out?