i had sonarr running nicely on my DS114. everything was set up and working perfectly. decided to upgrade the DS114 to the newer DS115 model so just removed the hard drive and re-installed it in to the new enclosure.
Ran the initial setup tool which ran the data migration. It did ‘break’ a few packages - Mono and Sonarr being two of those, but it gave me the option to repair them (which seemed to be simply re-installing) which i did.
Whatever i tried from that point didn’t work. i uninstalled Sonarr and rebooted the drive and re-installed - nothing.
Uninstalled Sonarr AND Mono, rebooted and then re-installed both packages - nothing. Sonarr still refuses to run.
I even chose “run” and then went out for an hour as i read one other thread that says it takes a long time to start - nothing.
i can’t get any logs for you as it won’t even start on the first run to create the folders. it’s giving me “20150325-6” as the version number if that helps.
i’m also wondering if i need to maybe do a full destructive reset and fully re-install everything from scratch because it makes me wonder if the fact that the migration ‘broke’ sonarr, there might be some leftovers that i can’t see ?
This sounds more like a problem with the package, not Sonarr. Not sure if there is someone with a synology that can help out on this forum or if you’d be better off asking on a Synology related forum.
Considering you still have the file structure of the old NAS, it’s possible that some of the folders it needs are owned by users that no longer exist. It’s a long shot, but look in /tmp, Sonarr can put files there starting with “nzbdrone” and they need to be writable by the nzbdrone users. Look in /volume1/@appstore/nzbdrone/share/NzbDrone and check that the nzbdrone user has access to that folder, and double check the config folder you mentioned above and all the files in it as well.
If you don’t see anything weird there, try running this:
thanks for your replies. i checked the folders and they were all 755 permissions for the nzbdrone user, so that should be fine as far as access goes.
the nzbdrone user also exists in /etc/passwd as well.
i ran the nzbdrone.exe program as well and got this …
“The file /usr/local/mono/lib/mscorlib.dll is an invalid CIL image”
… which obviously suggests a problem with mono, but i’ve tried removing and re-installing it already - unless i have to specifically delete that dll file and only then do the remove and re-install ?
funnily enough, i’ve just actually tried installing the synology mono package instead of the SynoCommunity one just to see what happened
i then tried to re-install sonarr and it quite obviously told me that i needed to install mono from the synocommunity, so i did just that, while leaving the Synology version still installed and running. it told me it had installed so i went to the package page and saw “stopped” - but - i actually saw the URL there as well, which hadn’t happened up until now.
clicked on it and … it only frikkin’ ran
i’ve just stopped and uninstalled the Synology Mono and clicked on Sonarr again and it’s still running. really don’t have a clue what’s happened to fix the problem but, as it stands, it’s fixed and running.
the only thing i can think of is that maybe the official package provided a working version of that DLL file that seemed to be causing an error ???
I think both Mono packages install into a different directory, so that would be weird. Still, I’ll take a solution I don’t understand over no solution any day. Good to hear it’s fixed.
heh, the solutions you don’t understand and stumble in to are always the best
i’m very happy it’s fixed as it’s a fantastic package - i tried sickbeard and sickrage and they just didn’t really find anything. i installed sonarr and it just worked straight away and found and grabbed everything i wanted.
