DrHazard

Already done. Tried two different flash drives, one usb 2 and one usb3. Tried via usb creator, and manually building. Tried all ports on the server. Tried multiple versions. No dice It definitely seems like something hardware, but everything is testing fine, and other OSs have no issues. Only unraid

Hello friends, I made the mistake of rebooting my server today and now have had zero luck getting it back online. It either hangs or goes in to a boot loop. It is not consistent with where it fails in the boot process, and it's a 50/50 shot if it will reboot on it's own, or just freeze. No actual errors are shown on the screen. The one consistency is it has never made it past verifying checksum for the various BZ flavors. It often reboots before it even gets here, but it never makes it past this point. It will always reboot or freeze. Basic specs: - Ryzen 7 5700 - 32GB ddr4 RAM - Gigabyte b550 Aorus board Things i've tried: Rebuild flash drive. all flavors of safe boot Fresh drive with fresh install. tried various versions, used unraid usb creator, and done manually via both windows and linux Tested every USB port Minimal system, dropped intel GPU, HBA card, all sata ports. Currently down to just 1 stick of ram, and the usb stick. everything else not needed to post has been removed. Bios reset. Bios updated. Toggled all the usual troublesome settings, no overclock, no fast boot. Memtest 5+ passes. Tested with other known good RAM just to be safe Flash drive works in another machine. I can boot to windows or linux on this machine with no issues. Prime95 and cinebench pass. No obvious hardware issues detected. Only unraid will not boot I'm at my wits end since everything has been working fine for months until this reboot and everything seems to be functional on this machine. I would normally point to the CPU or MB at this point, but no other OS is having an issue. Any insight or other troubleshooting steps I can try would be greatly appreciated syslog is attached, but of course it only shows up to the first expected reboot. syslog

Hello friends, I have a drive in my array that has been throwing occasional read errors, and has a slowly increasing UDMA CRC error count. I've swapped sata and power cables, and even tried connecting the drive to a PCIE/SAS controller to rule out chipset, but alas the issues persist. I'm working on swapping out the drive but need to upgrade parity size first. My new parity drive is currently rebuilding, but of course is getting the occasional read error. Since these are CRC errors, i'm hoping that means it is being corrected and re-read, allowing for a proper parity rebuild despite the occasional error? Or is the new parity compromised and I need to find a way to replace the problematic drive first? Any advice is appreciated. Logs attached tower-diagnostics-20241212-1038.zip