- #Sonarr says path is already configured as a root folder update
- #Sonarr says path is already configured as a root folder software
- #Sonarr says path is already configured as a root folder code
- #Sonarr says path is already configured as a root folder series
My setup has been the same for 1.5-years, ie: all folders, directories, drive letters, mappings…etc. Ok, allow me to clarify in case I’m not explaining it properly. If you wish to provide the paths Qbit is downloading into and the root folders you configured in sonarr, we can likely see the problem real quick. It’ll happen again unless you changed your paths. It is not a pestering notification: downloading into your library/root folder ALWAYS eventually causes problems. Sounds like you had an healthcheck error type of error that went away and then still had a healthcheck error type of warning. Issues and self investigation are expected in this branch. This branch is only recommended for advanced users. There is no guarantee that it will even run in some cases. This build may have not been used by us or other users yet.
#Sonarr says path is already configured as a root folder code
It is released as soon as code is committed and passes all automated tests. Let us see how long it goes without it complaining about it again, lol.
#Sonarr says path is already configured as a root folder update
The status changed from red to yellow on its own, I didn’t change anything as it has been the same every day since early 2020, and again, just like others have mentioned, I have been using the same path and storage locations for more than a year without any changes anywhere but the latest update decided to complain about it with red system errors and yellow warnings, so yes, a dev suddenly decided to add this pestering notification.īetter yet, where is the option to “turn it off”, “disable it”, or “ignore” that notification status?Įxited qbit, restarted sonarr, started qbit and the warning message is gone, so now there are no error messages or warning messages as of 22-minutes ago. In other words, the folder your download client downloads into or moves completed downloads to, should not be the same folder you have configured as your root/library/final media destination folder in the *arr application.Īpparently, that means that every version that is updated is making it buggy(er), hence, no point in constant daily updates unless it is absolutely and critically necessary since it is already buggy enough. New: Please note that this check looks at all defined/configured root folders added not only root folders currently in use. Old: Please note that this check looks at all defined/configured root folders added not only root folders currently in use. I’ve updated the wiki to cover that point you noted to clarify.
#Sonarr says path is already configured as a root folder series
Sounds like you have /Volumes/Media1/Complete Media/ either erroneously added a root folder or have a series or list pointing there.Ĭorrect setup would be downloads go to say /Volumes/Media1/Complete Media/ and library folder is /Volumes/Media1/Series ? Yellow statuses are system warnings…which are not great and should be corrected.ĭon’t do anything, wait till they fix this warning issue. Well red statuses are system errors…which are bad and should be corrected. I just noticed that the status message has now changed from a red system status to a yellow warning.
![sonarr says path is already configured as a root folder sonarr says path is already configured as a root folder](https://wiki.servarr.com/assets/radarr/radarr-filter-cutoff-wanted.png)
Without actual paths, I cannot comment on this, but my best guess is you’re misunderstanding the error (which again, is accurate). In my case, it is not actually the root folder but a 2nd subfolder with other subfolders to the actual system on the network where it is located, however, to sonarr, it is the root folder because it is mapped directly to that 2nd subfolder on the network, but irregardless, if this path/drive has been working properly for me and others then sonarr should not suddenly complain about it. However, if you wish to stay on outdated, buggy version…you do you. Not sure what you’re talking about? This is factually incorrect.
#Sonarr says path is already configured as a root folder software
No software or application requires updates every few hours on a daily basis, it’s overkill. Or trash’s their next update fixes this whining complaint from sonarr, I will be blocking any/all updates permanently.