iankaufmann

A few months ago, I started having random reboots (sometimes complete shutdowns) on my 13900k setup. I set up a remote syslog and could never find anything in the logs when it would happen. Like others here I systematically replaced everything other than the CPU with the same result. It wasn't until trying to boot some other OSs I had laying around on other USB sticks that something caught my eye in the logs on boot... I think it was when I was booting PFSense. Anyway, the error was something about how Core 20 had some kind of fault. That got me searching around and finding all sorts of information about 13th and 14th gen chips degrading and going bad at an alarming rate. It seems that many motherboard manufacturers had pretty bad settings for these chips that were destroying them. I ended up disabling the e-cores in the BIOS and after that I had an uptime of 2 months again. Everything was completely stable as soon as I did that. Maybe something to look into? I just swapped out the 13900k for a 14900k this evening and I'm going to see if I can RMA the 13900k. I ordered the 14900k almost two months ago (same as the uptime I had up until today) and it's just been sitting. I put off swapping it out because while it seemed urgent at the time... it turns out that running the server with the e-cores disabled made no noticeable difference in my life and I wanted to see how long it would run without freezing/rebooting. It was nice having a working server again for a couple months. But I'm back up and running on the 14900k now with all cores enabled and hoping it doesn't happen again with this chip.

Just going through this now which led me to this thread. Unraid 6.11.5, just swapped my parity drive from 6tb to 18tb. When I booted up, I added the new parity drive to the empty slot and started the array. I started to search for something in another tab and the Unraid tab stole focus when the alert box popped up and I hit enter at the exact same time so it accidentally did the "Resend" option. Now I'm stuck with "Array Stopped * Parity-Sync 0.9% * stale configuration" at the bottom, but all Dockers and VMs started up and everything seems to be working even though the GUI doesn't agree. Guess I just have to wait it out now for a couple of days until this process finishes. I think everything is OK, but it's very unnerving when already doing such a big operation. Guess I should have updated the OS before I did this, but I've been otherwise very happy on 6.11.5 and didn't want to add other unknowns to the mix.