I am a bot, and this action was performed automatically. Once your question/problem is solved, please comment anywhere in the thread saying '!solved' to change the flair to solved. This post has been published and no further action is required for anyone to read it. Those humans will likely ask you for the exact same thing this comment is saying. If you're still stuck you'll have useful debug or trace logs and screenshots to share with the humans who will arrive soon.
#SONARR LOGS DOWNLOAD#
Searches, Indexers, and Trackers - For if something cannot be found.
#SONARR LOGS HOW TO#
Please review our troubleshooting guides that lead you through how to troubleshoot and note various common problems. Note that Info logs are rarely helpful for troubleshooting.ĭozens of common questions & issues and their answers can be found on our FAQ. Logs should be provided via the methods prescribed in the wiki article. In all instances where you are providing logs please ensure you followed the Gathering Logs wiki article to ensure your logs are what are needed for troubleshooting. Please review this comment and you can likely have your problem solved without needing to wait for a human. Mainly losing the ability to hardlink (TL DR a way for a file to exist in multiple places on the same file system while only consuming one file worth of space), or atomic move (TL DR instant file moves, rather than copy+delete) files while processing. There are many resources available to help you troubleshoot and help the community help you. We have set /tv and /downloads as optional paths, this is because it is the easiest way to get started.While easy to use, it has some drawbacks. until you locate the source of your problem If you find a suspiciously large folder, you can cd into it and run the command again, etc, etc. procġ60T don't need to worry about any of the "cannot read" or "cannot access" like this ones above, they don't matter in this instance. sudo du -h -d 1ĭu: cannot read directory './proc/2177/task/2177/net': Invalid argumentĭu: cannot read directory './proc/2177/net': Invalid argumentĭu: cannot access './proc/17058/task/17058/fd/3': No such file or directoryĭu: cannot access './proc/17058/task/17058/fdinfo/3': No such file or directoryĭu: cannot access './proc/17058/fd/4': No such file or directoryĭu: cannot access './proc/17058/fdinfo/4': No such file or directory 0. To start however, I would suggest the following to show what folder(s) are eating up all your space. It may not have anything to do with Sonarr. I would really suggest reaching out to something like r/linuxquestions for help with this.
0 kommentar(er)
