October 31, 20241 yr I moved recently, and I'm trying to boot into Unraid in the new place and for some reason it no longer works. As far as I can tell, nothing changed in the configuration and it worked flawlessly in the old house. I noticed in the boot sequence an issue with the Nvidia plugin. A few days ago, after many failed attempts, I randomly managed to get into the OS and checked the Nvidia plugin control panel. It said the plugin was corrupted and prompted me to reinstall. I did and then rebooted. Unfortunately, since the reboot I cannot access the UI anymore. Not by plugging in a monitor directly or via the webUI. As such I can no longer download a diagnostics file. Looking at the boot sequence, it looks like the Nvidia plugin is still causing problem, but I can no longer access the UI to disable it. I've already tried to boot without the GUI and I've tried to boot into safe mode, but the results are the same. It looks like the OS tries to load the Nvidia plugin, even in safe mode somehow. I've managed to hook up a capture card to the server and record the boot sequence, hopefully this helps with diagnostics. In this particular boot attempt I try to boot into regular GUI mode, I manage to get to the log in screen, but the display quickly goes black and after a few minutes, the drive activity indicator lights on the front of the server go out as well indicating that the server has turned itself off. On subsequent attempts, the server behaves erratically. Sometimes the display doesn't even show the boot sequence, just a black screen until the server turns itself off. I'm sorry if I sound manic, I'm trying to completely document the servers behavior, along with all of my debugging attempts so far. Any help would be much appreciated, and I can provide additional information as needed. Thank you! 2024-10-31 00-54-48.mkv
October 31, 20241 yr Community Expert I would think the Nvidia driver would not load in safe mode, @ich777can you confirm? And if it does, what file(s) need to be renamed/removed to on the flash drive to not load it? In the meantime, try booting with a new flash drive using a stock Unraid install, no key needed, just to see if it boots normally.
October 31, 20241 yr 2 hours ago, SxC97 said: I noticed in the boot sequence an issue with the Nvidia plugin. Can you please specify what you mean exactly? 2 hours ago, SxC97 said: It said the plugin was corrupted and prompted me to reinstall. I assume you are talking about the Plugin section and that the Nvidia Driver was in an error state, so to speak in the Plugins Error tab correct? 2 hours ago, SxC97 said: I've already tried to boot without the GUI and I've tried to boot into safe mode, but the results are the same. It looks like the OS tries to load the Nvidia plugin, even in safe mode somehow. The plugins won't install in Safe Mode and also the driver itself won't be installed on boot. I assume you try to open the GUI directly on the server through GUI mode correct, or do you try it over the network from a foreign computer? Can you maybe try to not boot into GUI mode, let the server start, log into with your root account, type in `diagnostics`? This will put the Diagnostics on your USB Boot device into the /logs directory, please post them here. I don't suspect the Nvidia Driver plugin causing issues, since the driver itself seems to install fine and it also loads fine.
October 31, 20241 yr Author Hi there, thank you for the quick response. Quote I noticed in the boot sequence an issue with the Nvidia plugin. I didn't manage to get a screenshot, but it said something about not being able to load the Nvidia plugin. Quote It said the plugin was corrupted and prompted me to reinstall. I assume you are talking about the Plugin section and that the Nvidia Driver was in an error state, so to speak in the Plugins Error tab correct? The plugin tab just said that it was out of date. But the Nvidia settings pane in settings (the section that's added once you install the plugin ) said that the plugin install was corrupted. I hit install from there. Quote The plugins won't install in Safe Mode and also the driver itself won't be installed on boot. That's what I assumed, and this is why I was so confused 😅. Quote I assume you try to open the GUI directly on the server through GUI mode correct, or do you try it over the network from a foreign computer? I have tried both options, neither work. Quote Can you maybe try to not boot into GUI mode, let the server start, log into with your root account Wow, it looks like it worked! I booted into safe mode with no GUI. It didn't show anything on the display, but it did allow me to access the webUI and grab a diagnostics file. I've attached it here. tower-diagnostics-20241031-0356.zip
October 31, 20241 yr Author Also, looks like something went wrong after I got the diagnostics file and after a few minutes the server turned itself off. 🤷🏽
October 31, 20241 yr Community Expert 2 minutes ago, SxC97 said: Also, looks like something went wrong after I got the diagnostics file and after a few minutes the server turned itself off. 🤷🏽 This sounds like a hardware issue. My first thought would be that is either a PSU issue, or something like the CPU overheating and closing the server down.
October 31, 20241 yr Author Hmm, maybe you're right. I just rebooted into regular mode with no GUI. The server was stable for ~20 min, then it shut itself off. Maybe the CPU cooler got jostled loose in transit? I'll open it up and take a look and update back soon. I also have a second server that's exhibiting similar issues. It looks like it's stable when you boot into the OS with no GUI, but the webUI doesn't seem to work. I've already tried restarting nginx, but it doesn't seem to work. I've managed to get a diagnostics file and uploaded it here. Please let me know if it is appropriate to post here, or if I should open a new thread for this server. miranda-diagnostics-20241031-0351.zip
October 31, 20241 yr Community Expert Did you open up the server and make sure that all of the cards are properly seated and all of the cables are firmly plugged in? Then double check after you have done it the first time as rummaging around the inside of the case can easily loosen a cable adjacent to the one you are working with.
October 31, 20241 yr 3 hours ago, SxC97 said: Hmm, maybe you're right. I just rebooted into regular mode with no GUI. The server was stable for ~20 min, then it shut itself off. Maybe the CPU cooler got jostled loose in transit? I'll open it up and take a look and update back soon. You have a lot of hardware errors in your syslog: Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 514 Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: It has been corrected by h/w and requires no further action Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: event severity: corrected Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: Error 0, type: corrected Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: section_type: PCIe error Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: port_type: 0, PCIe end point Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: version: 0.2 Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: command: 0x0006, status: 0x0010 Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: device_id: 0000:63:00.0 Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: slot: 0 Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: secondary_bus: 0x00 Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: vendor_id: 0x1022, device_id: 0xb000 Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: class_code: 010802 Oct 31 03:18:27 Miranda kernel: {2}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x0000 It seems that these are related to your nvme drives: 63:00.0 Non-Volatile memory controller [0108]: Advanced Micro Devices, Inc. [AMD] Device [1022:b000] Subsystem: Samsung Electronics Co Ltd Device [144d:a801] Kernel driver in use: nvme Kernel modules: nvme Is this a new built system or did you change anything recently (Hardware/BIOS update,...)? Also maybe try to upgrade your BIOS if a newer version is available.
October 31, 20241 yr Author This is a new system. It has never worked properly unfortunately, it's always been a little erratic. This machine uses 4 nvme drives in a pcie card that came with my motherboard (https://www.amazon.com/ASUS-M-2-X16-Expansion-Card/dp/B084HMHGSP). I just double checked and it looks like I did not properly configure my bios to use these nvme drives as a raid 0. That might have been why Unraid was giving me errors and why the drives were showing up as 4 separate drives. I've just wiped the drives and configured them properly. Here is the new diagnostics file. Unfortunately, this still doesn't resolve the issue with the webUI. From the server's command line I can ping google and my laptop just fine, but from my laptop, I cannot ping the server. Perhaps this is a network issue? I double checked and it looks like the server and the laptop are both connected to the same network. The server via ethernet and the laptop via wifi. miranda-diagnostics-20241031-0736.zip Edited October 31, 20241 yr by SxC97
October 31, 20241 yr Community Expert You have an static IP address assigned to the server miranda as 192.168.0.4 Did you get a new router (or MODEM/Router) when you moved? Did you assign (or reserve) the Unraid server's IP address on your router? What is the base address of your router?
October 31, 20241 yr Author Yes, we received a new router and modem when we moved as we had to get a new ISP. I changed the new router's SSID, password, IP range, and reserved IP addresses to match the old network. If I recall correctly, the Unraid server's IP address was set when I created the USB drive, I did not assign the IP through the router. By base address, I assume you mean the IP address of the router? I ran netstat -nr | grep default on my laptop and ip route | grep default on the server and the address on both was 192.168.0.1 I also double checked and I can successfully ping the router via its IP address from both the laptop and the server.
October 31, 20241 yr Author I also checked my router's app and the server is not showing up in the list of connected devices. However it looks like my server can still ping the Unraid mothership as it shows up as being online on the Unraid Connect dashboard website.
October 31, 20241 yr Author I also looked into the NVME errors and it looks like this is a fairly common, but harmless error for Samsung drives. Link to Unraid support thread from 2022:
October 31, 20241 yr Author Ok, so I also managed to open up the first server, the one that kept shutting down randomly, and found that there was an issue. First I realized that I had a missing 4 pin EPS slot on my motherboard. The server had run fine for 3+ years so I didn't think much of it. I had some extra PSU cables so I plugged it in just to be on the safe side. The other problem was that the system was booting fine into GUI mode, but after a few minutes (maybe 10?) the red CPU light would come on and then the system would stop responding. I checked and made sure that the 24 pin ATX cables and 4 pin EPS cables were all correctly seated in both the PSU and the Motherboard. I also made sure the CPU cooler was plugged into the correct pin headers. The CPU cooler fan was running and the heatsink was warm but not hot to the touch, so I don't think it was a thermal issue. At this point, I'm assuming it's either a motherboard issue, or a CPU issue.
October 31, 20241 yr Author Good news! I updated the BIOS in the first system and everything seems to be stable now. It's been up for 3 hours with no erratic behavior. I think we can consider this server fixed. The issue still remains, however, of the second server (Miranda). It seems to be stable now, but I still cannot access the WebUI. Any help in resolving this matter would be much appreciated! Edited October 31, 20241 yr by SxC97
November 1, 20241 yr Community Expert Solution Try booting with a different flash drive using a stock install, no key needed, that will confirm if it's a confirm problem or a server/external issue.
November 5, 20241 yr Author Hi there, I finally managed to go out and buy a new flash drive and it seem like it's working fine. I'm assuming this is an issue with the initial flash drive. Should I just switch to the new flash drive or is there any way to fix the old one?
November 5, 20241 yr Community Expert You can try to backup and recreate the old one, or just replace it.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.