Loki_C

Tried that already, same problem. I was able to get pass that "Triggering udev events:..." by downgrading back to 6.12.6 but as soon as it got to the login screen, the server kept rebooting itself. I also noticed during the boot sequence one of the messages was something about " [Hardware Error]: CPU 0:..". Anyways I ended up buying another replacement CPU (EPYC 7532) and I was able to boot back up into Unraid without any issues.

Hello, I'm unable to get my server to boot up. The system is rebooting itself on start-up and it's happening when it displays the "Triggering udev events: /sbin/udevadm trigger --action=change". It was working fine until Saturday morning (3/9/24), since then it's been down. I've tried resetting the BIOS back to default, unplugged all the PCIe devices including my HDDs. I even tried creating a new Unraid USB stick same issue. Did a memtest86 and it passed it. I plugged in a spare Windows OS SSD and that booted up fine. I also run prime95 for about 2 hours and no crashes. If I check the SMBIOS Event Log (On the Supermicro H11SSL-i), it shows CPU failure as the error when Unraid reboots itself during the start-up sequence. But I don't think it's the CPU as I was able to boot up fine in Windows and didn't crash during the prime95 stress test. I even bought a new motherboard Supermicro H12SSL-i but same issue (Nothing plugged in except for the USB), it restarts itself on the "Triggering udev events: /sbin/udevadm trigger --action=change". But this time if I check the SMBIOS Event Log, it doesn't show any CPU failure message on that board. Booting with the Safe mode option also reboots the system. Hardware: AMD Epyc 7532 Tested on both Supermicro H11SSL-i and H12SSL-i 128GB RAM I hope someone can help me out. I'm really desperate at this point that I may buy another CPU to test it out... Thanks, Loki.