Fizzyade

Since upgrading to 6.12 and updating the nvdia I've been getting GPU errors, like the following: [56386.612293] NVRM: Xid (PCI:0000:08:00): 31, pid=17147, name=ffmpeg, Ch 00000008, intr 10000000. MMU Fault: ENGINE GRAPHICS HUBCLIENT_FE faulted @ 0x1002_06807000. Fault is of type FAULT_PDE ACCESS_TYPE_WRITE [57317.960662] NVRM: Xid (PCI:0000:08:00): 69, pid=27124, name=ffmpeg, Class Error: ChId 0020, Class 0000c1c0, Offset 00001b0c, Data 00008000, ErrorCode 0000000c I am using Emby in a docker container, it's the only thing that uses the GPU and once the GPU fault occurs, it kills that ffmpeg which then causes Emby to either just stop playing the stream that was being played, or it jumps ahead to the next episode if it's a TV series that is being watched. Nothing else has changed and the machine was 100% stable prior to updating. I know when I was on a previous Unraid release, I had stuck to an older driver and I never had any issues, when I checked the driver being used it was using "latest", so as a test I changed the settings in the plugin to use " v530.41.03" and all the issues have now gone away, it's back transcoding without any GPU faults.

The drive has only been used over the past couple of days, these issues I've been suffering with since 6.9 came out, but i'll check that out. The VM's causing excessive load is what is killing me at the moment, they're idle with no load in the VM but I'm seeing ridiculously high loads in unraid.

I can't reboot it, in going to have to hard power down the machine. reboot failed as did reboot -f

Once again, the GUI has locked up. A linux VM that was completely idle sent unraid into a load average of 100. Yesterday when I had to reboot it, a different idle linux VM ended up sending it to 700.

tower-diagnostics-20210510-2225.zip Here's a set of diagnostics I took a few minutes back.

Been there, Got the t-shirt, but no solutions.

<rant> Tbh, I'm getting sick of problems since 6.9 and thinking of starting to look at alternative solutions to Unraid. I appreciate that this may not be the experience of others, but prior to 6.9 I had no problems, zero, none, nada, I didn't expect 6.9 to cause so many problems from day 1. The VM performance is killing my machine, I'm seeing loads of 70-700 when VM's are idle and qemu consuming all the CPU. When I first updated I had an issue where every KVM was locking up the graphics, the VM's themselves were still running but unable to VNC to the KVM, I eventually edited one of the VM's config file in the editor and suddenly all the VM's stopped locking the KVM up. I've seen that others are having this problem too, I've tried the "fixes" that have been mentioned, but nothing thus far has solved it. Between that and continual "blank pages" (i.e I get the unraid header but no actual content) returned from the web server, sections empty or missing it's starting to become a really miserable experience. Long standing issues like the VNC port resetting when making changes in the GUI, that I've mentioned several times over the course of a few years still haven't been fixed, this is *basic* stuff. The GUI feels clunky. The mover has always been a resource hog, killing the machine when it runs, this is an machine with 64GB of RAM, ssd's for the cache and VM's. I'm at a loss to what is actually going on, but it has got to the point now that I'm losing faith in my Unraid solution.

I'm seeing high CPU usage on my virtual machines since switching to 6.9. I previously had an issue with 6.9 where the KVM would die on any VM after a very short time, I switched the CPU type on one of the VM's and suddenly everything started working again without locking up, support were just as baffled about this as me. Now though I'm seeing high CPU load constantly on my VM's, I have a windows VM 10 VM running and the CPU usage inside the VM is low, but looking on unraid I'm seeing 300-400% CPU usage constantly and a screen full of red bars on the main unraid page. All my issues started when I moved to 6.9, 6.8 everything worked like a dream. I've seen a few other reports about CPU usage and people have mentioned changing the scheduler, I checked and mines already set the recommended value mentioned in those threads. I can often get Unraid to "hang" by starting a VM, the CPU usage goes crazy and the web ui stops responding, the only way to fix it is to ssh in (which takes quite a while due to the CPU usage) and kill the VM process, at which point everything drops back to normal. Anybody else experiencing this? Any thoughts?

driver: ixgbe version: 5.10.28-Unraid firmware-version: 0x00012b2c expansion-rom-version: bus-info: 0000:03:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes

No, no log spam regarding the card. (Sorry for not replying earlierm i'm unwell)

I have a X520-DA2 (uses SFP+ modules rather than RJ connectors) and it is working fine for me, also reports as a 82599. Wonder whats different? 03:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)

64GB. I really wish that Unraid supported lxc containers though, I have a NUC running Proxmox which has a load of containers set up which I use for CI (TeamCity), but I need more containers to handle other builds and the NUC has no more ram (it's got 64GB as well) and unraid would be ideal if it supported them.

@SpencerJ@jonp Ok, I created a new VM, pointed it at the existing disk image and set the mac address to the previous VM and so far, Windows 10 seems to have held up and not fallen over. I'm guessing I could post the XML of the VM that doesn't work? I'm going to see how this holds up before doing the same procedure to all of my other VM's. The only thing I can really see, is that the graphics freezing VM is 'pc-i440fx-4.2' and the newly generated VM is 'pc-i440fx-5.1'

@jonpI'm at the end of my tether here, none of my virtual machines work properly anymore, I just rebooted the windows one and I managed to get to the desktop before KVM stopped working, went back in via RDP and I could use it, back into VNC and it works again, but if you drag a window or do anything intensive, it stops working again. I'm happy to send you any logs necessary, but I need some input on what I can give you to try and figure out what is going on. Doesn't matter if it's Windows or Linux, every VM exhibits this behaviour.

Yes, the wiping out of XML values is infuriating. When changing stuff in the GUI, only the items that were affected by the change should be updated in the XML, everything else should remain as it is. Ideally, the VNC port should be exposed in the GUI because it's pretty much a requirement, you don;t go around changing the VNC port on your client every time because the order has changed.

Yeah, I've seen other funnies in the GUI with safari. Funnily enough, I just switched to firefox a week or so back because Safari on Big Sur is crashtastic, it also seems very slow.

In the interest of being fair, the Unraid team have held their hands up and apologised and have gone out of their way to try to find the cause of my problems. Although it's still ongoing, I'm hoping that we can get to the bottom of it. I rarely rely on support, I've been a programmer professionally for 25 odd years and programming 6-7 years before that, so I normally figure stuff out myself so I'm probably a bit more sensitive when it comes to asking for advice. I've had very few issues with Unraid over the past 2 or so years that I've been running it, I bought the pro license a couple of days after trialling to support them, even though I didn't need that many disks, I'm a believer in supporting companies (especially smaller software companies) because it's hard work writing software.

I updated to the latest release, but I'm still suffering with this issue. Latest KVM drivers as well, it affects Windows and Linux, both will just stop providing graphics, the VM's themselves are still up and running. I've checked logs in Windows/Linux and on Unraid and can't see any issues being reported, I'm baffled by this. I rely on VNC when I am setting up my Windows TeamCity build agent as my code signing certificate is smartcard based and you cannot access the card via RDP (for security), so I have to ensure that the session is set to VNC. I use the same VM to do test builds as well, the software I am working on (https://www.pingnoo.com) runs on macOS, Linux and Windows, so I have development environment VM's set up and can just pull the latest code and check it compiles and runs correctly under the various operating systems. @jonpany ideas on any logs or info I can send your way? It's really frustrating as it's worked perfectly for 2 years and suddenly all the VM's have started to misbehave in exactly the same way. I just don't get any problems with Unraid normally (barring an issue I had with the cache transfer causing CPU load, but I managed to solve that quite a while ago).

Hi Jon. As I just mentioned in the other thread, I updated VirtIO to the latest, I'm using QXL. I currently have my WIndows 10 VM running and although the display is working, the keyboard and mouse are not at the moment. If I switch out to RDP and then go back into VNC they will start working again. This is the same mechanism as the other problem I am happening when the screen stops responding, if I go back into RDP and then back out, VNC will start working again. I would assume the same applies to Linux, except there's no RDP, so there's no real way of me fixing a Linux machine when it gets into this state, I just have to ssh in and reboot. These issues started when I upgraded to 6.9 stable, I'd been using the release candidates for a quite a while and they gave me no issues like these, but now every VM is behaving the same.

Hi Jon, Thanks for taking the time to respond, it's been a little frustrating but hopefully this has been a constructive exercise, I wasn't angry, just a little bit dissapointed that the communication wasn't as good as I expected. I wanted to let you guys know in a polite manner that I felt this way! The VNC port issue is just a long standing thing, I've mentioned it a few times. While under normal circumstances it's probably not something that most people will have an issue with, but for me, it is. You definitely need the options to set a port and keep it even after editing the XML, this is my only real bug bear with unraid. Another semi related thing is hitting the console option on dockers for me always results in a pop up window which asks me to log in again, I have to log in and then go back and click on console and then I get to the console. I'll upgrade once everybody has gone to bed and finished watching shows. I absolutely love Unraid, I recommend it to anybody who wants to put together a media server or NAS, and apart from 2 dead USB sticks which were caused by a plugin I've not had any significant issues with it. I'm a Mac user, I have been since the mid 90's and I use unraid to host VM's which I use for software development, so I have various Linux and Windows installations with my development tools in, the KVM for me is crucial (although I could run a VNC server in windows) as my code signing certificate for windows is smartcard based which means it is not accessible when connecting through RDP, so being able to use VNC means that I am able to sign binaries - it's all handled through TeamCity. I did just update the VirtIO drivers and straight away I hit one of the VNC issues I've seen as well (I didn't mention this one before), on some occasions the screen is still working, I can see the cursor flashing, the time updating etc but niether the keyboard or mouse are functional, it doesn't matter if I just my favourite VNC software, Jump Desktop, or the built in noVNC client in Unraid. Actually, last week I tagged you guys on twitter as I had a chain of tools running which involved Unraid, Jump Desktop and Duet and it worked perfectly. When I see these issues with VNC, I can normally close the VNC session, switch to RDP and immediately exit and go back to VNC and then the session starts working again. I posted the question in the other forum more of a "is anybody else seeing this or is something gone screwy with my install".

And still no reply. Seriously? I called you out on poor support, you tell me to email, which I did on the 24th of Feb and I still get no response. @SpencerJ

I have to also say, I'm grateful that those who have responded in this thread have taken it at face value, that it was a observation about my perception of support, it wasn't meant in any way to single out anybody or a "this sucks" kind of post, I wanted it to be constructive and I'm glad that I haven't had to don the flame suit just yet! I think Unraid is awesome, for people like myself who use it primarily to run a media server (and the assosicated other tools that go along with that) and who use the virtual machines as development environments it's brilliant. The fact that a catastrophic array failure results (i.e your parity + other deivces) only in the loss of data from those disks and not the array. The speed trade-off for me is worth that alone.

I have done this, as I said, I don't like to tag people as sometimes it gets people really wound up!

For anybody coming up with this issue, you need to ensure your client is using 32-bit colour.

I try to avoid tagging people, sometimes tagging somebody can have the complete opposite effect to what was desired! 😛 It's just an observation, not just from my posts, but other peoples posts as well and the appearance it gives to people visiting the forum, especially if they happen to be prospective users. As an aside, there's also the issue of issue reports, I've mentioned many times that the setting for the VNC port should be in the GUI because as it stands if you change it in the XML and then suseqently make a change in the GUI it gets lost, I'm forever chasing my tail on this, it's presumably something that's entirely trivial for them to fix and that makes it even more disheartening that it's been ignored, hell, I'd even settle for them to remove auto and just use a counting high water mark for the VNC port every time you create a new VM because the current behaviour is exceedingly irritating. As I said, this is all said in the most constructive way I can do it, I'm not stamping my feet and throwing toys out of the pram, but giving feedback on my experience.