Drillpin

Members
  • Posts

    20
  • Joined

  • Last visited

Recent Profile Visitors

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

Drillpin's Achievements

Noob

Noob (1/14)

2

Reputation

2

Community Answers

  1. Correction: I found out that my qbitorrent docker had too many active downloads for my system to handle. A funny side effect of this would be that parity checks would take an estimated 30-60 days to complete, and the rest of my containers would be very sluggish as well.
  2. Correction: I found out that my qbitorrent docker had too many active downloads for my system to handle. A funny side effect of this would be that parity checks would take an estimated 30-60 days to complete, and the rest of my containers would be very sluggish as well.
  3. @JorgeB Sorry I meant to post in here before. I found out that my qbitorrent docker had too many active downloads for my system to handle. A funny side effect of this would be that parity checks would take an estimated 30-60 days to complete, and the rest of my containers would be very sluggish as well.
  4. Updating Post for solution. I have swapped the motherboard out for another, and the crashing behavior has appeared to go away.
  5. Updating Post for solution. I have swapped the motherboard out for another, and the crashing behavior has appeared to go away.
  6. Thank you for the advice, and I already downgraded to 6.11.5. The same crashes would occur. I just don't know what hardware is the issue. Memtest runs flawlessly, and I wouldn't think intel 13th gen would not be supported.
  7. It heard me post that and immediately crashed again. I noticed the log didn't include the boot sequence, so I'll post another one down the line too. server-syslog-previous-20240124-0510.zip server-diagnostics-20240124-0010.zip
  8. I'll upload the next one, but I do have a historical instance. I'll post a new comment with the next one server-syslog-previous-20240119-1411.zip server-diagnostics-20240119-0911.zip
  9. My server becomes unresponsive every day. All the hardware tested fine. Might be a motherboard issue, but I do not know. server-diagnostics-20240123-1634.zip
  10. I'm running an hba card to interface with a SAS backplane, could that cause issues?
  11. I experience kernel panics everyday with my new unraid server. I have updated the BIOS and ran memtest already. The crashes happen somewhere between 15 mutes to 25 hours of uptime. I'm considering downgrading to a 6.9 release because I do not know what to do now. server-syslog-previous-20240119-1411.zip server-diagnostics-20240119-0911.zip
  12. Memtest finished running, and rather ominously, no errors to report.
  13. I'll grab that and run it this weekend and report back later.