Same problem as OP.
Pi 4 with SSD formatted in ext4 (not the problem) exporting completed files to Windows server.
SMB shares set up through dietpi config.
Using Sonarr or Radarr to export/rename files to SMB shares, they get a “failed to import” error, and a ~partial file is located in the destination folder. Sonarr/Radarr are able to create the destination folder on the SMB share.
I had the same problem on a Sonarr install that I did the manual way (raspbian+mono+sonarr v2.x) until I installed mono v3, which uses Mono v5 instead of v6.
I LOVE how easy installing everything with DietPi is (fresh install), except that everything is installed with Mono v6, which is broken for me.
I have uninstalled Mono, but in order to get it completely gone, I have to:
sudo apt-get --purge remove mono-*
sudo rm -rf /etc/mono
sudo rm -rf /usr/lib/mono
sudo apt --purge autoremove && sudo apt clean
I can then install Mono v5.20 with a revised sources.list. If I don’t do the above, the Mono install fails because it’s looking for v6 in the v5 repo that I’ve specified.
UNFORTUNATELY, all these steps completely bork the sonarr install, and I’m stuck reinstalling it. Probably Radarr as well, I haven’t checked. If I manually reinstall Sonarr rebuilding the repository and using apt-get to install, I have no idea what settings (user,group,permissions) that DietPi used originally to install.
If I reinstall through DietPi console, it overwrites the Mono v5 install with v6 and I’m back to square one.
Just to be clear, all the moving parts were functioning properly, from Radarr reading my library on SMB share, adding movie, finding and sending nzb to SABnzbd, downloading, right up to the Mono v6 refusal to export the file to SMB share.
Is there a way to alter the DietPi install scripts to not overwrite the Mono source.list? As it stands, it kills the original one with the v5 repo and creates an new one with just the current stable version repo.
So very frustrated by this…