Kung-Fubick

Okay, thanks for the fast answer, I have updated now and will monitor the server. I'm honestly unsure if I mean crashes. I followed the guide on how to gather information about an unclean shutdown. But every time it seems to happened (can't reach any of my docker containers webui, nor the webgui, no smb shares) it won't do a clean shutdown when I only press my power button. I always (when the server is crashed) have to shut it off by "unclean" means (force reboot)

Hi, I am also having a pretty high amount of unclean shut downs lately. I have enabled the syslog server and found the errors in the following zip file. I am not sure if it is a hardware failure or some incompability. I would really like some help to stabilize my server. tower-syslog-previous-20241102-1513.zip

Looks like I won't be able to, in the attempt at resolving this I managed to crash my Unraid by adding (what I can only assume) was an incorrect vpn configuration. I think from now on I will have to do it the VM way, or only run arr applications without a VPN and just have the torrenter behind a VPN.

Hi, I can't figure this issue out no matter how much I google and try so I will try posting here. Currently I am running multiple docker containers behind a VPN tunnel (wg0) setup with unraids VPN manager (using a mullvad config) and all of that works great when I am on my physical network: I can reach each webUI by accessing my NAS LAN address with port number (10.0.1.25:7878 for example). However when I try to access these docker container by going through my unraid tailscale IP (100.50.50.50:7878 for example) it can't connect if the container is using wg0 but I can reach it if it uses br0 (default bridge). So I have tried adding a subnet route in tailscale to where my VPN ip pool is (10.10.10.0/24) without any success.

So I got this message under common problems for the first time after using unraid for a bit over 2 years: "Your server has detected hardware errors. The output of mcelog has been loggeg. Post your diagnostics and ask for assistance on the Unraid forums". I am not sure where to start but posting diagnostics here in the hopes that someone will be able to help. nas-diagnostics-20240108-0009.zip

Looks like that did the trick. Thank you for your help @JorgeB! Sometimes the simple solutions are the best ones.

Okay, I guess I could try a 2nd GPU. Because I have tried it with the older AMD GPU and it's still the same result. Will return once I have tried with a 2nd GPU.

Well neither does the 3600 but it should still give an output for the bios, right?

Hi, this is not strictly an unraid issue but the community has been very helpful previously. I have an unraid build with a b450f motherboard and a AMD Ryzen 9 5950X. I am however unable to get any type of output signal from it. It boots up unraid just fine and I was able to get an output on my older AMD Ryzen 5 3600 which I used in this build before switching CPU. Now I need to change bios settings because they reversed after I switched processors, but this is impossible because I can't get a HDMI/DP signal from the server. Any help is greatly appreciated. I use to have an old AMD GPU which I have now taken out to see if it would make a difference but nothing has changed.

Hi, I am unable to access my unraid webgui from the browser. I tried booting unraid into GUI mode and logging in there but I was unable to reach it from there as well. The array is currently not started since I use encryption and start it by manually entering the key from the webgui. So no VMs or docker containers are currently running. This came after a reboot. What I did before rebooting was setting the ACSI override setting in VM manager from "both" to "disabled". The unraid usually runs a pfSense VM as my primary router and a static IP 10.0.1.25. As of the reboot I am have an old router which has DHCP enabled and runs on the same subnet. I don't think it's an issue with the router since I can't access the webgui while booting in GUI mode. This is the only time I have done this and it opened a web browser with the address "localhost" which could not be reached. I have no idea how to fix this issue. EDIT 1: I switched the port of the UNRAID Usb bootable drive and now I can access the webGUI from booting into GUI mode. The odd thing is that it says all of my drives are missing and it has changed name from "NAS" to "TOWER". Have I managed to accidentally pass through my sata drives? Or does anyone have any idea what I can do to fix this? I still can't access the webgui from personal computers but that might be a routing error for all I know. EDIT 2: Seems like everything is working correctly after I switched back to "Both" on the ACS override in VM manager. "Multifunction" seems to work as well. The original problem seems to have been switching this setting and switching where the USB bootable drive is when trying to figure out what was wrong from start.

I will keep trying a bit and see if it gets me anywhere. Yeah those prices are truly insane, got the card to be able to run a mac vm with linux and windows. I do have a nvidia gpu that currently occupies my workstation so I might get a new card and put the old nvidia card in for ubuntu and windows. Then try with the R9 for the mac. Big thanks for all the effort you put into helping me anyway!

Oh well that's a bummer, tried with the ubuntu VM aswell. Screen went black and gpu fans maxed out so had to reboot anyway. So if I would use this card I would have to reboot host every time I shutdown the VM? Also is there any easy way to find out which cards that are supported?

Getting some display output, was into the "repair windows screen" which I was able to click around in once I forwarded the USB controller. Tried reinstalling windows and it all went fine until some type of crash when screen went fully black. This was when I had finished installing and was browsing in the OS. And all of this happened after I added the vbios. However right now when I start either Windows VM (created a new one to reinstall windows) it freezes while booting. Getting the windows "ring" of loading and the TianoCore picture. Going to try again and see if I did something wrong after installing windows. I did install a display driver that might have been intended for VNC (followed an old spaceinvader video). Attaching another diagnostics if it is of any interest. nas-diagnostics-20211022-1513.zip

I have the spaceinvader script for it so I will use that. Will update after.

Removed the USB controller and replaced the ealier gpu section with the one you wrote. Recognize that part from spaceinvaders video. I didn't change anything else in the VM. It still starts after the changes but I still get a black screen. Attaching diagnostics after trying to start the VM with configurations. Here is the output of the lines you provided me with: for iommu_group in $(find /sys/kernel/iommu_groups/ -maxdepth 1 -mindepth 1 -type d);do echo "IOMMU group $(basename "$iommu_group")"; for device in $(\ls -1 "$iommu_group"/devices/); do if [[ -e "$iommu_group"/devices/"$device"/reset ]]; then echo -n "[RESET]"; fi; echo -n $'\t';lspci -nns "$device"; done; done IOMMU group 17 [RESET] 02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) IOMMU group 7 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU group 25 [RESET] 09:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] IOMMU group 15 01:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller [1022:43c8] (rev 01) IOMMU group 5 [RESET] 00:03.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU group 23 [RESET] 08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] [1002:6939] (rev f1) IOMMU group 13 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1440] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1441] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1442] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1443] 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1444] 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1445] 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1446] 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 [1022:1447] IOMMU group 3 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU group 21 02:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) IOMMU group 11 [RESET] 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU group 1 [RESET] 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU group 28 [RESET] 0b:00.1 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486] IOMMU group 18 02:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) IOMMU group 8 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU group 26 [RESET] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a] IOMMU group 16 01:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge [1022:43c6] (rev 01) IOMMU group 6 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU group 24 08:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Tonga HDMI Audio [Radeon R9 285/380] [1002:aad8] IOMMU group 14 [RESET] 01:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller [1022:43d5] (rev 01) IOMMU group 4 [RESET] 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU group 22 [RESET] 03:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) IOMMU group 12 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) IOMMU group 30 0b:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] IOMMU group 2 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU group 20 02:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) IOMMU group 10 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU group 29 [RESET] 0b:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU group 0 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU group 19 02:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) IOMMU group 9 [RESET] 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU group 27 [RESET] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] nas-diagnostics-20211022-1401.zip