Sonarr not loading after drive failure

Help & Support
#1

Hi,
I run sonarr on Ubuntu 16.04. I have system drive 3 data drives, data1, 2 and 3. Drive 3 failed and is now not accessible. The drive has been physically replaced, however when I try and connect to sonarr now it always times out saying page cannot be displayed. Is this because it is looking for data on the failed drive?

I cannot open sonarr so can’t access the log files that way. I did find a logs DB and also the backup from 31 December, not sure if either of these for any use in troubleshooting?

Many thanks,
Ben

This e-mail has been composed using Dragon Dictate. Apologies for any typos / grammatical errors which have been missed.

#2

We’re going to need all the requested information (version, OS and debug logs), you can access to logs outside of Sonarr, it’s covered on the wiki page.

#3

Thanks for the reply. I’ve created a Drive folder with to logs, hope thats ok? https://drive.google.com/open?id=1HA_JlKPluOi7Y-B4Oc_bNtLW1OAT3b0C

running ubuntu 16.04 lts. Latest stable release of sonarr

thanks

#4

Looks like Sonarr is running just fine, has the port changed/been reset? You can look in Sonarr’s config file to confirm.

Beyond that try restarting Sonarr and check the logs for any errors after starting.

#5

Thanks. Nothing has changed with sonarr. What has changed is I lost one of my drives containing 3 TB of data. This drive has been replaced, but it is since that failure that these problems have occurred. The drive has the same name in Ubuntu and I can see sonarr has recreated the folder structure for all the missing programs.

Could it be because there are so many missing programs that sonarr is searching for that the server is under too much load?

Kind regards,
Ben

This e-mail has been composed using Dragon Dictate. Apologies for any typos / grammatical errors which have been missed.

#6

what url are you using to access sonarr? manually entered or bookmarked? and what happens when you enter/click on it?

like marcus said, it looks like its running ok and listening on the default port, 8989, so http://ubuntu_servername_or_ipaddress:8989 should work

19-1-21 17:16:05.0|Info|OwinHostController| http://*:8989/

youre not trying to use https?

#7

i’m not using HTTPS and it doesn’t matter whether I use localhost, server name, or IP address. It also doesn’t matter if I do it locally on the Ubuntu box or remotely from another machine on the same LAN. Either page just doesn’t load all the grey sonarr screen with the white dots appears and the page never properly loads

#8

if you havent already, do a full shutdown (not a restart) of your ubuntu machine then power it back on

if youre seeing the grey screen and dots then sonarr is active and the http server is running - its just barfing on something

#9

I have shutdown multiple times

#10

do you have a backup of your database? there should be scheduled ones in the /config/backups/scheduled folder at minimum that you could use

shut down sonarr, move just the files in the /config folder somewhere else, eg, to /config/backups/live, start sonarr - can you access it now (yes, it will be empty but if it works thats all that matters at this point)

if not then theres something wrong with your OS. what version of mono do you have? 4.x or 5.x? if 4.x can you upgrade it to 5.12 or 5.18 and see how that goes?

edit, checked your debug logs for mono

19-1-21 17:16:25.4|Debug|MonoVersionCheck|Mono version is 3.10 or better: 4.2.3

actually just upgrade mono first 4.2 is really old and will have TLS issues anyway

can you confirm your sonarr version as well, its not mentioned and i cant find it in the logs

#11

i Using Ubuntu 16.04 lts, i have found instructions on how to upgrade mono. Can you point to some instructions on how to shutdown sonarr a bit new to all this :slight_smile: ? Thanks for your help

#12

Thanks for all your help, upgrading mono seems to have done the job and I can get in now. I now have an issue with one of my Indexers not working but I will post about this separately if I can’t figure it out. Thanks again :slight_smile:

#13

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.