dfdonea

I downloaded and extracted the .zip file straight from the manual installation section in the guide. I forgot to run the batch file though. After running it, UNRAID OS finally loads! Is there any underlying reason which could have been the cause for UEFI not working?

I just tried this and it loaded into something but there are just a bunch of error messages. It says "Drive is too large to handle, using only 1st 8 GB" and then ends by stating "illegal partition table". Also, it says FreeCom version 0.86 before giving me a place to enter commands on a C drive?

I just attempted a format with Rufus using settings from a post that JorgeB replied to a year ago, then attempted a manual install. Still no luck. SHould i try legacy mode with CSM enabled and have the Batch file run on the drive? Also, will I need to add a dash to the EFI folder when I attempt this as well?

No, I had used the Unraid creation tool and done it manually with windows format but I haven’t used Rufus. trurl recommended I try legacy boot first but I can try both when I get back home.

That is how I have it now but it wasn’t working. Here I am just asking how to do it trying in legacy

I don’t believe this is the issue because it booted on a different system fine. I can try though. Will I have to do the manual install afterwards or no?

I think I did but I am not sure if I did it correctly. Do I need to enable CSM and add a dash to the EFI folder? Or just enable CSM and try that way?

It booted up instantly on a different System with a 9800x3d and MSI B850i with 2x16 G. SKILL CL32 6000 MT/s memory. I am not sure where to go from here since I already verified the memory working in the other system and the motherboards are both MSI.

Yes I was able to boot with memtest and had no fails in the test. I also can get to windows. I am not in a spot now with a computer other than this system. I can try when I get to another one. If it boots to another system, what should I try on this one?

I tried this yesterday on the 2.0 flash drive. I just tried it on a 3.0 but it seems to yield the same result even on 7.2.2 instead of the latest release.

I ran the system with memtest 86 and it passed but still no luck. I also tried a new 3.0 micro center usb which worked on the system I already use. I am already on the newest version of BIOS for the motherboard. What should I do next?

I am away from the location where the server is at now but I will test that in the morning when I am back

There is a monitor attached. It is just a blank screen. I already have no dash on the EFI folder. It didn't have one to begin with. I also have tried to use WEB GUI from the address/name.

I spend today building a new UNRAID server but could not get it to boot into UNRAID although I believe I have the right settings enabled in BIOS. It has all new parts which I'll list below. AMD Ryzen 9 9900x MSI X870E-P WIFI AM5 Motherboard DDR5 6000Mhz CL36 Crucial 2x16gb memory 3 16TB Toshiba N300 7200RPM Crucial P310 1TB Gen 4x4 NVMe I booted into BIOS fine and used only UEFI as recommended for modern systems. I also tried all ports with both a 3.1 Sandisk and a 2.0 Lexar USB drive (both 32gb) and I used the make_bootable batch file after all he motherboard USB ports did not work. I could not find an option for fast boot in the bios but I don't know if this would be the problem. Furthermore, I was able to launch into Windows Installation Media so I don't believe it was a hardware issue. Where should I go from here to continue troubleshooting?

Done now. Can't really test this because I haven't been able to replicate issue in my own. Seems to happen every week or so; will update in ≈ 2 unless it happens sooner

Revisiting this now. Server crashed again this morning at 11:58 EST. New 1000W power supply installed which is overkill. All components minus CPU/cooler and NVMe have been changed as well. Not sure if CPU is thermal throttling; the pairing is a 7800X3D with a Thermalright Peerless Assassing, which should be fine or so I thought. Could it be something in Bios perhaps? IOMMU is on but not sure if anything else needs to be changed. Full Specs: AMD Ryzen 7800X3D 32 GB G. Skill DDR5 6000mt/s CL32 memory Nvidia Quadro P4000 1000W Corsair Power Supply 1TB 980 Pro PCIe 4.0x4 NVMe 1x18 TB Toshiba NAS drive 2x16 TB Seagate NAS drive Like I said, EVERYTHING has been swapped except for the NVMe and the CPU/CPU Cooler. No components over a year old either. Not sure where to go from here.

Seems like nothing is going on now that it is doing the parity check. Will update once the docker is started and GPU is used and whether I will buy a new PSU.

Recently upgraded my server which had no GPU to having a PNY P4000 for Plex docker hardware transcoding. After installing the drivers as a plug in and disabling/enabling them, the server would power cycle and come back on after around 20 minutes of up time. This happened a few time and now the server is doing a parity check while I haven't opened any dockers or VMs today. From what I gathered, I believe it may be a power issue seeing as nothing else in the system changed even though I have a 750W power supply for only 3 hard drives, the P4000, and a 7800X3D. Before buying a new one I wanted to ask here if there is something else that could possibly be wrong. I also attached the syslog file to this topic. Thanks syslog2.txt

Got it. Started VM and seems to be working fine now; didn't launch Firefox but I will look into it again if it crashes. Thanks for your help.

Currently remoting into my home system to check on it. VM is running now but reluctant to open browser. I might try Edge instead of Firefox first then a new VM later tonight if that still reboots. If it isn't the VM, then what hardware is typically the cause of the issue in this circumstance?

It was my understanding that when you said reboot the server was back up and running again. It was essentially a shutdown though, as it did not come back online. Sorry for misunderstanding, still new to this. I didn't think it was a hardware issue because this only happened whenever I did something specific in a VM syslog1.txt

I attached both of what you mentioned. The server was not rebooting by itself. I had the VM running for over a day at the point where everything stopped working. Everything was still on as well inside of the server, no motherboard lights or anything of the sort. And like I said the VM would only fail and shutdown the server whenever I opened a browser and attempted to make a search. Other apps inside of the VM working fine. VM is off now and Plex docker is currently running as it should be. Only issue is the VM homenas-diagnostics-20241121-1024.zip Syslog.txt

I'm a new Unraid user as of last month and only recently installed a VM a few days ago. I'm currently using Unraid Version 6.12.13 and I have a Windows 11 VM which I torrent on, so I am constantly leaving it running. I have allocated 2 cores, 4gb RAM, and 200GB of disk space from my cache drive to this VM and it had been working fine until yesterday. I got home from work, and it was working fine so I locked my home computer and worked for a few hours on a microwave install. Upon coming back and checking on the VM, I noticed that I couldn't connect through VNC and that I couldn't even connect to it through browser to check if the VM was running still. I ended up shutting down the server and rebooting it but that didn't fix the problem. I had to boot into BIOS and boot into the boot flash drive manually. After doing this I was able to access the server but had to restart the array and do a mandatory parity check. I then started my Plex docker app and my VM and gave it some time to work. VM seemed to be working fine at first, but the moment I opened up Firefox browser, the whole server crashed again and the screen displaying from it showed my motherboard manufacturer's splash screen with no other pop-ups to boot into BIOS or otherwise. Server was again inaccessible after this. Is this a known issue with Firefox or completely unrelated? Other apps in the VM seem to be working fine, haven't tried any other browsers, but my torrenting app and VPN seem to be working regularly. Currently sitting at work after last night powering the system down and rebooting through BIOS; server is currently going through parity check.