mhn_10

Members
  • Content Count

    32
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mhn_10

  • Rank
    Newbie
  1. An unknown error occurred (4294967283) Error code: 4294967283 Getting the above error all of a sudden. Running Plex Version 1.21.0.3711 and unraid 6.8.3. Any ideas why this is happening
  2. Hi, my unraid server was working perfectly until now. I'm only able to access my unraid dashboard. Looks like the server is not able to connect to internet. I'm worried if I've been hacked. I'm attaching diagnostics here unmhn-diagnostics-20201120-0136.zip
  3. rtorrent was working fine, but suddenly getting the following errors (attached screenshot) What could be the issue. 2020-07-06 20:45:05,333 DEBG 'rutorrent-script' stderr output: 2020/07/06 20:45:05 [error] 713#713: *65 connect() failed (111: Connection refused) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.106:9080" unmhn-diagnostics-20200706-2042.zip rtorrentlogs.txt
  4. No I haven't done it. The field is left empty.
  5. It started picking up the proxy when I gave port 8119 of rutorrent
  6. I had my sonarr & radarr connected to Jackett indexers. This was done through privoxy of delugeVPN. So in my settings>general of sonarr/radarr, I had 192.168.0.106 of DelugeVPN with 8112 port. Recently my ISP changed, and now my subnet is 192.168.1.x. So accordingly I changed the LAN_NETWORK Container Variable of Deluge to 192.168.1.0/24, restarted the container. I also changed the proxy settings inside sonarr/radarr, and copied my new jackett url to indexers. But the indexers are not getting connected. and I get the error Failed to test proxy: http://services.sonarr.tv/v1/pin
  7. Here is what I did. The old configuration was 1x 500 GB + 1x 250 GB ssd I needed to replace the 250GB one and I had just installed it recently in single mode. So I was pretty sure that it won't have any data on it. So when the mover finished with 11 GB remaining on cache, I took the chance of replacing the 250 GB ssd with the new 500 GB ssd. This is a chance I took, since I had all the appdata backed up already if anything went wrong. After I replaced the the cache with 2x 500gb ssd, I did a balance with RAID0 and then set the required shares to prefer and started the mover b
  8. Yes, It shows up when I explore it. Looks like it only has app data Disabled in settings
  9. My mover ended with 11.2 GB still in cache. I made sure I turned of docker and VM. And changed all shares to cache:yes Why could this be happening since there is nothing else in the server that could access the files. Could it be that deluge might be locking the files, even if deluge is not running?
  10. Seeing some progress. Cache has reduced to 11 GB remaining. So I guess its still running. Any idea on why there is a delay?
  11. I'm trying to add a new (500gb) cache disk to my cache pool by replacing the existing 250gb disk. Presently its 500gb+250gb cache pool. To do this, I've backed up my appdate folder using the CA Backup/Restore plugin, and then followed instructions here https://wiki.unraid.net/Replace_A_Cache_Drive I started the mover, and the mover has copied some data onto my array, but its now stuck at 43.4GB remaining for a long time. Any idea as to why my mover is stuck. diagnostics-20200702-2148.zip
  12. Thanks. I took a backup of the appdata using CA Backup/Restore and then I'm gonna follow this https://wiki.unraid.net/Replace_A_Cache_Drive to add the new drive. After that I'll do a balance with RAID0
  13. Gonna recreate my database. Sigh. What is the general procedure next time, when I want to change my cache pool? Planning on getting a drive for making it RAID0 cache pool
  14. Looks like my plex database is corrupt. If I try copying just the database files from the old plex container to the new linuxserver container, the container fails to start.
  15. 3-4 Days I would think. And the logs you saw was after a reboot. Since I rebooted when plex started crashing