NeoJoris

Members
  • Posts

    27
  • Joined

  • Last visited

Converted

  • Personal Text
    100TB

Recent Profile Visitors

909 profile views

NeoJoris's Achievements

Noob

Noob (1/14)

0

Reputation

  1. @xhonestly If you dont have a backup or a file from the folder appdata/sonarr/Backups/scheduled i think you should start from scratch
  2. @xhonestly Sorry for the late reply. Only try this if you have a backup of your old databasefile (via manual backups or appdata backup plugin) Steps: remove docker image remove (specific) appdata folder install older version of this docker (see attached image) after stopping the newly made container (I had an backup of the database file) move the old database file into the new folder (only necessary if backup has been stored elsewhere) run DockerSafeNewPerms via tools tab (re)start the container Good luck!
  3. I have the same error as @boianski I tried the sollution by @bobobeastie but not succesfull. Also tried to delete the database, and try to recover it from a backup but also not succesfull. Also tried another docker but also not succesfull.. I really dont want to set-up a fresh docker, all the settings are also in this database and not in the config.xml... Does anyone know how to install a earlier version of this docker so i can use the built-in restore to backup my settings? Ive done a rollback to repository binhex/arch-sonarr:3.0.10.1567-1-01 Managed to restore my settings and database, via the build-in restore function and a scheduled backup file
  4. Thanks this rollback worked for me.
  5. Thanks, After replacing disk 6 (and xfs_repair in maintenance mode) I've got it working again. But only without cache drives, which is fine for now.
  6. root@NAS:~# cat /tmp/file.activity/file.activity.disks /mnt/disk1 /mnt/disk2 /mnt/disk3 /mnt/disk4 /mnt/disk5 /mnt/disk6 /mnt/disk7 /mnt/disk8 /mnt/disk9 /mnt/disk10 /mnt/disk11 /mnt/disk12 /mnt/disk13 /mnt/disk14 /mnt/disk15 /mnt/bufferdownloads /mnt/cache I did Yes, is fixed now Well I was not planning to replace that one just yet. As it still functions correctly with all other data; I do not understand what that has to do with the starting and stopping of this plugin. Can you elaborate? Ive attached dianostics nas-diagnostics-20220516-1512.zip
  7. Same here on version 6.9.2 2021-04-07 No file activity visible and service stops repeatedly (restarting service via first tab does not result in any file activity) nas-diagnostics-20220511-1614.zip
  8. I'm also experiencing some problems... Including being unable to login to game stores. ==> /mnt/user/appdata/lancache-bundle/log/nginx/access.log <== [wsus] 192.168.1.148 / - - - [10/Mar/2021:17:43:30 +0100] "GET /msdownload/update/v3/static/trustedr/en/authrootstl.cab?7768c4ebe73d95a2 HTTP/1.1" 502 182 "-" "Microsoft-CryptoAPI/10.0" "-" "ctldl.windowsupdate.com" "-" ==> /mnt/user/appdata/lancache-bundle/log/nginx/error.log <== 2021/03/10 17:43:30 [error] 2550#2550: *483 ctldl.windowsupdate.com could not be resolved (110: Operation timed out), client: 192.168.1.148, server: , request: "GET /msdownload/update/v3/static/trustedr/en/authrootstl.cab?7768c4ebe73d95a2 HTTP/1.1", host: "ctldl.windowsupdate.com" Although if other people still got it working, I might think it is my setup...
  9. I'm sorry to maybe misinterpreting your problem, but have you checked for any hardware faults? Please try some cpu and memory tests (xmp was for me a random crasher and causing some drive and network instabilities on a threadripper)
  10. To better understand your problem: Is this your user name? Also tried "samba reload" ?
  11. Does this mean we can upgrade to 6.9 rc1 directly?
  12. Hi, thanks for updating, unfortunately I have to roll-back again due to the following;
  13. I'm not trying to hush you, but any idea when version 6.9.0-beta35 will be supported? I had to rollback just now.
  14. I have somewhat the same issue: I have a dual socket motherboard which has onboard error leds and when these errors happen the leds points at the 2nd CPU. I still have some troubleshooting to do, (re-seat the CPU in the socket (re-seat the RAM), and if that fails switch the CPUs from socket), but it is hard when the system continues to run without errors for months even though i did not change anything.
  15. Deze mening deel ik. Al moet de vertaling dan inderdaad wel goed/goed genoeg zijn. Heeft iemand een link naar de pagina waar we de vertaling kunnen zien/aanpassen?