heilage

Hey guys. I've had my rig up and running for a little over a year, but there is a need emerging for doing more Linux desktop work, and I need a GPU for that. So I'm looking for suggestions. When i've previously tried this with an Nvidia GTX 970, the results left a lot to be desired. A lot of unstable behavior, and difficulties with drivers. I'm not sure if there are inherent problems with Nvidia cards in unRAID VM setups, or if this was something else, but I'm looking for suggestion for a cheap GPU to put in that provides decent driver support for Linux (Fedora in particular). The only physical requirement is DP1.2 output, because I daisy chain my monitors.

As of yesterday, I was looking for a system crash, which should have been logged in some form, but I gained access to the event logs for my alarm system, and it turns out to have been some kind of power error that evening. Looks like unRAID was fine, but I should get a UPS on it anyway. I'll have to ask my alarm company why they couldn't tell me what was in the event log in my alarm system, but that's another matter. Thanks for helping

I do not have a UPS (should though... one of those things), so the parity check is running now. Everything seems to be fine though, at least for now. I'll try the plugin, so I can check it out if it happens again. If not, I'll have to chalk it up to a coincidence or freak occurrence. I have no pets (sadly), and to my knowledge no critters, so I doubt that was the issue.

Hi everyone. Last night my Plex docker died (was not at home), and I couldn't connect to it again for some reason. When I got home today, my server was dead. I apparently didn't have a power outage, I called my alarm company and they could inform me that there hasn't been any outages recently that affected my system. So I'm concluding that my server died, for some reason. I booted it back up, and it seems to be working, but the syslogs all start from today, I can't seem to find any logs or diagnostics that are older than when I just now turned it on. What happened here? Shouldn't unRAID keep the old logs, at least for a while?

I suspect that the root issue here is in Windows, actually. I have previously (although not in unRAID setups) had problems with Windows being finicky about which audio outputs were enabled/disabled and presedence. Could you show a screenshot of your output devices from Windows? (Right click on the sound icon in the taskbar)

Updates abound! Sorry for the delay, I'm preparing to move to a new apartment, so I have less time to mess around with my computers, naturally. Right now, stability looks pretty good. I've rebooted several times, shutdown unRAID and rebooted it to see if I lose any configs. As far as I can see, I haven't gotten any reboot loops or BSODs for a while. I have no tried editing syslinux like jonp suggested though, but I might as well try it. I even got games from network shares to work (enabling visible shares for alternate accounts helped massively). Pretty happy with the results right now, but I'd still like to know what was causing all my issues. And who knows, the BSODs might turn up again. I haven't had any issues since disabling core 0 for VMs though, as I read in another post that unRAID uses it a lot. I want more cores...

I've been using 0.1.110, I believe it was the recommended version?

Since installing the drivers often cause the issues, yes. I use the latest stable set, from GeForce Experience. In the previous thread, I also rolled back the drivers in an attempt to fix the issues, but it did not help.

Oh, forgot to mention that. I set the CPU cores to 3 since that post, and have not changed it since. Also, I always pass through the audio now too. I have updated the GPU BIOS, luckily Gainward supplies self-installing updates from their website, so it went smoothly. I'm working on setting MSI interrupts now (it was disabled). EDIT: Enabled MSI interrupts, rebooted, still working fine. EDIT2: Getting random BSODs now. First SYSTEM_SERVICE_EXCEPTION, then MEMORY_MANAGEMENT, but in both cases it boots normally again after a reboot. This is on SeaBIOS. Also, has anyone experienced that unRAID switches the vdisk order, so that it doesn't boot?

Suggestions from any angle are welcome I have not messed with MSI interrupts, and right now I have a SeaBIOS based one working. I'm not using HDMI sound, but it does say to do it anyway. I would also like to try flashing the ROM/BIOS on my GPU, I will report back with results. (Trying the MSI thingy first)

Okay, so I'm having a bunch of issues in general with my Windows VMs. There appears to be two patterns emerging: SeaBIOS - Mostly work fine on initial installation, I can even use it for some time to game - Fail after a few days to BSODs with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, and constant reboots, caused by the graphics card - Perhaps something goes wrong here after a reboot as well? OVMF - When they crash, and they do, they take unRAID with them - Will also crash when initializing driver - Non-persistent boot configuration whenever unRAID goes down, will not boot after a reboot and has to be reinstalled/reconfigured from scratch The issues appear to be linked to the initialization of the graphics drivers, on my Nvidia GTX 970. This card should work fine, but it does not. Linux appears to be fine in most cases, although Fedora had some issues after I fiddled around with some drivers and window managers. That said, right now I can boot both my Xubuntu and Fedora VMs (SeaBIOS based) just fine. I upgraded to unRAID 6.1.7 this weekend, and I was hoping for some stability, but thus far no luck. I refer you also to my thread from last week or so: https://lime-technology.com/forum/index.php?topic=45367.0 What am I doing wrong? I've had to install Windows 10 10-15 times the past two weeks, I can't help but feel that something is very wrong. I could RMA my GTX 970, but if it is the cause of my issues, why is Linux working fine?

I think you can, Jon. I haven't had any issues since. (Is there a button for marking it as solved? I can't find it)

Hah, don't worry about that. It was my own error (although I can't remember this being specified in the manual?). I'm just glad it's working again, although I do wonder what made it work the past month or so.

It works! It was working fine with Win10 natively installed, so I was suspicious as to what could cause it, if the GPU was not faulty (it may still be, but that remains to be seen). I will address this point by point: - This was not recommended, as per my google results. I did not do this step. - Changed to OVMF, may have contributed to my success - HyperV is off, always have been - GPU firmware, I left this as-is, to limit the number of variables. Also, the newest firmware is older than when I bought the card (may still be outdated though) - Switched from 110 to 109, may have contributed to my success - I did not know about this. I have never forwarded the GPU audio, and as such, this may have been the issue all along. It would also kinda make sense given my BSOD. Setting this may have contributed. - MSI interrupts have not been set, but this could be an option. Thank you, you put me on the right track! More testing and verifications are necessary, but this was a huge help.

I'm not sure if I have a spare 8.1 image available that can be used to install (I don't think I have a key right now, I believe I need one to install?). I'm starting to think that this might be down to the GPU itself, and a hardware issue (maybe the RAM?). There appears to be some instruction running when the GPU initializes that causes it to crash, and it wouldn't surprise me if the process is different under Ubuntu, considering it has a completely different driver package, which may explain why it does not break when booting there. I'm going to yank out the power on the unRAID drives and try to install Win10 again directly. If it fails again, I believe we have our man. It actually didn't occur to me that the GPU might be faulty until I woke up this morning. It's less than a year old, so RMAing it shouldn't be an issue, if that's the case. If it works fine on a native Windows installation, then I'm not sure what to do. Scrapz: I actually haven't set a lot of the things you mention, but considering that Win10 was working fine for a good month before it suddenly crashed, these things shouldn't really be that relevant? It appears to have spontaneously died on me, but of course, it may have been running half-assed without me noticing (I have had some issues, and I haven't had time to go into heavy usage yet).