Jump to content

Drillpin

Members
 View Profile  See their activity

  • Posts

    20

  • Joined

  • Last visited

 Content Type 

Everything posted by Drillpin

  1. Drillpin
    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. Drillpin
    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. Drillpin
    @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. Drillpin
    Updating Post for solution. I have swapped the motherboard out for another, and the crashing behavior has appeared to go away.
  5. Drillpin
    Updating Post for solution. I have swapped the motherboard out for another, and the crashing behavior has appeared to go away.
  6. Drillpin
    Changed Status to Solved
  7. Drillpin
    ¯\_(ツ)_/¯
  8. Drillpin
    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.
  9. Drillpin
    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
  10. Drillpin
    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
  11. Drillpin
    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
  12. Drillpin
    I'm running an hba card to interface with a SAS backplane, could that cause issues?
  13. Drillpin
    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
  14. Drillpin
    Memtest finished running, and rather ominously, no errors to report.
  15. Drillpin
    I'll grab that and run it this weekend and report back later.
  16. Drillpin
    I tried to run memtest from the boot menu earlier and it would power reset the server and send me back to the boot menu
  17. Drillpin
    Initially before I set up the array I performed 2 passes through asus's bios. I plan on doing it again if nothing else comes up.
  18. Drillpin
    Accidently double posted my bad server-syslog-20240109-1709.zip server-diagnostics-20240109-1710.zip server-syslog-20240108-1434.zip
  19. Drillpin
    I have set up a new server to automate alot of tasks I used to perform on my desktop, and I decided to go with unraid as the OS. It's my first time ever dealing with Linux, so interpreting the logs is like translating a different language. For troubleshooting I have already changed my usb drive, disabled fast boot and XMP, and turned off virtualization. The server hangs have existed since I initialized the server. can anyone point me to what I should do to stop these hangs?
×
×
  • Create New...