ashman70

So yes I have a Samba share mounted to another server, the idea is that Sonarr will send a download request to sabNZB who will in turn download the file then it will get copied to the Samba share. It was working ok until Sonarr started screwing up and I had two hard resets of my server, then I removed the Sonarr docker and added it back and now its messing up again.

Here is a screen shot of the docker settings. At the moment I can't bring up the web ui of the docker, it won't load, it just spins and spins trying to load.

How do I post them internal to Sonarr?

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?

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>:0at 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:222at 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:489at 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:311at 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:195at 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:118at 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:80at 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:66at 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

Thank you for your patience and I apologize for being slow at understanding. I believe I have it working now, thank you again.

Ok here are my dockers, where have I gone wrong?

I am seeing these errors in Sonarr not sure where its getting this path from. [Error] DownloadedEpisodesImportService: Import failed, path does not exist or is not accessible by Sonarr: /data/completed/ I am going to post screen shots of my dockers because I believe everything is correct.

How does it work? Does Sonarr push the file to the destination I provide?

I had one of the containers spelled wrong in the Sonarr docker, I've corrected that and restarted both SAB and Sonarr but it doesn't seem to be copying the episodes over.

Squid I need your help again, I had to delete the Sonarr docker because it wasn't working properly and affecting my server. I thought I took screen shots of all the settings but evidently I did not, and now episodes that sabNZB downloads are not being automatically copied to my other server as they were before.

Well I had to do a hard shut down. Server is backup now, I am going to let the parity check run just in case it finds any inconsistencies. I have deleted and re added the Sonarr docker, hopefully that will fix whatever was wrong with it. Thanks for everyones help.

Well its been a few minutes already and the server hasn't shut off. I have a feeling I am going to have to do a hard reset again......:-( and I really don't want to have to run a parity check as that takes a day and a half.

I executed a powerdown command without the -r. What does the -r switch do?

The docker img is already unmounted. If I do a powerdown -r will that attempt to unmount the array?

Right but when I execute the command ls /mnt all the drives come up green indicating to me that the array is still mounted. I want to unmount it so I can do a graceful reboot.

I am trying to take the array offline gracefully so i can reboot. Last night I did a hard reset and I want to avoid doing that if at all possible.

Wondering if someone can advise me on next steps.

I am however able to SSH into the server successfully so that is something. What other commands can I try at this point? And the array is still online. The docker image has unmounted though.

Tried that command and got this: grep: \k us not followed by a braced, angle-bracketed, or quoted name. And now I am getting no response from the command prompt...lol just a blinky cursor.

What do I put in place pf {WHATEVER} if I try to unmount the docker image?

Now I am trying to take the array offline and that is timing out, ugghhhhh. Is there a command to unmount the array or do you have to do it one disk at a time?

So now I have decided to remove the docker, but its stuck on removal.....not sure what else I can do but wait. Are there any commands I can run in the CLI to either remove the docker or do something?

My Sonarr started acting strange yesterday, and then after my server became unresponsive and I had to hard reset it, Sonarr was doing weird things like saying it was downloading a file that was 1.6GB but when it moved that file to a share it was half the size. I messed around with quality settings and after manually re downloading some episodes two or three times it was doing it properly. Now this morning I went to refresh the calendar and its taking forever to respond. I tried to stop the docker and that is not working again. What can I do? I can't launch the docker either, so I can't stop it, reload it or launch it at this point.

I remember having to do this years ago with Dell Perc 5i cards, didn't know it was an issue with other HBA's