I’ve got the new health warning that my root folder doesn’t exist (which is accurate - I rearranged a bit ago), but I can’t find where to set the root folder now . . . Is it currently only available by initial set up and the config file?
The warning means one of your series is at a non-existent path.
You can add a root folder when adding existing series (and delete them from there are well).
Ah, ok. I’ll look thru the series and see who’s kicking it up.
Discovered that I had the same issue. Found the culprit. Tnx markus101! As a user for a few months by now, I love the program, donated!
I am now getting this warning on my system, but no show is pointing to a non-existent dir. I double checked with the series editor and all my shows are pointing to my 2 tv folders. It would be helpful if there was more info on why this error is appearing…
I have 2 drives D and E and each has a TV folder. Shows are still downloading and playing fine, yet NZBDRone tells me that my roots folders D:\TV and E:\TV are missing, they obviously aren’t and even show up right below in the disk space section.
Is this possibly related to not having “create empty series folders” checked? There may be a few shows I added that haven’t aired yet and may not have folders, but this really shouldn’t trip on error if that’s the case. This is the only reason I can see this error being displayed and would really like to suppress the big red 1 on my system icon 
@Stryk3r I’m not able to reproduce it showing missing when the series folder has not yet been created.
If you remove one of those root folders (which won’t remove any shows) and try to re-add it, does it work? You can add/remove them via Add Series -> Import Existing Series from Disk
Are D:\ and E:\ local drives?
Hi Markus,
Yes D and E are local USB drives They both show up in the system tab and they both have a TV folder in the root of the each drive.
Also E is a new drive and only has about 5 shows on it and I can see they all have folders, and it’s been downloading new shows to this drive all day yet it’s still included in this error. I did try what you suggested and removed and readded the paths, but it didn’t change anything.
All my series paths show up under the series editor for every show, I really don’t know why it thinks these folders are missing as they are not.
@Stryk3r could you try restarting drone? It will check for the missing disks and start up, but then not again for 6 hours, if for some reason the drives weren’t available on start or on the check it would show the error until it saw them.
In either event 6 hours between checks isn’t very ideal, so I’ll look at make that shorter.
Maybe make that time between checks configurable? That way ppl who use systems w/ disks they let spin down aren’t spinning up every X minutes just for that check?
Shorter was likely the wrong way to word it, probably going to make it action based, like some of the other checks, download client check is run at startup, on a schedule and whenever settings are changed.
Fair point though.
I have restarted my computer several time before I even came here (I am an IT person by trade so I do these things before I ask for help) and this was 2 days ago when it all started after the last update. The next morning after the update, the error was gone, but then for some reason it came back later in the day. This morning the error is now gone again, and as of now 1:34pm EST it is not showing any errors BUT I have not changed anything in my configuration so I’m not sure why this even happened.(the error was just very distracting as I am OCD about these things and don’t like errors in my config).
Maybe you could also include some info in the logs or something about this on startup? I didn’t see anything listed in the logs about my config error, just the big red 1 on my system icon. I really don’t know what changed maybe I just had to wait the 6 hours after re-adding them through “add series” for the error to update.
I will reply back should anything change in the meantime.
My theory is the drives were slow to mount via USB and drone had already started and looked for them, so they were reported as missing. That was the reason for wanting you to restart drone, not the computer.
Not really anything more information to log, it couldn’t find them so it displayed the error, we could log the exact same thing, but it wouldn’t give any more information.
By the time it checked again they were mounted properly and all was well, the test for removing and re-adding was to make sure drone could see them and it wasn’t something else.
I just rebooted my computer and the error has returned. So it does seem that it is not waiting long enough to detect my drives.
I just restarted drone only, and the error went away. So your assumption seems correct, maybe you can add an optional setting to increase the delay at startup for checking for the paths? It really must only be a matter of seconds as my PC boots up within 30 secs.
Delaying the check would delay the startup process of drone, not something we’re going to do. You could try setting the Service in Windows to Delayed which will start it later on, or try running via the Startup folder instead.