Jump to content

JasonM

Members
  • Content Count

    34
  • Joined

  • Last visited

Community Reputation

2 Neutral

About JasonM

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Is it your observation from the logs that Mover is the problem? I changed it to monthly and will see how things look in the morning.
  2. Yes, I do have cache drives, but I only use cache-only shares. There is nothing for mover to move. I wish there were a way to disable mover completely, but there is no readily apparent way to do so. Mover is set for 1AM. I have scheduled tasks spread out enough such that they should not conflict with each other: 1AM Mover 2AM Auto update plugins 3AM Auto update containers 4AM CA backup 5AM SSD TRIM
  3. I've been trying to isolate this issue for a while. It has survived hardware changes and complete USB rebuild. At some point overnight, the system becomes unresponsive. Dockers and VMs cease to operate. The web UI is sometimes available, and when it is, shows 2-3 CPUs pegged at 100%. Interacting with the web UI in this state works for a few navigation clicks before completely locking up. On other mornings, the web UI won't load at all. In all cases, a hard reboot is required. The server runs all day without issues. In an attempt to get more data, I installed a user script that tails the syslog onto the flash drive since I'm not able to get a log at time of crash. Regular diags as well as this log are attached. Around line 460, the system seems to enter an endless loop. On one occasion, I noticed a strange message about CA Backup in my browser status bar, of which I took a screen shot. All three files are attached. Any help nailing down this issue is greatly appreciated. unraid-diagnostics-20190911-1207.zip syslog-2019-09-09_0637.txt
  4. Thanks for the shout out. Helping each other is what this community is all about. Also, I see above that you're passing your keyboard and mouse from the host to the VM. Since you're handing off the USB controller from your GPU, you can connect a USB hub to that USB-C port on the back of the GPU, and then plug the input devices into that. This way, you don't have to pass them through at all, and you also get true USB Plug-and-play support in windows. You can connect flash drives and the like without unRAID even knowing they're there. I do this with a dedicated PCI USB card, but it works with that port on the back of the GPU just as well.
  5. I had this issue also. The workaround (although it's not really a "workaround" as much as it is just doing it a little differently) is to, instead of stubbing the NVIDIA USB and serial controllers, add them as two hostdev blocks to the VM XML for the two devices. This will have the same result with the two devices appearing in the GUI so you can check them to pass to the VM, but they will be returned to the host when the VM shuts down. This way, all four NVIDIA devices in the IOMMU group go to the VM together and are released together. Spaceinvader One has a good video with copy/paste XML on doing this with an NVMe drive, but the same principle applies here as well.
  6. Regrettably, this did not correct the problem. At least not for me. I'm going to leave it stubbed since that makes sense anyway, but I'm still chasing random crashes. It seems to happen over night, so I suspect it is a scheduled task that's making things freak out. I'll post diags to the main forum and see what we get.
  7. I am not currently, but I'll try that tonight. If I wake up in the morning to a functioning unRAID UI, that may be the fix.
  8. Yes, very similar issues. I have an RTX 2080 passed to a Windows VM and a P2000 for transcodes. Even with hardware acceleration disabled and the NVIDIA variables removed from the Plex docker, I'm getting random crashes that require a hard reboot. Haven't had much time to troubleshoot, but I was planning to start by reverting to vanilla unRAID to see if that was the issue. I'll continue following your progress and will report updates as well. Thanks!
  9. Not any more, because of this. I had a Plex meltdown last week that caused filesystem corruption. The server would lock up and require a hard reboot within minutes of starting the Plex docker. After several repeats of this, I started in maintenance, ran check and repair, nuked docker image and reinstalled everything minus the decode patch, and it's been fine. TL;DR: +1 for this being a Plex issue.
  10. Now y'all have me thinking... This may be the solution to the artifact issue I posted about a while back. The P4000 is Pascal based. I need more than 2 transcodes at a time, so it's gotta be a Quadro. It looks like I could flip my current card and cover about 75% of the new one. If it fixes the issue, that's worth it. Is there anyone out there using an RTX 4000?
  11. I certainly could have on the devices that were computers, but even then, you could only do maybe 2 or 3 before the client device became the bottleneck. I think I was close to the limit. The GPU wasn't maxed out, but the 8GB RAM in the card was just about tapped. I might have been able to get one more.
  12. I'm pretty sure you are correct. That's mostly why I haven't spent the cycles looking into it. Artifacts are visible on any transcoded stream. I tried multiple formats and multiple devices. I discovered the issue immediately after setting up the GPU. I wanted to see how many streams the card would support before things started to choke. I got up to 7 before I ran out of client devices, and the card had hardly broken a sweat. I used multiple source files including 4K h264 and HEVC, as well as 1080p. On the clients, I used various quality profiles from 1080p down to 480p using both wired and wireless connections. I have more network capacity than most office buildings, so that wasn't the issue. All transcoded streams showed artifacts, even if I was only running a single session. FWIW, I've only heard complaints from 1 or 2 remote users, and their client device (Apple TV) is notoriously bad at format support anyway. I can't verifiably say that the artifacts are happening on all remote transcode streams, but it definitely happened on all local transcode streams.
  13. Same here with multiple formats on the P4000. Since it only affects remote users, I've told them to "deal with it" until I can sort it out. My proc supports QuickSync. I haven't had time to determine if I can configure things such that Plex will use that for decode and the GPU for encode. If anyone has done this, I'd be curious as to how. I just haven't had time to mess with it.
  14. I just use a custom cron schedule in User Scripts to run an hour after the backup runs. My backups don't take nearly that long, so I know the timing is safe and nobody is likely to be watching anything at 4 AM.
  15. As long as you use the current script version as Cessquill indicated, it will check to see if the patch is applied each time it's run. I have mine set to run nightly, after my backup and Docker containers update.