woozaa.

Hi trurl Thanks for your reply! Werent aware of this! Thanks! I will check asap since I cant remember. But most likely it is. I remember to do the setup as secure as possible to take care of any situations when I am not at home. But I was next to the machine several times when unRAID restarts. There was no power interrupt. It seems as if only the OS itself reboots (is this even possible?).

Hello unRAID Community Since a week now my unRAID server has strange behaviour. In random timeframes it seems to reboot itself and starts a parity check. When it kind of "freezes" all access ist lost, I cannot reach the web gui nor any running docker container. The system is just not responding and booting again. But not the full machine with a short power cut or full reboot, it seems to just restart unRAID. And then it starts the parity check again. No matter if I move the date of the check or anything - it always starts. The server will reboot at random occasions no matter if the parity check is ongoing or canceled, if docekrs are running or not or if plex is streaming a video. Completely random. The Syslog says: Sep 30 15:41:13 Jukebox kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA Sep 30 15:41:13 Jukebox kernel: ACPI: Early table checksum verification disabled Sep 30 15:41:13 Jukebox kernel: floppy0: no floppy controllers found Sep 30 15:41:13 Jukebox kernel: amdgpu 0000:07:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response status is (0x7) Sep 30 15:41:13 Jukebox kernel: amdgpu 0000:07:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4) Sep 30 15:41:13 Jukebox kernel: amdgpu 0000:07:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0 Sep 30 15:41:37 Jukebox rc.local: error log : /var/log/graphql-api.log Sep 30 15:42:08 Jukebox root: error log : /var/log/graphql-api.log Sep 30 15:42:18 Jukebox root: Error response from daemon: network with name br0 already exists Sep 30 15:42:18 Jukebox root: Error response from daemon: endpoint with name watchtower already exists in network br0 Sep 30 18:41:09 Jukebox kernel: mce: [Hardware Error]: Machine check events logged Sep 30 18:41:09 Jukebox kernel: [Hardware Error]: Corrected error, no action required. Sep 30 18:41:09 Jukebox kernel: [Hardware Error]: CPU:0 (17:60:1) MC17_STATUS[Over|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0xdc2040000000011b Sep 30 18:41:09 Jukebox kernel: [Hardware Error]: Error Addr: 0x000000068011c040 Sep 30 18:41:09 Jukebox kernel: [Hardware Error]: IPID: 0x0000009600050f00, Syndrome: 0x000004960a400902 Sep 30 18:41:09 Jukebox kernel: [Hardware Error]: Unified Memory Controller Ext. Error Code: 0 Sep 30 18:41:09 Jukebox kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD Sep 30 19:43:45 Jukebox root: Fix Common Problems: Warning: Docker Application immich has an update available for it Sep 30 19:43:45 Jukebox root: Fix Common Problems: Warning: Docker Application n8n has an update available for it Sep 30 19:43:45 Jukebox root: Fix Common Problems: Warning: Docker Application plex has an update available for it Sep 30 19:43:53 Jukebox root: Fix Common Problems: Error: Machine Check Events detected on your server Sep 30 19:43:53 Jukebox root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Sep 30 19:43:56 Jukebox root: Fix Common Problems: Other Warning: dynamix.unraid.net Support Updated ** Ignored Sep 30 19:43:57 Jukebox root: Fix Common Problems: Other Warning: Unassigned Devices Plus not installed ** IgnoredIt seems to display a CPU Error? Is this possible? Which is funny, because the error message is not before the reboot but randomly placed. I tried switching RAM modules but no change of behaviour. I attached two diagnostics with a few days inbetween. Can you see more than I do? I am very new to this kind of troubleshooting and I would appreciate any help. Thanks in advance Wooz jukebox-diagnostics-20250930-1943.zip jukebox-diagnostics-20250929-0105.zip

Thanks for the reply! May I ask what leads to the decision? Am I right with the L3 cache failure, hardware related? Greetings woozaa

Hello fellow Unraid Users I´m asking more experienced users and/or pros for help, since my journey just began a few months ago. I would appreciate any help or hints since I don´t know if i miss sth here. I am getting a MCE errors to above mentioned topic - on a pretty constant/daily basis. It only startet on June 10th and did not stop yet. I did not change anything regarding software/BIOS/hardware. The server is working fluently as of now and does not have any crashes. Jun 14 04:31:45 Jukebox kernel: mce: [Hardware Error]: Machine check events logged Jun 14 04:31:45 Jukebox kernel: [Hardware Error]: Corrected error, no action required. Jun 14 04:31:45 Jukebox kernel: [Hardware Error]: CPU:0 (17:60:1) MC17_STATUS[Over|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0xdc2040000000011b Jun 14 04:31:45 Jukebox kernel: [Hardware Error]: Error Addr: 0x000000065f50b900 Jun 14 04:31:45 Jukebox kernel: [Hardware Error]: IPID: 0x0000009600050f00, Syndrome: 0x0000019d0a400902 Jun 14 04:31:45 Jukebox kernel: [Hardware Error]: Unified Memory Controller Ext. Error Code: 0, DRAM ECC error. Jun 14 04:31:45 Jukebox kernel: EDAC MC0: 1 CE on mc#0csrow#2channel#0 (csrow:2 channel:0 page:0x69f50b offset:0x900 grain:64 syndrome:0x19d) Jun 14 04:31:45 Jukebox kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD Any tests made during setup 3 months ago were perfectly fine, nothing is overclocked or whatsoever. no power surges known, nor any power outages or sth else. as far as i can read the logs i see errors occuring related to L3 cache from the CPU. is this correct? can i assume this CPU is damaged and should be replaced? or do i misinterpret these lines and its RAM related? THX for any help! syslog.txt