Sonarr Home Drive issues, will no show in HTTP

chrischambers · June 25, 2018, 4:57pm

Sonarr version (exact version) 2.0.0.5225:
Mono version (if Sonarr is not running on Windows) 3.10.0:
Raspberry 3:
Debug logs:
happy to supply once Sonarr works.

Description of issue:
I am not sure if the two are related but the first issue I am getting is that I am getting a “This page can’t be displayed” message every time I try to log into my Sonarr via the Http://IP Address:8989.
if I reboot my raspberry then I am able to get in for about 5 mins then I get the same error.

the second error I am getting is that for some reason, the Sonarr application is reporting that it can’t find the ‘Missing root folder: /home/pi/tank/TV_Shows’ folders for the TV shows, but I have added a new TV show and this sees the drive with no issues. I am also able to FTP into the Raspberry via Putty and I can see the mount home drive with no issues.

I have other applications running on the Raspberry ’ Deluge ’ is is working fine, and also VPN.

my current storage is
4.0G    /media/pi/ExtStorage/complete
7.4G    /media/pi/ExtStorage/downloading
12G     total

pi@raspberrypi:~ $ df -h
Filesystem           Size  Used Avail Use% Mounted on
/dev/root            7.2G  4.9G  2.1G  71% /
devtmpfs             481M     0  481M   0% /dev
tmpfs                486M  4.0K  486M   1% /dev/shm
tmpfs                486M  6.7M  479M   2% /run
tmpfs                5.0M  4.0K  5.0M   1% /run/lock
tmpfs                486M     0  486M   0% /sys/fs/cgroup
/dev/sda1             30G   12G   17G  41% /media
/dev/mmcblk0p1        63M   22M   42M  35% /boot
tmpfs                 98M     0   98M   0% /run/user/1000
//192.168.0.7/media   11T  6.1T  4.6T  57% /home/pi/tank

pi@raspberrypi:~ $ sudo fdisk -l

Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mmcblk0: 7.4 GiB, 7948206080 bytes, 15523840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x4ce00e54

Device         Boot  Start      End  Sectors  Size Id Type
/dev/mmcblk0p1        8192   137215   129024   63M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      137216 15523839 15386624  7.3G 83 Linux

Disk /dev/sda: 29.8 GiB, 32019316736 bytes, 62537728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc3072e18

Device     Boot Start      End  Sectors  Size Id Type
/dev/sda1          32 62537727 62537696 29.8G  7 HPFS/NTFS/exFAT

markus101 · June 26, 2018, 8:32pm

Upgrade mono, 4.6 or higher.

Beyond that you’re going to need to get trace logs of the issue. You’ll want to redirect standard output and error to a file to capture any crashes with mono.

chrischambers · June 29, 2018, 3:39pm

I have been searching the web for a upgrade path which works and I can’t find a clean step by step procedure on how:

to remove the old version
then install the new version

can you please advice or point me to a good documentation which I am able to follow.

chrischambers · July 14, 2018, 2:06pm

I. I have looked for a path to upgrade for the past 2 weeks and I can’t find a way, can you please advice

markus101 · July 14, 2018, 5:43pm

Pretty much the same way you installed it to begin with, add the apt repository and install/upgrade mono.

The has general steps on installing mono and Sonarr.

chrischambers · July 15, 2018, 8:04am

Hi. sorry but I think you have miss understood me. I was referring to a repository with a stable version of Mono 4.* or later, as I have looked around and I can’t find a repository which contents one.

I know how to connect to a repository, using the wget and then using the apt command but it is just the repository I am having issues with.

markus101 · July 15, 2018, 10:28pm

Not sure if mono publishes ARM packages, if so: http://www.mono-project.com/download/stable/#download-lin if not, not sure.

system · September 13, 2018, 10:28pm

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