Dieter Koblenz

I've switched memory banks for ECC in the hope this would solve the problem. It doesn't. I've changed all components including the motherboard except for the drives. At this moment, I'm considering moving to another OS to see if it also crashes this often.

As a temporary solution, I've added a script to reboot my machine at 04 AM. This did prevent crashes for a couple of days, until this morning I had another (new) kernel panic. Unfortunately, I couldn't screenshot the debug screen this time: I did see the following message: rcu_sched stall. Nothing much so far to go on, but it's definitely driving me nuts.

I've uploaded a new syslog with several errors, I tried reboot from the command line but it failed. Edit: Never mind, I see it doesn't contain anything useful. syslog-127.0.0.1.log

This morning I found my syslog filled with this error: Dec 15 07:29:23 STARBASE nginx: 2021/12/15 07:29:23 [alert] 8124#8124: worker process 20337 exited on signal 6 I've closed some dockers for the time being, and the spamming stopped. I've seen people in this thread: with a similar problem and also kernel panics, so this might be related even though previously I didn't see this error anywhere.

Here's the syslog, though at first glance I can't find a problem just before the kernel panic. syslog-127.0.0.1 - kopie.log

Yes, I am doing a couple of memtest passes first and then I'll fire up the box again. I did enable the syslog server, but I need a remote recipiant to sustain it right? I think I did enable logging to a share as well.

I've been working with UnRAID for some time now, and I recently installed a new MB, CPU and memory. Before I had the occasional crash and never completely figured out why. Now I've got IPMI, I can view the screen and I seem to get a kernel panic. This happened three times now, at random intervals. I've disabled C-states in the bios (and via terminal) and the memory is running on it's design speed (conforming to the best practices tutorial). Temperatures are all within acceptable parameters. I've added my diagnostics file and the screenshot from the terminal. I am hoping someone can give me some pointers. starbase-diagnostics-20211212-1025.zip

Thank you, I managed to restore the disabled disk.

And here's a diagnostics report. starbase-diagnostics-20210606-1341.zip

I had a power fail, and on boot of unRAID I noticed one of my four disk array's was disabled and emulated. I ran a successful smart check, and would like to re-enable the disk. How can I? It's an xfs system, so per help files I started the array in maintenance mode and ran check on the disk involved. I got this result, but I'm clueless on what to do next. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 1 - agno = 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 1 - agno = 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.

Hi guys, trying my hands on Hackingtosh with Macinabox. I followed the instructions from the youtube guide and managed to get the system running with VNC. Second step was running it with a RX 570 card, which also works. I'm now stuck with either a boot screen without any USB passthrough, or the following screen when I passthrough my USB keyboard and mouse. I've haven't found a similar problem in this subforum, any hints? Same happens with a usb hub 3 pci passthrough.

Some feedback should be in order, after changing the stick to a different controller I haven't had any problems. The controller I used before still has my keyboard and mouse attached and doesn't seem to fail at all. I guess the motherboard is to blame then.

I've tried this, however I always get the following error: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. I've bound the graphics/audio part of the card to my VM, but that's required to boot the VM. Any hints to get this working?

I'll use a different controller, it's a rather new motherboard. I'll see if I can find a tool to extensively test this. Before unraid I ran Win 10 24/7 without USB problems. It seems my mouse is connected to the same controller.

And with the third usb stick, seemingly undamaged, it happened again a couple of times. The latest diagnostics zip is attached. starbase-diagnostics-20210318-1326.zip