Jump to content

Mistershiverz

Members
 View Profile  See their activity

  • Posts

    45

  • Joined

  • Last visited

 Content Type 

Posts posted by Mistershiverz

    Frequent Server Crashes and Segfault Errors

    in General Support

    Posted

    @Jarskyappreciate the feedback.
     

    Quote

    Also you updated the BIOS recently as your revision is from March 2024

    Yes amongst the troubleshooting and after running the memtest i did update the boards bios in hope that it would resolve some of the errors. 

     

    Quote

    I see in your logs you're running them at 4800Mhz; did you run them with XMP disabled (which IIRC is 3200Mhz)? 

    No this is worth a look but when in this board's bios i could not see any mention of the RAM using an XMP Profile.

    Hmm ok i may have to start looking at hardware replacements as all the feedback looks to be failing hardware.

    Frequent Server Crashes and Segfault Errors

    in General Support

    Posted

    @JorgeB @Lavoslav Thanks for the feedback. I'm beginning to share the same suspicion, but I want to understand these errors thoroughly before investing in new hardware. Is it safe to conclude that segfault errors are typically indicative of failing hardware?

     

    I've noticed that when I decrease the number of dockers running, the crashes happen less frequently. However, could this simply be because there's less strain on the hardware?

     

    Frequent Server Crashes and Segfault Errors

    in General Support

    Posted · Edited by Mistershiverz

    Hey everyone,

     

    I'm dealing with frequent server crashes and having a tough time figuring out what's causing them. When the server crashes, I'm left with no choice but to hard reboot it. Sometimes, the unRaid GUI remains responsive, but basic functions like stopping dockers or rebooting the server don't work or get stuck.

     

    I've been going through the server's syslogs and noticed some common errors, mainly segfault errors, whenever the crashes happen. After looking around this forum, I found that many people suggest running a memtest on the server's RAM when encountering these errors. I've already done this, and it didn't report any issues. I even tried replacing the RAM with new ones, but the problem persists.

     

    So far, I've tried:

    1. Running a memtest on the previous RAM, which showed no errors.
    2. Buying new RAM, but it didn't solve the issue.
    3. Removing all unRaid plugins except the essential ones (like CA Plugins).
    4. Disabling all Docker containers except for essential ones like Plex.

     

    Despite these steps, I'm still struggling to identify the root cause of the problem. I'm not sure if it's related to a specific docker/plugin, an unraid function, or failing hardware. Any advice or insight into this issue would be greatly appreciated.

     

    I've attached the server's diagnostics and a couple of recent syslogs showing the common errors I'm encountering.

    Thanks in advance for any help with this issue.

     

    tower-diagnostics-20240421-0738.zip syslog.txt syslog2.txt

    syslog-previous.txt

    Unable to create Cache Pool after update to 6.10

    in General Support

    Posted

    Hey Team

     

    I am unable to create a cache pool after updating to 6.10.3 coming from 6.8.3.

     

    I have selected the "Add Pool" and once i have created the pool i get no option on the UI to add my previous cache drive.

     

    I can see my SSD as a unassigned drive but without being able to create a pool i cannot assign this to a cache pool.

     

    Im getting no error or output on why i cannot create a pool so any help would be appreciated.

    ironmike-diagnostics-20220806-0816.zip

    Errors in Sys Log, Docker stopping with BTRFS error (device loop2)

    in General Support

    Posted

    Hi @trurl

     

    I cannot recall why the docker.img has been set to 40G as this server has been running well for a good couple of years now but i will get that changed when i rebuild the .img

     

    I rebuilt the .img about 5 days ago and everything has been fine until today is there are partucular docker etc that i can look at that would be causing this issue or should i rebuild the .img and go from there?

     

    Again thanks for the help much appreciated.

    Errors in Sys Log, Docker stopping with BTRFS error (device loop2)

    in General Support

    Posted

    Hi Team

     

    Currently experiencing issues related to the errors below where i will login to my server and notice a couple docker containers have stopped and a few are hung. When trying to restart the Dockers i then receive the Execution 403 error on Start.

     

    I have had a look through the forums regarding this issue with it looking to be related to the Docker.img or a failing cache drive. I have gone ahead and deleted the Docker.img and rebuilt this a few days ago all was fine and the errors are present again.

     

    Can anybody help me with how to proceed or what is causing this issue is it the Docker.img or a failing drive that will need to be reformatted/replaced?

     

    Below is a list of errors i am receiving is the Logs and Diagnostics posted below:

     

    kernel: loop: Write error at byte offset 7824109568, length 4096.

     

    kernel: print_req_error: I/O error, dev loop2, sector 15281464

     

    kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0

     

    kernel: BTRFS error (device loop2): parent transid verify failed on 9361899520 wanted 9195 found 9104

     

     

    Thanks in advance for any help it much appreciated.

     

     

    tower-diagnostics-20200903-1916.zip

    [Support] Linuxserver.io - Ombi

    in Docker Containers

    Posted

    Hey Team

     

    I am having issues with Ombi using large amounts of memory at the moment it is using 4gb or ram is this to be expected as by the end of the day it will have used all 8gb of the ram in my system.

     

    I would just like to know if this is to be expected or if there is something wrong with my docker or if i have enabled some setting in Ombi to cause this issue.

     

    Any help would be much appreciated.

×
×
  • Create New...