Hi, after link database of Radarr to RAM I make connection in Radarr webUI and in Test I have error:
Must not be a descendant of '/boot'.
How to fix that?
Guide: https://dietpi.com/forum/t/dietpi-arr-to-ram-link-sonarr-radarr-lidarr-database-files-to-ram/3120/1
Regards,
Przemko
Hi,
looks like Radarr V3 changed stuff and did not except scripts located at /boot
MichaIng Maybe something to look into. As well I don’t see an option to set arguments like 2 radarr anymore.
Ohh, that is bad. Why not leaving that decision to the administrator 
. This was a backport from Sonarr, I guess Sonarr V3 which hence will be affected as well: https://github.com/Radarr/Radarr/blame/bb721272ca1ef4336fcc159563a33794345a185b/src/NzbDrone.Core/Notifications/CustomScript/CustomScript.cs#L141-L147
Ugly workaround:
echo -e '#!/bin/dash\nexec /boot/dietpi/misc/dietpi-arr_to_RAM 2 radarr' > /var/lib/dietpi/dietpi-software/radarr_backup_database.sh
chmod +x /var/lib/dietpi/dietpi-software/radarr_backup_database.sh
Then adding that script instead.
Also, the radarr DB is now called radarr.db not nzbdrone.db so
dietpi-arr_to_RAM 1 radarr
will not create a /tmp link
Yeah since Radarr V3 thinks are brocken as quite a lot of thinks changed on Radarr side 
I’ll implement Sonarr v3 migration + Radarr v3 supported as good as possible with the next DietPi release. If it stays that way that arguments are not possible anymore for those event hooks, we’ll pre-create a backup update script within the Sonarr/Radarr data directory to invoke.
for sonarr v3 fix typo in dietpi-arr_to_RAM.sh from
/boot/dietpi/misc/dietpi-arr_to_RAN 2 sonarr
to
/boot/dietpi/misc/dietpi-arr_to_RAM 2 sonarr