jsspanjer

I was searching for ages before i found this. Thank you!!! My GUI was showing blank sections, terminal not working. This happens sporadically after weeks of uptime and only fix was a reboot. Now i an just ssh into the box and run these commands.

After the "typical current idle" setting there was no outage anymore.

I saw that you mentioned a specific bios setting in another post. I have a AMD Ryzen 9 5950X cpu and have never set this in bios. I just have made the change to "typical current idle"

Crashing is back. At trhis time i see something in the system log: Sep 25 14:37:32 titan kernel: microcode: CPU29: patch_level=0x0a20120a Sep 25 14:37:32 titan kernel: microcode: CPU30: patch_level=0x0a20120a Sep 25 14:37:32 titan kernel: microcode: CPU31: patch_level=0x0a20120a Sep 25 14:37:32 titan kernel: microcode: Microcode Update Driver: v2.2. Sep 25 14:37:32 titan kernel: IPI shorthand broadcast: enabled Sep 25 14:37:32 titan kernel: sched_clock: Marking stable (1581031478, 626371003)->(2252762862, -45360381) Sep 25 14:37:32 titan kernel: mce: [Hardware Error]: Machine check events logged Sep 25 14:37:32 titan kernel: registered taskstats version 1 Sep 25 14:37:32 titan kernel: mce: [Hardware Error]: CPU 3: Machine Check: 0 Bank 0: baa00000000d0135 Sep 25 14:37:32 titan kernel: mce: [Hardware Error]: TSC 0 MISC d012000100000000 SYND 4d000001 IPID 1000b000000000 Sep 25 14:37:32 titan kernel: mce: [Hardware Error]: PROCESSOR 2:a20f12 TIME 1695645423 SOCKET 0 APIC 6 microcode a20120a Sep 25 14:37:32 titan kernel: Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no Sep 25 14:37:32 titan kernel: pstore: Using crash dump compression: deflate Sep 25 14:37:32 titan kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd Sep 25 14:37:32 titan kernel: usb 1-6: new full-speed USB device number 2 using xhci_hcd Sep 25 14:37:32 titan kernel: hub 5-2:1.0: USB hub found Sep 25 14:37:32 titan kernel: hub 5-2:1.0: 4 ports detected Sep 25 14:37:32 titan kernel: hid-generic 0003:051D:0002.0001: hiddev96,hidraw0: USB HID v1.10 Device [American Power Conversion Back-UPS BX2200MI FW:378700G -302202G ] on usb-0000:02:00.0-6/input0 Sep 25 14:37:32 titan kernel: usb 1-11: new high-speed USB device number 3 using xhci_hcd Sep 25 14:37:32 titan kernel: usb-storage 1-11:1.0: USB Mass Storage device detected Sep 25 14:37:32 titan kernel: scsi host0: usb-storage 1-11:1.0 Sep 25 14:37:32 titan kernel: scsi 0:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6 Sep 25 14:37:32 titan kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Sep 25 14:37:32 titan kernel: sd 0:0:0:0: [sda] 60088320 512-byte logical blocks: (30.8 GB/28.7 GiB) Sep 25 14:37:32 titan kernel: sd 0:0:0:0: [sda] Write Protect is off Sep 25 14:37:32 titan kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 Sep 25 14:37:32 titan kernel: sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Sep 25 14:37:32 titan kernel: sda: sda1 Sep 25 14:37:32 titan kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Sep 25 14:37:32 titan kernel: floppy0: no floppy controllers found Sep 25 14:37:32 titan kernel: Freeing unused kernel image (initmem) memory: 1868K Sep 25 14:37:32 titan kernel: Write protecting the kernel read-only data: 18432k Memory related? or CPU?

Uptime 7 days 20 minutes Ok. i think it was configuration / software related. What I can think of: 1. Network configuration failed after 6.12.3. I did a lot of vlan related configs through the year. Maybe some settings lingered. 2. I used a Docker XFS image but recently formatted all cache drives to ZFS. 3. Configuration settings from 5.* onward that do not play nice anymore. Current fresh installed Unraid 6.12.4 is working great. I immediately saw that it boots to login prompt again on monitor. This did not work for me in years. Recreated all network from scratch. Docker is now not image anymore, but folder based. Config also recreated from scratch (as needed). So. I will hereby mark this post as "Solution". Thans for all input!

Uptime 1 day 20 hours 20 minutes

So. I have an extra usb drive (backup) which i erased. Installed fresh version of Unraid 6.12.4 on it. Only config i copied over are the minimum settings to do a parity sync to see if it stays up. From latest flash backup: /config/pools /config/shares /config/disk.cfg /config/share.cfg super.dat copied my second pro.key to it. Parity succeeded. Uptime 19 hours and counting. As far as i see it. No hardware issue. The original "master" usb is an upgraded Unraid installation from 2019. I will slowly configure this new usb to see if the server will continue to function.

Thank you for looking at the log. Will let you know if I find some other "culprit".

Installed the new power supply. RM1200 (1200W). Came to realize that the "old" power supply was 850W. It was the RM850i. So should have been sufficient. Booted the server up. Parity check started again at sep 7, 19:20 hours. Looked this morning and the server rebooted again at 4:20 ish. I am not seeing anything strange in syslog. Could someone please assist in looking at it? Latest image is from my telegram-bot notification. One thing to mention. Disk 1 is normally not used and is seen overheating when parity occurs. 51 degrees and drops again to 49 degrees. I have many more of the same kind. They are close together but only this one is 3 degrees warmer than the rest. Normally I do not use this disk. It was empty. I started doing Time Machine backups to it a couple of weeks ago. This morning, after I saw that the server still reboots, I disabled that and removed all files on it. syslog.zip media-01-diagnostics-20230904-0922.zip

I have ordered a new power supply. This time I bought the Corsair RM1200 shift. That's mostly overkill but will make sure that there's enough power. Hopefully that will solve the issue.

If I did not provide the logs everybody would want me to provide them. Now I provided the logs and nobody seems to do anything with them. There was only one download.

If I insert my Power calculations into https://outervision.com/power-supply-calculator I get a Load Wattage: 543 W So. That means that my current PSU is not capable of running that kind of max power. I currently have a Corsair RM550x 550 Watt 80 PLUS Gold Fully Modular ATX PSU. Hmmm.

Good idea. Thank you.

Hi. I get that. But. I have traversed this forum for years. I have never asked a question here. Every time someone posts a problem here, there's always someone who asks for syslog and diagnostics. I only see the syslog downloaded once. So it is not looked at. I myself am in the IT troubleshooting business. I am doing Windows. Unraid is a hobby. When something like this happens, I always look at wat was changed. I had an uptime of hundreds of hours before I updated to 6.12.3. Immediately after reboot the crashes happen. Mind you. It still could be hardware related. But it happened directly after installing 6.12.3. After that the crashes stayed. Degrading to 6.12.2 did not fix it. Upgrading to 6.12.4 did not fix it. I did a couple of memtest days (as asked) and tested my PSU (as asked). But still see 1 download of the syslog. 0 downloads of the diagnostics files I am not ruling out hardware but I am not Unraid minded enough to see if there's anything wrong in the syslog / diagnostics. Could please someone rule them out before I am buying new PSU? Or if anyone is kind enough to show me (a manual) how to read them.

So. Did a 10 pass memory test and test my PSU with a PSU Tester. Nothing wrong with them. Everything tests fine. Als did an upgrade to 6.12.4 with the recommended configurations for docker. Nothing solved. Still a crash after i start Docker and VM's. I have custom Docker networks on. eth0 and vlan configuration. Also reformatted my cache drives to zfs.