Nanobug

I'll check on next reboot, just to be sure. I won't do it now though

Yeah, I can see that. But I'ver never enabled it on any servers. But I'll double check it on next boot. Changing C states and removing eco mode made it run for 2 days and 5 hours without issues. Thank you for helping out, both of you!

I don't run with XMP/DOCP/EXPO on my Unraid server at all. Never did. Thanks though So far it's at 31 hours, so it looks stable. But I'll give it tomorrow as well, just to be sure

So far so good. It haven't become unresponsive yet, and it just hit the 18 hours uptime mark. If this was the fix, it's really odd that it started becoming a problem 2 months after I upgraded it to 7.0.0 and the BIOS haven't been updated for quite some time.

I did have eco mode on my 5900X to save a bit of power. I don't need it to boost and all that, 12 cores is more than sufficient, and it's been running just fine for years until now. But I've disabled it now, and disablec the C state power savings. I'll let you know again in a day or two. Thank you so far!

At 4 AM CET it disconnected from the network. I'm pretty sure it's exactly at 4 AM, and that's oddly specific, but it could be a coincidence. I'll reboot it and get the diagnostics.

Tried a different bank now at a 3.X port, and so far it booted. I'll see if it stops working within the next 24 hours.

Just to try it in a different system, it's easiner in a VM for me.

Doesn't look like a RAM issue to me: I'll try a VM tomorrow, been a bit busy today. I'll let you know if it can boot on that

I've started the memtest now, I'll let it run for 24 hours and post the result. I'll try the other device afterwards, I think I've got an old NUC somewhere I can add it to, or just use a VM on my desktop and pass it through. I'll figure it out. I see I was a bit off on that. It's still powered on, but it's unresponsive in anyway. No SSH, no WebUI, even the local terminal is unresponsive. Network wise it also disconnects. I've tried 3 different USB ports, 2 of the USB2 and one of them USB3. I'll try another set as well, just to be sure. That'll be after the memtest since I've alreadt startarted it. I'll let you know tomorrow. Thanks so far guys!

I'm running Unraid 7.0.0 on it, and it's been running that for 2 months or so. Yesterday, I noticed the Unraid server was off, so I booted it and thought that was it. But this morning, it was down again, and I decieded to take a look. As the title says, it hangs on the "Verifying bzfirmware checksum". What I've done so far: Before I did anything, I copied all the files on the USB drive as a backup, just in case. Then I've verified the USB drive, which had errors accordingly to Windows when I checked it in that. After wards it reported no errors. The problem persisted. I tried this solution: Which worked, but was followed by a new error: rc.udev - Triggering udev events... Which I managed to fix by changing USB port. Later that evening, it crashed, and I checked the USB drive, and it had errors again, so I decided to replace it. It wasn't a new drive, but it didn't report any errors, so I went with it. I used Rufus to make it bootable, downloaded the zip files (decided to upgrade to 7.0.1 now that I'm at it), copied the files over and replaced the config files. Now, it's stuck on the "verifying bzfirmware checksum" again. I can't for the life of me figure out why I keep having issues. I'm starting to think there's a hardware error somewhere. Is there anyway I can see what the actual issue is?

There's a "Proxmox Backup Server" container that works even better

I wasn't sure, but thank you And sorry for my brainfart 😅

I missed a few words there 😅 When I exclude the disk and shrink the array, I guess my parity is going back normal, to take over if another disk fails then?

When I exclude shrink the array, I guess my parity is going back normal, to take over if another disk fails then?