It seems that the version we download from dietpi-software uses v3, which relies on mono and is an exe.
V4 has been out a while but doesn’t download from the dietpi-software library
I’ve tried sudo dietpi-software install 144
I’m on DietPi v9.8.0
correct, we did not switched to v4 yet. Something still on the agenda.
Ok, I have a failure from the last few days now with Sonarr, it no longer seems to have permission with the /mnt/dietpi_user/sonarr directory, even though it has the following folder properties:
drwxr-xr-x 3 sonarr dietpi 4096 Oct 18 18:39 sonarr
Do you have an error message to share?
This is from a fresh install, other arr services are running well, and during the install script I see the following in the log:
[ OK ] DietPi-Software | APT install sonarr mediainfo
[ OK ] DietPi-Software | systemctl stop sonarr
[ OK ] DietPi-Software | mkdir -p /mnt/dietpi_userdata/sonarr
[ OK ] DietPi-Software | usermod -g dietpi -d /mnt/dietpi_userdata/sonarr -s /usr/sbin/nologin sonarr
[ OK ] DietPi-Software | rm -Rf /mnt/dietpi_userdata/sonarr/logs*
[ OK ] DietPi-Software | ln -s /var/log/sonarr /mnt/dietpi_userdata/sonarr/logs
[ OK ] DietPi-Software | ln -s /var/log/sonarr/logs.db /mnt/dietpi_userdata/sonarr/logs.db
[ OK ] DietPi-Software | ln -s /var/log/sonarr/logs.db-shm /mnt/dietpi_userdata/sonarr/logs.db-shm
[ OK ] DietPi-Software | ln -s /var/log/sonarr/logs.db-wal /mnt/dietpi_userdata/sonarr/logs.db-wal
[ OK ] DietPi-Software | chown -R sonarr:dietpi /mnt/dietpi_userdata/sonarr /usr/lib/sonarr
service status
dietpi@DietPi:~$ sudo systemctl status sonarr
× sonarr.service
Loaded: not-found (Reason: Unit sonarr.service not found.)
Active: failed (Result: signal) since Fri 2024-10-18 18:31:45 BST; 1h 38min ago
Duration: 11.871s
Main PID: 21438 (code=killed, signal=ABRT)
CPU: 10.846s
Oct 18 18:31:45 DietPi systemd[1]: sonarr.service: Consumed 10.846s CPU time.
Oct 18 18:31:45 DietPi systemd[1]: sonarr.service: Scheduled restart job, restart counter is at 4.
Oct 18 18:31:45 DietPi systemd[1]: Stopped sonarr.service - Sonarr (DietPi).
Oct 18 18:31:45 DietPi systemd[1]: sonarr.service: Consumed 10.846s CPU time.
Oct 18 18:31:45 DietPi systemd[1]: sonarr.service: Start request repeated too quickly.
Oct 18 18:31:45 DietPi systemd[1]: sonarr.service: Failed with result 'signal'.
Oct 18 18:31:45 DietPi systemd[1]: Failed to start sonarr.service - Sonarr (DietPi).
Running from the terminal:
dietpi@DietPi:~$ /usr/bin/mono -O=-aot /usr/lib/sonarr/bin/Sonarr.exe -nobrowser -data=/mnt/dietpi_userdata/sonarr
[Info] Bootstrap: Starting Sonarr - /usr/lib/sonarr/bin/Sonarr.exe - Version 3.0.10.1566
[Info] AppFolderInfo: Data directory is being overridden to [/mnt/dietpi_userdata/sonarr]
[Trace] DiskProviderBase: Directory '/mnt/dietpi_userdata/sonarr' isn't writable. Access to the path "/mnt/dietpi_userdata/sonarr/sonarr_write_test.txt" is denied.
[Fatal] ConsoleApp: EPIC FAIL!
[v3.0.10.1566] NzbDrone.Common.Exceptions.SonarrStartupException: Sonarr failed to start: AppFolder /mnt/dietpi_userdata/sonarr is not writable
at NzbDrone.Common.EnvironmentInfo.AppFolderFactory.Register () [0x00081] in <7c4b50a9ebef4330b1391d4929a00110>:0
at NzbDrone.Host.Bootstrap.Start (NzbDrone.Common.EnvironmentInfo.StartupContext startupContext, NzbDrone.Host.IUserAlert userAlert, System.Action`1[T] startCallback) [0x00064] in <be265798898444b893f12d91e86839d4>:0
at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00036] in <84a7347b1752473980a5d741cffcf57a>:0
Press enter to exit...
Non-recoverable failure, waiting for user intervention...
be careful with mixing things like user, command and permissions.
On terminal you tried to start sonarr as user dietpi. Of course this will give permission issues because user dietpi is not allowed to write into sonarr directory
You see, write bit has been set for sonarr user only, which is fine.
seems like service definition is missing
can you share the whole log for the service
journalctl -u sonarr
Here’s what I could get in the output, let me know if it’s not good enough
This is from a fresh boot
hmm something seems to be wrong using mono. If you are in mood, we could try to switch to Sonarr v4.
I am very in the mood 
Radar v4 seems to be running well, so I’m hopefully optimistic.
first step do a full system backup using dietpi-backup
Hope following will work
First let’s do a full system backup
dietpi-backup
once done we can start migration to Sonarr v4
cd /tmp/
wget https://raw.githubusercontent.com/Sonarr/Sonarr/develop/distribution/debian/install.sh
chmod +x install.sh
on the installer, we need to adjust 2 line. You can use nano or any other text editor
around line 35 set
app_prereq="curl sqlite3 wget libicu72"
around line 43 set
datadir="/mnt/dietpi_userdata/$app/"
save and exit the file. Ready to start 
./install.sh
following input needed
user = sonarr
group = dietpi
Continue if you are ok. Script should complete in 1-2 minutes. Once done, some cleanup steps needed
systemctl stop sonarr.service
dietpi-software uninstall 150
apt remove sonarr
rm /etc/apt/sources.list.d/sonarr.list
rm /etc/apt/trusted.gpg.d/dietpi-sonarr.gpg
rm Sonarr.main* install.sh
systemctl start sonarr.service
Now you should be able to reach Sonarr as usuall.
!!! This might not be working on ARMv6 !!!
4 Likes
UPDATE: OK seems to work, I couldn’t run the G_ADP sonar command, not sure what you wanted there, to set an environment variable?
The web server is running now, and I have to set it up again, I made a backup of my sonarr folder so will try and copy that across and see if it keeps my data.
Oh and running dietpi-backup took ages and failed on me, I didn’t quite see what the issue was, but thought what the hell, let’s go.
Running the backup is going to take about an hour, I’ll update this post once it’s complete and I’ve run the rest of the commands - which will be later today.
1 Like
Can’t chip in but great to see movement on this topic 
Fingers crossed
This will purge the old sonarr package. But there was a typo (missing r) corrected above
Tried the above but error with
Unable to locate package libicu72
I installed this manually, I noticed it as an error with V3 anyway.
Following the above instructions from @Joulinar V4 has installed fine, and seems to be working for me so far.
Package name depends on your Debian version. What Debian version you are on?
Just found out I am still on Bullseye. There is no package for Bullseye. Should I use libicu67?
There it is libicu67 Debian -- Details of package libicu67 in bullseye