[Support] Linuxserver.io - Sonarr


Recommended Posts

what I would do (in conjunction with the question on the other thread)

 

SSH:

 

powerdown

 

After a couple of minutes if it still hasn't shutdown, then

 

ls /mnt

 

Either all the disks are still there, or only the cache drive is still there

 

Probably the docker.img is stopping a powerdown / shutdown.

umount /mnt/user/{WHATEVER}/docker.img

Hopefully the shutdown will now continue.

Link to comment

The path to the docker image....  ie: /mnt/user/docker.img or /mnt/user/appdata/docker.img, etc

 

To stop the array (at least pre 6.3.2:)

 

 

wget -qO /dev/null http://localhost:$(lsof -nPc emhttp | grep -Po 'TCP[^\d]*\K\d+')/update.htm?cmdStop=Stop

 

Not sure if they work with 6.3.3 and the csrf security though

Edited by Squid
Link to comment

Not suggesting this would have fixed the issue, or that it is the right way to go, but sometimes when my server refuses to shut down, I try and unmount each disk individually, and then try a powerdown again...

umount /dev/disk1
umount /dev/disk2
...

Sometimes it works and I get a clean shutdown, sometimes it doesn't :)

Link to comment

I am getting these errors in Sonarr, what exactly do they mean?

 

[Warn] ImportApprovedEpisodes: Couldn't import episode /data/completed/xxx.xxx.S02E08.720p.HDTV.x264-AVS/xxx.xxx.S02E08.720p.HDTV.x264-AVS.mkv

[v2.0.0.4689] System.IO.IOException: Win32 IO returned ERROR_GEN_FAILURE. Path:
at System.IO.File.Move (System.String sourceFileName, System.String destFileName) <0x2aeaa4bca5c0 + 0x002f0> in <filename unknown>:0
at NzbDrone.Common.Disk.DiskProviderBase.MoveFile (System.String source, System.String destination, Boolean overwrite) [0x000e3] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Disk\DiskProviderBase.cs:222
at NzbDrone.Common.Disk.DiskTransferService.TryMoveFileTransactional (System.String sourcePath, System.String targetPath, Int64 originalSize, DiskTransferVerificationMode verificationMode) [0x0008f] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Disk\DiskTransferService.cs:489
at NzbDrone.Common.Disk.DiskTransferService.TransferFile (System.String sourcePath, System.String targetPath, TransferMode mode, Boolean overwrite, DiskTransferVerificationMode verificationMode) [0x003c2] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Disk\DiskTransferService.cs:311
at NzbDrone.Common.Disk.DiskTransferService.TransferFile (System.String sourcePath, System.String targetPath, TransferMode mode, Boolean overwrite, Boolean verified) [0x0000e] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Disk\DiskTransferService.cs:195
at NzbDrone.Core.MediaFiles.EpisodeFileMovingService.TransferFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Tv.Series series, System.Collections.Generic.List`1 episodes, System.String destinationFilePath, TransferMode mode) [0x0012c] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\MediaFiles\EpisodeFileMovingService.cs:118
at NzbDrone.Core.MediaFiles.EpisodeFileMovingService.MoveEpisodeFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Parser.Model.LocalEpisode localEpisode) [0x0005e] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\MediaFiles\EpisodeFileMovingService.cs:80
at NzbDrone.Core.MediaFiles.UpgradeMediaFileService.UpgradeEpisodeFile (NzbDrone.Core.MediaFiles.EpisodeFile episodeFile, NzbDrone.Core.Parser.Model.LocalEpisode localEpisode, Boolean copyOnly) [0x00144] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\MediaFiles\UpgradeMediaFileService.cs:66
at NzbDrone.Core.MediaFiles.EpisodeImport.ImportApprovedEpisodes.Import (System.Collections.Generic.List`1 decisions, Boolean newDownload, NzbDrone.Core.Download.DownloadClientItem downloadClientItem, ImportMode importMode) [0x00277] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\MediaFiles\EpisodeImport\ImportApprovedEpisodes.cs:107

 

And I am seeing some errors in my log I've never seen before:

 

Apr 12 18:34:32 Tower kernel: docker0: port 1(veth2a2229d) entered disabled state
Apr 12 18:34:32 Tower kernel: vethbe9fc90: renamed from eth0
Apr 12 18:34:34 Tower kernel: docker0: port 1(veth2a2229d) entered disabled state
Apr 12 18:34:34 Tower kernel: device veth2a2229d left promiscuous mode
Apr 12 18:34:34 Tower kernel: docker0: port 1(veth2a2229d) entered disabled state
Apr 12 18:34:36 Tower kernel: docker0: port 1(veth3a54573) entered blocking state
Apr 12 18:34:36 Tower kernel: docker0: port 1(veth3a54573) entered disabled state
Apr 12 18:34:36 Tower kernel: device veth3a54573 entered promiscuous mode
Apr 12 18:34:36 Tower kernel: docker0: port 1(veth3a54573) entered blocking state
Apr 12 18:34:36 Tower kernel: docker0: port 1(veth3a54573) entered forwarding state
Apr 12 18:34:36 Tower kernel: docker0: port 1(veth3a54573) entered disabled state
Apr 12 18:34:41 Tower kernel: eth0: renamed from veth66ec916
Apr 12 18:34:41 Tower kernel: docker0: port 1(veth3a54573) entered blocking state
Apr 12 18:34:41 Tower kernel: docker0: port 1(veth3a54573) entered forwarding state
Apr 12 18:37:01 Tower kernel: CIFS VFS: Error -104 sending data on socket to server
Apr 12 18:37:01 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:37:01 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:37:01 Tower kernel: CIFS VFS: Error -104 sending data on socket to server
Apr 12 18:37:01 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:37:01 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:37:01 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:37:01 Tower kernel: CIFS VFS: Error -104 sending data on socket to server
Apr 12 18:37:01 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:37:01 Tower kernel: CIFS VFS: Error -104 sending data on socket to server
Apr 12 18:37:23 Tower kernel: veth96f98b7: renamed from eth0
Apr 12 18:37:23 Tower kernel: docker0: port 2(veth35c7b3c) entered disabled state
Apr 12 18:37:25 Tower kernel: docker0: port 2(veth35c7b3c) entered disabled state
Apr 12 18:37:25 Tower kernel: device veth35c7b3c left promiscuous mode
Apr 12 18:37:25 Tower kernel: docker0: port 2(veth35c7b3c) entered disabled state
Apr 12 18:37:31 Tower kernel: docker0: port 2(vethbe3d879) entered blocking state
Apr 12 18:37:31 Tower kernel: docker0: port 2(vethbe3d879) entered disabled state
Apr 12 18:37:31 Tower kernel: device vethbe3d879 entered promiscuous mode
Apr 12 18:37:31 Tower kernel: docker0: port 2(vethbe3d879) entered blocking state
Apr 12 18:37:31 Tower kernel: docker0: port 2(vethbe3d879) entered forwarding state
Apr 12 18:37:31 Tower kernel: docker0: port 2(vethbe3d879) entered disabled state
Apr 12 18:37:36 Tower kernel: eth0: renamed from veth4a83df2
Apr 12 18:37:36 Tower kernel: docker0: port 2(vethbe3d879) entered blocking state
Apr 12 18:37:36 Tower kernel: docker0: port 2(vethbe3d879) entered forwarding state
Apr 12 18:49:34 Tower kernel: cifs_vfs_err: 8548 callbacks suppressed
Apr 12 18:49:34 Tower kernel: CIFS VFS: Error -104 sending data on socket to server
Apr 12 18:49:34 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:49:34 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:49:34 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:49:34 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:49:34 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:49:34 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:49:34 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:49:34 Tower kernel: CIFS VFS: Error -32 sending data on socket to server
Apr 12 18:49:34 Tower kernel: CIFS VFS: Error -32 sending data on socket to server

 

 

Edited by ashman70
Link to comment

Hard to say. It's just saying it cannot import the episode. It should give a reason somewhere in the log. Check the activity page.

 

The CIFS error has to do with a samba share. The two might be related. Maybe it cannot access your mounted share where your files are stored. From the looks of things, I think you've got problems that go way beyond Sonarr.

Link to comment
13 hours ago, bobbintb said:

Hard to say. It's just saying it cannot import the episode. It should give a reason somewhere in the log. Check the activity page.

 

The CIFS error has to do with a samba share. The two might be related. Maybe it cannot access your mounted share where your files are stored. From the looks of things, I think you've got problems that go way beyond Sonarr.

 

Indeed, he's trying to work with "M:\ ..... " no way Sonarr on uNRAID is going to know wtf that is.

Link to comment

I am having tremendous problems with Sonnar. Its messing up when it copies episodes, it either doesn't copy the whole file, just some of it, or it gets stuck copying and I end up with a partial file copied. I no longer seem to be able to restart sonarr and this has led to two hard restarts of my server. Can someone give me a hand?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.