chrishick

Thank you so much to JorgeB. It really was as simple as an update to the OS. Updated the OS and fixed the file system on disk 3 and things are running smooth for over 1 week now.

Really? I have no idea what a macvlan call trace is, but if it's as easy as a simple update you just made my day. I just updated to 6.12.13 we'll see what happens.

Unraid v6.12.4 ASUS TUF GAMING X-570-PLUS Ryzen 9 5900X 32gb ram I've been struggling with random lock ups on my server. Started a few months ago, was good for a few weeks or a month, happened again, now the frequency has increased to 12-24 hours. Based on the attached terminal screen I found some information indicating that it might be bad memory. I have recently installed 32gb more ram for a total of 64gb. The problem started before I installed the new ram, so I deduced that perhaps the old ram was going bad. I pulled the old ram leaving only the new sticks. The problem still persists, so I'm thinking it's not a ram issue unless I got incredibly unlucky and the new ram is bad also. It happened last night around 20:00-22:00. If you look at the attached syslog you'll see I rebooted at Nov 7 22:50:32. Looking at the log I see some BTRFS error for loop2, so I've got a problem with my docker image. Could that be the cause? I haven't rebuilt the image yet, but will do so today. The last message before it locked up (I think) is error: publish, 172: Connection reset by peer. Is that significant? I've attached the BSOD (black screen of death), syslog from my remote syslog server and the diagnostics zip. Any help would be greatly appreciated. ps, I'm working through some issues with array disk 3 sdi. It is currently unmountable. I've got a new drive to replace it with, but don't want to start a rebuild until I get this worked out. Probably not a good idea to crash during a rebuild of a disk. syslog.txt unraid-server-diagnostics-20241108-0546.zip