KptnKMan

I've been using this plugin to backup my VMs for a couple weeks now, but unfortunately I've found that this this is the cause of my server being unable to shutdown. My unRAID was unable to shutdown and would freeze forcing me to hard kill the system, causing a parity check every time. I do not want to do this for an otherwise stable system. Rolled back from 6.9.0-b1 to 6.8.3 didn't solve it. Running in safe mode showed that everything worked, but I couldn't start my VMs due to the Unassigned devices plugin. Uninstalling the VM Backup plugin solved the issue, and removed the error at startup. Something in the VM Backup plugin is breaking the Hypervisor and messing with my bonded network connection. From what I can tell, first there's the "error: failed to connect to the hypervisor" error: Failed to connect socket to '/varrun/libvirt/libvirt-sock' : No such file or directory" After this, I seemed to be getting some kind of trace error when shutting down: More shutdown: And finally stalls here forever (I've waited a day for this, and it didn't shutdown😞 Uninstalling the VM Backup Plugin fixed the issue, and I can now shutdown/reboot without stalling, crashing and parity check. The errors have gone also. It is a real shame because I use this plugin daily (Nightly). Does anyone know why this is happening? I'd like to use this plugin.

Thanks for this thread and thanks @JesterEE. I've traced my issue to this thread. I've been using this plugin to backup my VMs for a couple weeks now, but unfortunately I've found that this this is the cause of my server being unable to shutdown. My unRAID was unable to shutdown and would freeze forcing me to hard kill the system, causing a parity check every time. I do not want to do this for an otherwise stable system. Rolled back from 6.9.0-b1 to 6.8.3 didn't solve it. Running in safe mode showed that everything worked, but I couldn't start my VMs due to the Unassigned devices plugin. Uninstalling the VM Backup plugin solved the issue, and removed the error at startup. Something in the VM Backup plugin is breaking the Hypervisor and messing with my bonded network connection. From what I can tell, first there's the "error: failed to connect to the hypervisor" error: Failed to connect socket to '/varrun/libvirt/libvirt-sock' : No such file or directory" After this, I seemed to be getting some kind of trace error when shutting down: More shutdown: And finally stalls here forever (I've waited a day for this, and it didn't shutdown😞 Uninstalling the VM Backup Plugin fixed the issue, which is a shame because I use this plugin daily (Nightly).

Hi there, Hoping that maybe you could make an icon for my original Coolermaster Stacker 810 that I'm still rocking after all this time. 🙂 Thanks!

A bit of research goes a long way. There's not much reason to shy away from Nvidia GPUs. I've had both nvidia and ATI GPUs, nothing is perfect. Like I said, research what hardware you want to buy. Using unraid is not the easy path, you'll get what you put into it.

I've said this in other threads, but the hardware in my Signature works pretty well for what I'm doing, which is the same thing. 👍 I'm using Unraid as my daily desktop driver for the last few months, and it's worked pretty well. If you're set looking at Unraid for a daily driver setup, I'd recommend not doing anything too extreme in terms of configuration. That's what I went for, and it's been 99% great so far. There are so many variables with doing this that nothing (repeat: NOTHING) is going to work 100%, especially if you want to use very recent hardware, but you'll learn a lot getting there. However, on the flip side, very recent hardware will get you better performance and better future-proofing, but you'll have to deal with the inevitable bugs and incompatibilities. ¯\_(ツ)_/¯ Also, don't rely too much on getting community support for Unraid, it can be a bit hard to find help in this forum... but that's not to say people aren't out there helping. Consider that when buying potentially problematic hardware. So I'd recommend researching the hardware you want to use before purchasing anything. Check hardware component compatibility and Linux kernel requirements, if any, but you should be fine with most setups. I recently switched my all-AMD setup to an AMD(CPU)-NV(Gfx) because a friend of mine was kind enough to sell me his old 1080ti for cheap, and I'm liking this setup. This post is written using my virtualised, VR-gaming setup on unraid. 👍

@Shadow01 You should research the basic hardware before you look to purchase what other people are doing, its not too difficult.

Definitely, without question. I do all of those things now and more. I would say that I don't use Nextcloud, but there are some options for running exactly this in a docker container. You can find them in Community Apps, for example:

Still trying, the result of my `sensors-detect` root@blaster:~# sensors-detect # sensors-detect version 3.6.0 # Board: ASUSTeK COMPUTER INC. TUF GAMING X570-PLUS (WI-FI) # Kernel: 5.5.8-Unraid x86_64 # Processor: AMD Ryzen 5 3600 6-Core Processor (23/113/0) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... Success! (driver `k10temp') AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): YES Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found `Nuvoton NCT6798D Super IO Sensors' Success! (address 0x290, driver `nct6775') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): YES Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): YES Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0) Do you want to scan it? (YES/no/selectively): YES Client found at address 0x1a Probing for `Analog Devices ADM1021'... No Probing for `Analog Devices ADM1021A/ADM1023'... No Probing for `Maxim MAX1617'... No Probing for `Maxim MAX1617A'... No Probing for `Maxim MAX1668'... No Probing for `Maxim MAX1805'... No Probing for `Maxim MAX1989'... No Probing for `Maxim MAX6655/MAX6656'... No Probing for `TI THMC10'... No Probing for `National Semiconductor LM84'... No Probing for `Genesys Logic GL523SM'... No Probing for `Onsemi MC1066'... No Probing for `Maxim MAX1618'... No Probing for `Maxim MAX1619'... No Probing for `National Semiconductor LM82/LM83'... No Probing for `Maxim MAX6654'... No Probing for `Maxim MAX6690'... No Probing for `Maxim MAX6680/MAX6681'... No Probing for `Maxim MAX6695/MAX6696'... No Probing for `Texas Instruments TMP400'... No Probing for `Texas Instruments AMC6821'... No Probing for `ST STTS424'... No Probing for `ST STTS424E'... No Probing for `ST STTS2002'... No Probing for `ST STTS3000'... No Probing for `NXP SE97/SE97B'... No Probing for `NXP SE98'... No Probing for `Analog Devices ADT7408'... No Probing for `IDT TS3000/TSE2002'... No Probing for `IDT TSE2004'... No Probing for `IDT TS3001'... No Probing for `Maxim MAX6604'... No Probing for `Microchip MCP9804'... No Probing for `Microchip MCP9808'... No Probing for `Microchip MCP98242'... No Probing for `Microchip MCP98243'... No Probing for `Microchip MCP98244'... Success! (confidence 5, driver `jc42') Probing for `Microchip MCP9843'... No Probing for `ON CAT6095/CAT34TS02'... No Probing for `ON CAT34TS02C'... No Probing for `ON CAT34TS04'... No Probing for `Atmel AT30TS00'... No Probing for `Giantec GT30TS00'... No Client found at address 0x1b Probing for `ST STTS424'... No Probing for `ST STTS424E'... No Probing for `ST STTS2002'... No Probing for `ST STTS3000'... No Probing for `NXP SE97/SE97B'... No Probing for `NXP SE98'... No Probing for `Analog Devices ADT7408'... No Probing for `IDT TS3000/TSE2002'... No Probing for `IDT TSE2004'... No Probing for `IDT TS3001'... No Probing for `Maxim MAX6604'... No Probing for `Microchip MCP9804'... No Probing for `Microchip MCP9808'... No Probing for `Microchip MCP98242'... No Probing for `Microchip MCP98243'... No Probing for `Microchip MCP98244'... Success! (confidence 5, driver `jc42') Probing for `Microchip MCP9843'... No Probing for `ON CAT6095/CAT34TS02'... No Probing for `ON CAT34TS02C'... No Probing for `ON CAT34TS04'... No Probing for `Atmel AT30TS00'... No Probing for `Giantec GT30TS00'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1) Do you want to scan it? (YES/no/selectively): YES Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `k10temp': * Chip `AMD Family 17h thermal sensors' (confidence: 9) Driver `jc42': * Bus `SMBus PIIX4 adapter port 0 at 0b00' Busdriver `i2c_piix4', I2C address 0x1a Chip `Microchip MCP98244' (confidence: 5) * Bus `SMBus PIIX4 adapter port 0 at 0b00' Busdriver `i2c_piix4', I2C address 0x1b Chip `Microchip MCP98244' (confidence: 5) Driver `nct6775': * ISA bus, address 0x290 Chip `Nuvoton NCT6798D Super IO Sensors' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. Unloading i2c-dev... OK

I'd be interested to know what type of RAM you're using. I went on a similar journey last year and built the system in my Sig: - ASUS TUF X570-PLUS GAMING (Wi-Fi) - AMD Ryzen 5 3600 - Crucial CT16G4WFD8266 (16GB ECC) x2 Mine has been working great so far, did my research before purchasing and everything works in Multi-bit ECC mode. Only thing I might have redone is maybe gotten a CPU with more cores, as now I'm considering upgrading to a 3900x. 🤔

Hardware in my Signature works pretty well for what I'm doing, which is the same thing. 👍 This post is written using my virtualised, VR-gaming setup on unraid. 👍

Hi all, I've been trying for a while to get temp monitor working with My Ryzen setup. Trying to get the temps working for my ASUS TUF GAMING X570-PLUS (WI-FI), without much luck. Recently with the 6.9.0-beta1 release, I understand that there is support in the new kernel. When I initially upgraded from 6.8.3 to 6.9.0-beta1, I noticed that some temps were visible, but they have gone and now I get an error in my log when I "Load Drivers". I've seen in the 6.9.0-beta1 release thread that I should add `acpi_enforce_resources=lax` to my flash syslinux config, which I did: (I also loaded perl from Nerd pack without issue or error). Log during detection process: May 6 11:11:40 blaster kernel: i2c /dev entries driver May 6 11:11:51 blaster kernel: nct6775: Found NCT6798D or compatible chip at 0x2e:0x290 May 6 11:11:51 blaster kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20191018/utaddress-204) May 6 11:11:51 blaster kernel: ACPI: This conflict may cause random problems and system instability May 6 11:11:51 blaster kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver May 6 11:11:51 blaster kernel: nct6775 nct6775.656: Invalid temperature source 28 at index 0, source register 0x100, temp register 0x73 May 6 11:11:51 blaster kernel: nct6775 nct6775.656: Invalid temperature source 28 at index 1, source register 0x200, temp register 0x75 May 6 11:11:51 blaster kernel: nct6775 nct6775.656: Invalid temperature source 28 at index 2, source register 0x300, temp register 0x77 May 6 11:11:51 blaster kernel: nct6775 nct6775.656: Invalid temperature source 28 at index 3, source register 0x800, temp register 0x79 May 6 11:11:51 blaster kernel: nct6775 nct6775.656: Invalid temperature source 28 at index 5, source register 0xa00, temp register 0x7d I can detect a few different drivers/devices: Error when I "Load Drivers": ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20191018/utaddress-204) And now all the "Sensors" below are always blank no matter what: Any ideas what might be the matter?

@colem Haven't heard back from you about your issues. Going to assume you resolved it.

I'm afraid I'll need still more information from you. I've gone back to my previous post above and highlighted all the things red that I think you need to definitively confirm. You need to check and confirm all the things, including your hosts BIOS is setup correctly. I'd recommend use the BIOS Defaults option and then set everything up in turn. Virtualisation Enabled, Legacy PCI Support, Boot order, etc. Especially if you've upgraded your BIOS. Also, make sure you're on the latest BIOS (But it seems like you are). Also, be verbose and specific, I cant see what you're looking at. A couple of extra things here: - Assign your CPU cores in SETTINGS->CPU Pinning. I leave the first core completely alone for unRAID, use 4 cores for my VMs and currently my last core for Docker and one of my dev VMs. You can do it in each VM, but I find this method doesn't mess up my XML. Like this: - What does your XML look like? Maybe post that in a code block here. Also, considering that you're having issues, I think you're changing waaaay too many things at once: - You need to do everything step-by-step and see where problems arise. 1 change at a time. Check, confirm and reboot before anything else. - How about keeping everything the same, on 1 core, and add just the GPU and GPU-Audio. - Are you adding other Sound cards? Other devices? - What GPU are you using? Different GPUs have different requirements. - What vBIOS are you using and where did you get it? Lastly, I'd recommend posting your unRAID diagnostics file, as it will help others to troubleshoot. That's in TOOLS->DIAGNOSTICS.

Hey, if you're referring to the kernel in the latest 6.8.3 release, then I've had no issues. As a matter of fact, I've seen a slight performance boost in gaming, which I thought might be due to the AMD cpu cache passthrough update. The 4.19.107 kernel seems to be good for me. The solution I found was mostly due to the work by @SpaceInvaderOne. He really figured out most of this, but I'm happy to help. Let us know how you do. Like I said, we seem to have similar hardware, so we can probably figure it out. 👍

Thanks @johnnie.black for your help. Late reply to this, but I got everything copied over. Copied everything directly onto the disks, rather than to the shares. Marking this one as solved.

Hey, are you still getting these issues? I seem to have a very similar setup to you (Details in signature below), and I've been using my system as a VM gaming system for some time. I recently changed from an R9-290 to a GTX1080Ti, and that seems to now be working well also after some modifications (details here, recommend you check it out). Using my R9-290, I had to use a compatible vBIOS to get it to work at all. Some questions: - Have you isolated your CPU usage between VMs and other tasks like Docker? - What are the EXACT model numbers of your AMD and nVidia cards? - Are you downloading and using a compatible vBIOS from techpowerup? Some details I'd recommend for a smooth setup: - Host: Use legacy boot on your host, avoid UEFI. Broke things for me. make sure in BIOS that Legacy boot/compatibility is enabled for all PCIe devices also. - Host: I'm currently using Unraid 6.8.3, just upgraded, but I was stable on 6.8.1 and 6.8.2 for a good while. - VM: Use OVMF BIOS, Q35-4.2 machine type. - VM: Use latest VirtIO drivers, I'm using virtio-win-0.1.173-2.iso - VM: All vdisks mounted using VirtIO. - VM: Before trying to install Windows 10, try booting the VM with only CPU 1 core for the install.

Thanks @SpaceInvaderOne I appreciate the compliment. Just hoping that this helps someone else. I really hope that we could get a VM advanced UI for configuring the PCIe settings when using graphics card or sound card: - multifunction on/off - bus - slot - function These are PCIe devices, so it seems to be a common setting, that would translate to the XML like the other UI settings, overwriting the default. This would go a long way to making this easier to fix.

Well, I figured it out. I spent many hours trying many different things, but this turned out to be it. Really wished that someone could have pointed me in the right direction, especially with so many current thread posts about the same thing on this forum. As such, I hope that I might be able to help someone else by summarising my journey and how I got there. A full solution is below, but first, I highly recommend watching these 2 excellent videos from @SpaceInvaderOne. Really saved my bacon: 👍 I'm basically summarising much of what he put in the video. My Summary: I was able to fix an already working VM, with my newly added GTX1080Ti using these methods. I didn't need to disable Hyper-V as others have said, and I'm using the latest nvidia drivers. In the end, the "code 43" error that is prevalent, seems to be due to a couple of things: - Modified BIOS, removing application headers from file, using Hex editor. - Specifying GPU pci device as "multifunction" in VM XML. Modifying BIOS: - Download the Hex Editor, install. - Download your compatible BIOS from techpowerup. - Open the bios file in hex editor. I'm using HxD like in the video. - Look for line that looks like "UªyëK7400éLwÌVIDEO", mine was prefaced with a series of "ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ" characters. - Next, delete everything above line "UªyëK7400éLwÌVIDEO", so that the matching offset reads "00000000" (8 zeros). - "Save As..." the file with a new filename. Save it somewhere on your unRAID system, like one of the shares. - I saved mine to "isos" share. You can save it anywhere on unRAID. - You're done. Modifying your VMs XML: - Before Starting, make sure your GPU is in its own IOMMU Group (Tools->System Devices). - If your GPU is not in its own IOMMU Group (Its fine if the GPU shares that group with the GPU-Audio). - Setup your VM in unRAID as normal. - I have had success using "Q35-4.2" Machine type, and "OVMF" BIOS. I left Hyper-V "on". - I'm using VirtIO Drivers "virtio-win-0.1.173-2" if that is helpful. - Specify your GPU and GPU-Audio Sound Card of the GPU. Always add your GPU-Audio, dont try to avoid it. You need it. - If you want to use your motherboard sound card, you should add it by clicking the green plus-sign on the left. - Either "CREATE" (Do not "Start VM after creation") or "UPDATE" the VM at the bottom, to set a baseline config. - Go back into the VM config. On the right change "FORM VIEW" to "XML VIEW". - Find the lines for the GPU and GPU-Audio, the line should start with "<hostdev" and a line later will end the section with "</hostdev". - You should see 2 hostdev devices, there may be more. The first should specify your GPU BIOS you specified earlier. - You need to change the the lines that specify the "<address" within the VM, not the "<address" outside the VM (in the host). - On the first line, change nothing, but add "multifunction='on'" to the end before the "/>" close. - On the second line, change the "bus" and "function" to match the first line, but add 1 to the function. - When done editing, I recommend copying the whole xml and keeping a backup somewhere. - Save the config by clicking "UPDATE" at the bottom. - You're done. Something to note is that if you change ANYTHING using the GUI, it will overwrite these pci XML modifications. So, again I'd recommend keeping a backup somewhere in your unRAID. With this, I was able to use my single nvidia card without issues. Thanks again to @SpaceInvaderOne for figuring this out. I hope this can help someone else. ☺️

I've dunped my BIOS out directly in unRAID, and trying to follow instructions to fix. I'm unsure if this means something but I've noticed when running "lspci v" is that there is no kernel driver listed next to my card: 0d:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at f4000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f0000000 (64-bit, prefetchable) [size=32M] I/O ports at f000 [size=128] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [128] Power Budgeting <?> Capabilities: [420] Advanced Error Reporting Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] Secondary PCI Express <?> 0d:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1) Subsystem: eVga.com. Corp. GP102 HDMI Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 4 Memory at f5080000 (32-bit, non-prefetchable) [size=16K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Also, I'm unable to either unbind or bind the device: # echo "0000:0d:00.0" > /sys/bus/pci/drivers/vfio-pci/bind -bash: echo: write error: No such device # echo "0000:0d:00.0" > /sys/bus/pci/drivers/vfio-pci/unbind -bash: echo: write error: No such device

Another strange finding, is that my Windows 10 VM boots up and I can RDP to it. Looking around the system and forums more, it could be the "code 43" error.

I believe that this should be the correct BIOS for me to use from techpowerup, as it has the same modified date as the build date on my BIOS (2017-04-17) and VBIOS Version (86.02.39.00.90) that I got from the dump. Still doesn't work. I'm not sure what else to do.

Hi all, I'm hoping someone can help. I'm having trouble with passing through a GTX1080TI GPU. I am using model EVGA 11G-P4-6696-KR, known as "EVGA GeForce GTX 1080 Ti FTW3 GAMING". I had trouble finding a compatible BIOS on techpowerup, because there is no direct comparison. I saw that there are "FTW3 Elite Gaming" and "FTW3". I've tried the FTW3 BIOS, but not the FTW3 Elite, I'm concerned that it is not appropriate. So I dumped the bios in a bare metal Windows 10 install using nvflash, and have saved it to my array. Even still, I cannot seem to get my VM to boot with it using any configuration. The screen flashes and then no signal, every time. I need to reboot to get anything back. I was able to boot into Windows 10 using the bare metal install, so I think the card is working. I've watched the videos by SpaceInvader and I've passed through cards before using this system (An R9-290 and recently a RX-5600XT that I am returning). Both worked without much issue at all. Can anyone help with advice? I also dumped the version using nvflash: NVIDIA Firmware Update Utility (Version 5.590.0) Copyright (C) 1993-2019, NVIDIA Corporation. All rights reserved. Sign-On Message : GP102 PG611 SKU 50 VGA BIOS Build GUID : 402D5B72B8A34DFBBEB8A9C5CD99EE31 IFR Subsystem ID : 3842-6696 Subsystem Vendor ID : 0x3842 Subsystem ID : 0x6696 Version : 86.02.39.00.90 Image Hash : AAA37529FD718F13599221F885E83C25 Product Name : GP102 Board Device Name(s) : GeForce GTX 1080 Ti Board ID : 0xEE17 Vendor ID : 0x10DE Device ID : 0x1B06 Hierarchy ID : Normal Board Chip SKU : 350-0 Project : G611-0050 Build Date : 01/18/17 Modification Date : 04/17/17 UEFI Version : 0x30006 UEFI Variant ID : 0x0000000000000007 ( GP1xx ) UEFI Signer(s) : Microsoft Corporation UEFI CA 2011 XUSB-FW Version ID : N/A XUSB-FW Build Time : N/A InfoROM Version : G001.0000.01.04 InfoROM Backup : Not Present License Placeholder : Not Present GPU Mode : N/A

Thanks @testdasi but in the reading around this forum, I've decided to return the 5600XT and get a second hand 1080TI from a friend of mine. Maybe next year or year after I'll see how AMD is doing again with their hardware.

Also info update on this, using ASUS TUF GAMING X570-PLUS (WI-FI) BIOS with latest 1405 bios, also now getting this error. Something to note, I wasn't experiencing any issues until I upgraded my gfx to RX-5600XT. My older R9-290 worked without any issue.

Thanks @Squid I'm looking for a way to send only emails, especially with attachments of script logs etc. I use Pushbullet for my notifications, and I was hoping I could invoke email as a separate thing, as that would be ideal. Do you know if its possible to setup a config for using ssmtp/sendmail? It seems to half work.