mlody

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mlody's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I don't think its the plex container. I have a BTRFS pool that I use for camera recordings and Plex has not relationship with it and it experiences the spin up and spin down. Weirdly, the pool is raid0 and it will spin up 1-3 drive while there are 5 of them in the pool. So, it can't even be a read operation because it would need to spin up all of the drives for a read operation.
  2. This doesn't necessarily have anything to do with the plugin or rclone or unraid but... Just in case anyone runs into this issue... here is a solution. This is more of an issue with pihole but rclone is affected because it does so many DNS lookups. I had rclone backing up to onedrive from the unraid server and it wouldn't delete and uploads were odd. I checked the script result and I saw these entries: 2021/03/24 11:51:54 Failed to create file system for "onedrive:backups/some_folder_name": failed to get root: Get "https://graph.microsoft.com/v1.0/drives/blahblahblah/root": dial tcp: lookup graph.microsoft.com on 192.168.xx.xx:53 server misbehaving 2021/03/24 11:51:54 Failed to create file system for "onedrive:backups/some_folder_name": failed to get root: Get "https://graph.microsoft.com/v1.0/drives/blahblahblah/root": dial tcp: lookup graph.microsoft.com on 192.168.xx.xx:53 server misbehaving This meant that rclone was having DNS resolution issues. Well, I had a pihole serving up DNS requests. Apparently, they introduced rate limiting to the pihole and because rclone is so chatty with DNS, it was hitting the rate limiting count when trying to backup. You can see this by a spike on pihole during a backup. The solution is to modify pihole's /etc/pihole/pihole-FTL.conf and set the RATE_LIMIT. I set it to RATE_LIMIT=0/0 because that disables it but I imagine you can tweak and tune as you want.
  3. FYI, I fixed the boot problem by replacing the bz files after creating another usb stick and copying it from there. It booted up, didn't start the array right way, but the array started back up.
  4. I updated to RC2 and now I have a boot loop on the blue screen. it counts down to 0 and then restarts to 5 and keeps doing that. Hitting enter on the keyboard doesn't do anything. I'm trying to download the zip file to replace the bz files but I can't find the link... can someone point me to the link and/or give suggestions on how to fix this?
  5. Hey everyone, I am trying to hunt down with what appears to be a network problem. In fact, I upgrade the NIC in the server to an supermicro 10G with the x530 chipset thinking that it might simply be network saturation. When I read from the server I can saturate the NIC on the slow PC to ~980 mbps. When I do write tests on the drive on the unraid box, it can write at about 330 MB/s (~2.5 gbps). When I try to write to the cache pool, it writes at about 60 MB/s (~ 480 mbps). It varies wildly when trying to write to the cache between 40 MB/s and 80 MB/s. I noticed that if I turn off the VM service, unraid will write at 1 gbps. The VMs are not running on that drive pool and, in fact, they're quite VMs. One is a reverse proxy box and the other is a pihole with Splunk on it. They don't write or transfer much of any data. Any thoughts on how to troubleshoot this issue?
  6. I've been trying to hunt down an issue where the write speeds are degraded when running the ethernet with bridge mode enabled and the VMs are running. After breaking my VM's ethernet connection and then fixing them, the whole damn thing crashes now. A bit frustrated with the whole thing... Not sure if anyone can see anything in those logs because its a hard crash. I have to cut the power and turn it back on and then after a few min/hours, it will crash again. I found an error in a live log stream hoping to catch something that is also attached. I suspect its something to do with the hypervisor and its drivers. The reason is if I turn off the VM service, write speeds are great and because of the error I'm seeing in the logs. Thoughts? tower-diagnostics-20201213-1127.zip
  7. I'm on 6.9 beta25 and I've been trying to get close to 1 gbps from my cache/unraid pool thats all SSD and I can do that but not when docker is enabled. When I have the docker service turned off, I am able to saturate the entire gbps (avg 105 mb/s) but when I turn on the docker service, the transfer speeds to the unraid server drop to avg 55 mb/s and vary wildly between 35 mb/s and 70 mb/s during transfers. Happens on SMB and on NFS. Any ideas on what might be going on? The transfers between unraid and a docker container avgs around 33 mb/s I'm not doing anything special with the docker networks. Some Bridge mode, plex on host, a few on br0 with a static IP. I might upgrade to RC1 but haven't done it yet. I stopped all the containers but kept the service on and the transfer rates vary wildly. I don't have any containers that are super have I/o. I think it might have something to do with the networks that are setup for docker but I'm not sure what. I have a cache pool of SSDs, I also have an unassigned SSD drive that should
  8. Anyone having connection issues to Deluge from sonarr and radarr? I think I updated the containers a few days ago (all of them are currently up to date) and sonarr and radarr can't reach deluge (unable to communicate with deluge. Error: ConnectFailure (No route to host): 'http://...:8112/json). I can get to the webgui for deluge just fine, I can get to sonarr, radarr. Sonarr and Radarr can reach sabnzb just fine in another docker container. Also, privoxy works just fine with jackett through the container.