Jump to content
  • 6.12.10 Keeps Crashing every 4-8 hours


    wbhst83
    • Urgent

    There have been no recent hardware or configuration changes. Has been a stable host for many years now with regular uptime of 30-60 days with the mainatnece reboots from time to time. Also, on battery backup, there are no sudden power drops. I have been running 6.12.10 for a little bit now but now lose the host every 4-8 hours for unknown reasons. I have been mirroring syslog to flash, and there is no evidence of why there. The network keeps responding to pings, but the web UI, dockers, SSH, and direct console access are unresponsive. I'm not sure where to look now. I am going to likely downgrade to 6.12.6. 

    nas-diagnostics-20241010_1633.zip




    User Feedback

    Recommended Comments

    JorgeB

    Posted

    Downgrade back to the previous release you were using and retest, it could for example be a new hardware issue.

    wbhst83

    Posted

    I upgraded to 6.12.13, as I had not noticed that it had been released and marked stable, to see if things would improve. About 6 hours later, I lost the host with the same issue, and no faults I can find in Syslog. I realize it might be a new hardware issue, but I am looking for suggestions or clues on where I should start. I am uploading new dialogs from the recent reboot.

    nas-diagnostics-20241011-0808.zip

    itimpi

    Posted

    The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot.   It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.

    wbhst83

    Posted

    Yeah, the mirror is already enabled and not capturing any panics / traces that point me anywhere. Today I booted into safe mode (no plugins), and only ran a limited set of dockers (to keep my network services alive), and then on the console ran tail of syslog running nonstop. It died again; there was nothing in the syslog of concern on the screen. I could ctrl-c to a console, but no commands would run. However, I saw my server prompt. I could not open any logs or top. Hard rebooted and ran a memtest for the evening. It's 35% through, and no errors thus far. The second diag above, was captured with the mirror already enabled.

    wbhst83

    Posted

    Five MemTests passes passed with no errors. I have gone ahead and booted the server in safe mode without plugins, started the array, and started a parity check with dockers off. I will see if that causes a crash.

    wbhst83

    Posted

    The parity check finished fine without errors. I moved the boot disk to a new USB, which booted normally. Started a limited set of dockers. I will report the next crash when that occurs.



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...