iCarl

I recently upgraded to Unraid 7.0.0 from Unraid OS: 6.12.13, everything has gone smoothly with the exception of some Machine Check Events being detected on my server. I previously had similar errors and ran memtests with no issues really identified, I have not experienced errors in some time (4-5 months) and don't really see a negative impact to my server other than FixCommonProblems flagging this error. I've attached my diagnostics to this thread, I'd appreciate any help! Diagnostics-20250128-1106.zip

Attaching additional diagnostic logs post BIOS power supply idle change (since issues persist), I'm also mirroring to flash so hope there's something in these logs that may narrow things down! icarlnas-diagnostics-20240929-1826.zip

Appreciate the response @JorgeB, I ran a memtest that passed (acknowledging that this could still be the problem); I only have one stick of RAM so I could try purchasing another to swap it out. I recently purchased a new CPU, but issues persisted across both the old and new CPU. I also made sure that the Power Supply Idle Control is set to typical current idle via the BIOS. I have a AMD Ryzen 9 5900X in a ASRock AB350M Pro4 motherboard, would that topic still apply?

Forgot to preface my current Unraid OS: 6.12.13 The error cleared out of fixcommonproblems, but my server continue's to become unreachable randomly.

Any help would be really appreciated!

Fix Common Problems identified Machine check events detected on my server. I've been experiencing my Unraid sever freezing becoming unreachable and frozen when connected directly to it with a monitor. NAS-diagnostics-20240920-1952.zip

I've attached the syslog below, issues happened sometime between 10am - 10:30am on 12/24 Based on @Jryski's post, I may need to move away from bridging? I do have Ubiquiti and realtek gear, it sounds like I'm square in the middle of a few PRB's! I followed the first few recommendations here, but haven't moved all of my dockers off Bridge yet. syslog

My Unraid server has started becoming unresponsive, requiring a hard reboot to bring it back & sometimes multiple hard reboots. I initially thought it was a bad nic port on my motherboard and installed a fiber PCI card which worked fine for a day or two, but then issues persisted. Today I connected a monitor to the normally headless server and when it became unresponsive I logged in at the server where it looked normal. It then became responsive again after doing so. I've noticed other times where it'll be responsive, unresponsive for a short moment and show the array not started and the docker not running due to that, then the array starts and the docker also starts. I'm really hoping it's not a hardware issue, but would appreciate any help! I've posted diagnostics below. The last known issue happened 12/23 around 10pm-11:15pm. icarlnas-diagnostics-20231223-2311.zip

I noticed a lot of these in the logs: unraid kernel: atlantic 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) I followed this guide to add a config to my syslinux configuration and things seem to have improved!

unraid-diagnostics-20231220-2045.zipI seem to be having the same problem, can someone please help?

This also worked for me, thank you!

the connector on the disk itself. A heads up to others with the Fractal Node case, when sliding in the tray of HHDs be mindful of clearance with the power supply... it bent my Sata connector and snapped off one HHDs Sata pins.

Diagnostics attached, I know the drive failed because the sata port was damaged when doing maintenance on the server. Unraid-diagnostics-20220910-2227.zip

One of my data disks has recently failed, I have dual parity and would like to use of the two parity drives as the new data disk. Could I just remove the second parity drive and let unraid rebuild the failed drive on that? I'd like to make sure not to lose data so I'm asking here before doing anything.