BusterBrawls

Members
  • Posts

    9
  • Joined

  • Last visited

Converted

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

BusterBrawls's Achievements

Noob

Noob (1/14)

2

Reputation

  1. That was very helpful. Thanks. I enabled the syslog server and now have a better visual on system logs. What was looking like multiple bad disks, or maybe a bad HBA turned out to be a bad stick of RAM.
  2. sol-diagnostics-20210109-0946.zip Greetings, I upgraded my motherboard/ram/cpu and installed a new HBA and since Unraid has been somewhat unstable. I've noticed two issues: 1) Three or so times in the last 2 weeks the server will go completely unresponsive in middle of the night. The array will go offline and I'm forced to reboot with a hard reset. This happened last night. 2) Quite a few times in the last week I've woken up in the morning to find that Docker is running and some containers that should be running are not started. They will not start and throw a generic "server error" message. Other containers continue to run until I restart them. The only way to resolve that is to initiate a reboot from the GUI. I have attached is the system diagnostics I took this morning. And I am hoping someone will see something that I obviously missed. Notes: * I've been running Unraid for many years and have never done a clean rebuild. Maybe I have something "legacy" configured that's causing issues? * I'll say that this MSI motherboard (C246M-WU4) is finicky. Changes to the BIOS unrelated to USB will cause the usb disk to not boot and I get stuck in a boot-loop. I can't for the life of me figure out how to get into the LSI SAS 9300-16i controller firmware at boot time. * I tried upgrading to 6.9.rc2 then reverting back to 6.8.3. I am having a difficult time troubleshooting this one as I can't view any log files after a reboot. Tips for troubleshooting a problem like this would be helpful. Maybe someone will notice something obvious in the diagnostics that I have missed myself. Thanks for the assist. Bob *edit for clarification
  3. In fact, I do have a CA backup that starts at 3AM Monday mornings (Weekly). The containers usually restart after the backup and all others restart as expected. I'd be willing to believe this is responsible for one or two of the shutdowns. I'd also be willing to believe the switch to wireguard caused a couple issues until I got that updated. Looks like the issues are probably mine. The lack of restart is odd, but not necessarily a problem with the Docker image.
  4. At least three times in less than 2 weeks I have woken up in the morning and found that the Docker container had stopped. The last collection of logs (supervisord.log) before I restarted the container is here: 2020-11-09 02:54:30,752 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '44976' 2020-11-09 03:00:07,108 WARN received SIGTERM indicating exit request 2020-11-09 03:00:07,108 DEBG killing watchdog-script (pid 155) with signal SIGTERM 2020-11-09 03:00:07,108 INFO waiting for start-script, watchdog-script to die 2020-11-09 03:00:08,109 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22428397286640 for <Subprocess at 22428394042608 with name watchdog-script in state STOPPING> (stdout)> 2020-11-09 03:00:08,109 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22428397335984 for <Subprocess at 22428394042608 with name watchdog-script in state STOPPING> (stderr)> 2020-11-09 03:00:08,110 INFO stopped: watchdog-script (terminated by SIGTERM) 2020-11-09 03:00:08,110 DEBG received SIGCHLD indicating a child quit 2020-11-09 03:00:08,110 DEBG killing start-script (pid 154) with signal SIGTERM 2020-11-09 03:00:09,111 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22428393173920 for <Subprocess at 22428393173968 with name start-script in state STOPPING> (stdout)> 2020-11-09 03:00:09,111 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22428394041936 for <Subprocess at 22428393173968 with name start-script in state STOPPING> (stderr)> 2020-11-09 03:00:09,111 INFO stopped: start-script (terminated by SIGTERM) 2020-11-09 03:00:09,112 DEBG received SIGCHLD indicating a child quit I would be happy to provide (or capture) any other logs necessary.
  5. I can't keep qbittorrent open for a couple of days before it will eventually close on it's own. This is new behavior over the last couple of weeks. The only changes I've made to the configuration has been the updates for wireguard. Recently logged errors: "2020-11-09 07:35:11,796 DEBG 'start-script' stderr output: parse error: Invalid numeric literal at line 4, column 0" "2020-11-09 02:32:47,909 DEBG 'watchdog-script' stdout output: [warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed" *edit for spelling error
  6. I ended up buying a POS gpu to use as a primary. It's not ideal, but it works.
  7. I'm having trouble passing my nvidia 960 to my Windows 10 VM since I've upgraded my motherboard/cpu. This was working on my old motherboard/cpu (P8Z68-V PRO) with on-board graphics, but the new board (ASUS x299-Prime) doesn't have on-board video. I have a good 960 rom, but I'm left with an error 43 on the nvidia driver in Windows. The virtio drivers are installed as well as the QEMU Guest Agent. I have used VNC in my troubleshooting and have heard that might be a problem? Now there's 2 things worth noting. 1. I've been running unraid since early v6 and have upgraded through to current. I'm wondering if I have some old settings getting in the way? 2. Error 43 went away after a BIOS update and the GPU worked properly for a week! At about the same time the GPU passthrough stopped working again, Windows 10 had updated to build 1709 & I had opened up my case and moved my m2 drive from slot 2 to slot 1. The next time I started the VM, I got error 43. I've since moved the drive back. Re-flashed the BIOS, cleared all settings, & have reviewed all the BIOS settings multiple times. I've attached my system diagnostics, KVM template, and a recent VM log. I've gone through the forums, watched all of the videos on the subject from Spaceinvader One, and googled until I couldn't see straight any more. I just can't figure this one out. I might even try out, https://github.com/sk1080/nvidia-kvm-patcher. VM Log Windows 10 VM Template Troubleshooting: Disabled HyperV, removed all USB devices, tried different amounts of RAM. I have tried different append options in syslinux.cfg, but those didn't help so I went back to default. sol-diagnostics-20180220-2024.zip