Zer0Nin3r

Members
  • Posts

    152
  • Joined

  • Last visited

Converted

  • Personal Text
    We're looking down on Wayne's basement. Only that's not Wayne's basement. Isn't that weird?

Recent Profile Visitors

1327 profile views

Zer0Nin3r's Achievements

Apprentice

Apprentice (3/14)

23

Reputation

  1. Looking to modify the MTU size so the excruciatingly slow download speeds will be fixed due to ISP constraints. (5G Internet) Adjusting the MTU within Unraid's settings to 1350 has resolved the VPN issues on my other clients with regards to this particular ISP. I am able to set the MTU at the Unraid system level by: Settings > Network Settings > Desired MTU > 1350 I tried the following without any luck: Key 5 - Container Variable: VPN_OPTIONS --fragment 1350 --mssfix --fragment 1350 --mssfix 1350 Setting the 'mssfix 1350' parameter in the OpenVPN configuration file. I can see in the logs that @binhex sets the MTU in the script and I tried to find the script to adjust, but am unable to; it's not in the Appdata share...that's for sure. OPTIONS IMPORT: adjusting link_mtu to 1624 DEBG 'start-script' stdout output: TUN/TAP device tun0 opened net_iface_mtu_set: mtu 1500 for tun0 net_iface_up: set tun0 up Any ideas on how I can resolve this issue? Thanks in advance!
  2. I recommend that you don't uninstall @dee31797's Handbrake docker until we can get an answer from @Djoss whether it will be supported in the future. I'm with you though. Handbrake with NVENC support is my secondary docker application. If you are automating your encodes, you may want to check out Unmanic as that will support hevc-nvenc.
  3. Quite the DVR collection you have there! ๐Ÿ† I have my server setup to use GPU HEVC encoding (speed at the cost of quality/artifacts). Nothing wrong with libx265; better quality โ€” longer encode times and more power usage as it relies on CPU exclusively. As far as your episode failing it could be a bad h.264 encode or a small portion of the file is corrupted. This has happened to me before. Throwing those problematic videos into Handbrake allowed me to re-encode those videos into H.265. Subtitles. Subtitles would cause video encodes to fail 98% of the time with Unmanic. This is being worked on and improved upon in more recent times. /tmp. Is your transcoding cache using the /tmp directory? I suspect that in my case, either my gaming VM is not releasing the GPU fully and that's what is causing the crashes with Unmanic OR I'm running out of RAM memory when encoding large video files. Either way, a reboot of the server has worked for me โ€” not sure why though. **Update** I don't think RAM is a factor in my case at this point in time as 30 minute video files are failing now. I've seen it before though.
  4. Just noticed this happened when checking for Docker updates today. Should we uninstall this docker then?
  5. Agreed. I've been having issues with all encodes failing. Looking at the portion of your log you posted I decided to take a look at my Unraid system log and found this to be happening over and over in real time: Jul 24 23:30:43 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Jul 24 23:30:43 Tower kernel: caller _nv000708rm+0x1af/0x200 [nvidia] mapping multiple BARs Jul 24 23:30:44 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Jul 24 23:30:44 Tower kernel: caller _nv000708rm+0x1af/0x200 [nvidia] mapping multiple BARs Jul 24 23:30:46 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] I had a feeling that there was some sort of conflict over the GPU wherein Unmanic is failing. Although, I don't have any issues using the same GPU for my gaming VM. And I always stop Unmanic before launching my gaming VM...so something is happening when I re-launch Unmanic and it cannot interface with the GPU for some reason. I have rebooted the Unraid server in the past and I feel that this clears up the issue when it does occur. I wonder if using the Dynamix S3 Sleep is causing an issue...but I didn't really have these kind of encoding failures until this year. Will edit this post if/when I learn more. **Update** Found this in one of the failed encodes: [hevc_nvenc @ 0x560418cb3d40] dl_fn->cuda_dl->cuInit(0) failed -> CUDA_ERROR_UNKNOWN: unknown error Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height Conversion failed! Also, Unmanic is working again after rebooting the server.
  6. Do we have to input share specific folders? Would stopping at '/mnt/user/' allow the spotlight flag to be recursive? This is what the default looks like: #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end
  7. ๐Ÿ˜ณ Gadzooks! Now I know why Google is moving away from unlimited cloud storage even for universities. ๐Ÿ˜œ
  8. This feature has been requested many times over and I believe is on the roadmap. 1) Do you have Unmanic set to include closed captions? If so, try turning that off. There were issues with past releases wherein some of the CC embedded in a video file would throw an error in FFMPEG and then Unmanic would continue to keep trying those files. But I see that this has been fixed now: "Removes the subtitle stream from the container. This is useful if you intend to supply your own subtitles for your library WARNING: Unsupported subtitles will always be removed" 2) If you set Unmanic so that it is not including CCs, then there is something wrong with the video file. For this I turn to Handbrake (and there is a docker version of Handbrake that supports GPU encoding.) I have yet to run into a problematic video file that Handbrake couldn't handle. Try that. Also, don't have Unmanic NVENC and Handbrake NVENC trying to access the same GPU at the same time or you're asking for trouble.
  9. I just noticed that this was happening to me now that I have upgraded to Unraid 6.9. It's a real bummer that we have to do a work around in the meantime. My only hesitancy with this workaround is that I know I'll forget to remove the added code instructions once this resolves itself. I just submitted a feedback/bug report from within Unraid's dashboard and linked back to this post in the bug report. Hopefully the Unraid team pushes out an official patch. ๐Ÿคž๐Ÿผ
  10. Yeah, I didn't get the November 2020 memo either, LoL. So, is it cool that we skip trying to roll back the modified Nvidia Unraid build on 6.8.3 and simply back up our USB thumb drive and upgrade to v.6.9? Looks like 6.9 went live since the time of your post. Thanks in advance for the advice! **Update** Never mind! Found the answer. ๐Ÿ˜…
  11. It is dependent on your GPU and how many H.265 encoding threads it can handle. Nvidia has a break down in one of their developer sections with a grid that shows all the capabilities of the various GPUs which will show you how many streams your GPU can handle. I have a GTX 1060 that I use with Unmanic and I set it to two workers as I noticed my encodes for a large queue finished faster than with three workers believe it or not.
  12. And I have the opposite problem. ๐Ÿ˜† I can back up, but cannot restore from the SMB Unraid Time Machine share.
  13. I'm able to do backups to the Unraid Time Machine share, but now that I want to migrate over to a new system, I can connect to the server in Migration Assistant from a fresh install and that's about it. None of the time machine backups show up in the next screen after connecting to the server via SMB. It's been hit or miss as I remember a couple of months ago when doing a restore, I was able to see the Time Machine backups in the Migration Assistant, but I wasn't able to restore; I had to use the secondary backup drive. I know that this doesn't not really help anyone, but at least it goes to show that Time Machine backups over SMB needs some TLC from the Unraid team.
  14. Use the HDMI dongle and don't use Microsoft Remote Desktop/RDP. Instead use Parsec. This way you can still hear the audio passed through to your VR headset. You will also want to select your VR audio as the output in Windows' sound settings. Hope this helps. Or if you fixed it already @adnix42, share with us your steps to get VR + sound to work and mark your thread as [SOLVED].
  15. Have you tried a HDMI dongle? I want to say that the GPU drivers will want to detect a physical display. If that's the case the HDMI dongle that mimics an actual display may be what you are looking for. I game AAA titles in Windows 10 with GPU pass-through no problem. For that to work, I need to have a HDMI dongle. Also, do you have a second GPU for Unraid to use? You need to have a second GPU if you are trying to pass-through your primary GPU in the first slot.