Cannot update Radarr

[fdfytr]

Setup

Package Name: Radarr Package Version: 3.0.2.4552

NAS Model: DS220j NAS Architecture: rtd1296 (armv8) DSM version: 6.2.4-25556

Expected behavior

Trying to update to latest version

Actual behavior

Error (see log details)

Package log

|Error|CommandExecutor|Error occurred while executing task ApplicationUpdate

[v3.0.2.4552] System.IO.IOException: No space left on device at System.IO.FileStream.WriteNative(ReadOnlySpan1 source) at System.IO.FileStream.WriteSpan(ReadOnlySpan1 source) at System.IO.FileStream.Write(Byte[] array, Int32 offset, Int32 count) at ICSharpCode.SharpZipLib.Tar.TarInputStream.CopyEntryContents(Stream outputStream) at ICSharpCode.SharpZipLib.Tar.TarArchive.ExtractEntry(String destDir, TarEntry entry) at ICSharpCode.SharpZipLib.Tar.TarArchive.ExtractContents(String destinationDirectory) at NzbDrone.Common.ArchiveService.ExtractTgz(String compressedFile, String destination) in D:\a\1\s\src\NzbDrone.Common\ArchiveService.cs:line 110 at NzbDrone.Common.ArchiveService.Extract(String compressedFile, String destination) in D:\a\1\s\src\NzbDrone.Common\ArchiveService.cs:line 36 at NzbDrone.Core.Update.InstallUpdateService.InstallUpdate(UpdatePackage updatePackage) in D:\a\1\s\src\NzbDrone.Core\Update\InstallUpdateService.cs:line 133 at NzbDrone.Core.Update.InstallUpdateService.Execute(ApplicationUpdateCommand message) in D:\a\1\s\src\NzbDrone.Core\Update\InstallUpdateService.cs:line 275 at NzbDrone.Core.Messaging.Commands.CommandExecutor.ExecuteCommand[TCommand](TCommand command, CommandModel commandModel) in D:\a\1\s\src\NzbDrone.Core\Messaging\Commands\CommandExecutor.cs:line 118 at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid3[T0,T1,T2](CallSite site, T0 arg0, T1 arg1, T2 arg2) at NzbDrone.Core.Messaging.Commands.CommandExecutor.ExecuteCommands() in D:\a\1\s\src\NzbDrone.Core\Messaging\Commands\CommandExecutor.cs:line 44

---

Sorry guys total newbie with NAS, looks as similar error to Jackett. Is it something about DS220j low specs?? I have plenty space left on HDD -1.6GB. Thank you

[publicarray]

What file system is your NAS formatted with? btrfs? You can run sudo btrfs fi usage / to look at the unallocated space.

[fdfytr]

ext4

On Sat, 31 Jul 2021 at 13:52, Sebastian Schmidt @.***> wrote:

What file system is your NAS formatted with? btrfs?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/SynoCommunity/spksrc/issues/4755#issuecomment-890343994, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOUCQ2M3Y62VPEVOOKUY3GTT2PWY5ANCNFSM5BJ7V45Q .

[publicarray]

Even with 1.6GB I still think low disk space is to blame. You don't need to get to 0GBs left to start seeing odd behaviour due to low free disk space. Modern OSs need space for swap, temp files, log files and when extracting files etc. During installation, it is not uncommon to have 3 copies of the files in various stages i.e 3 times the size, (the downloaded package file, extracted package file, and the old package) until the installation is completed/cleaned up.

From the log, Extracting the files is what failed, due to not enough disk space.

IIRC Synology uses multiple partitions (a system partition). So the free space you are seeing is probably reserved for the system.

Did you get a low disk warning?

[publicarray]

My recommendation is to install more disk space, e.g. add an external drive to move some stuff off the NAS until you can extend the storage of the NAS itself.

[fdfytr]

I put OMV on pi 4 and run jackett sonarr via docker. Works like a charm. Struggling with getting NFS to work from synology to pi now :) I guess it is DS220j to blame...

On Sat, 31 Jul 2021 at 23:08, Sebastian Schmidt @.***> wrote:

My recommendation is to install more disk space, e.g. add an external drive to move some stuff off the NAS until you extend the storage of the NAS itself.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/SynoCommunity/spksrc/issues/4755#issuecomment-890409296, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOUCQ2OVRNIC4RWHHCGEM7DT2RX6TANCNFSM5BJ7V45Q .

[BenjV]

@fdfytr Maybe the space on the system volume is to low. Log into the commandline and look with the df command to see it that is the case.

[hgy59]

4621 might help.

1. stop sonarr to update radarr
2. define TMPDIR to point to a folder that is large enough

[fdfytr]

@fdfytr Maybe the space on the system volume is to low. Log into the commandline and look with the df command to see it that is the case.

I ran sonarr via docker with OMV5 at pi4 and works smoothly Now fighting to make radarr work via portainer :)