Jump to content
  • 6.6.2 - BUG: unable to handle kernel paging request


    vader75
    • Retest

    The system had gone into undefined state. It was accessible via GUI but docker was down and /var/log/syslog showed number of error when I tried to simply reboot the system (either via GUI or manually via reboot command from console). I have attached a snippet of error output.

     

    Not sure if this is a hardware issue that has developed or simply an OS bug. 

     

    Had a few instances where docker images would not start (rubbing is SSD cache) and had to reboot the box to clear this stalemate. Now I am a bit concerned.

     

    As I am not an expert, would somebody be able to identify if this is a genuine bug or I need to replace the system (given its old, mobo is from 2011).

     

    Thanks.

    bug_6.6.2_gk.rtf



    User Feedback

    Recommended Comments

    I jus realised there is 6.6.5 available, will give that a go as well. Still would appreciate feedback on issue.

    Share this comment


    Link to comment
    Share on other sites

    You need to update to the latest release and retest.  6.6.5 is current as of this writing.

    Share this comment


    Link to comment
    Share on other sites

    crashed again this time had to hard reboot. Hmmm, maybe hardware is going out. I will do more experiments. Maybe remove cache drive to test if its SSD(s).

    Share this comment


    Link to comment
    Share on other sites

    Just saw:

     

    Nov 23 09:12:31 VADER kernel: BTRFS warning (device sde1): csum failed root 5 ino 295563 off 2114744320 csum 0xc5bda441 expected csum 0x8963dcb1 mirror 1
    Nov 23 09:12:31 VADER kernel: BTRFS warning (device sde1): csum failed root 5 ino 295563 off 2114744320 csum 0xc5bda441 expected csum 0x8963dcb1 mirror 1
    Nov 23 09:12:31 VADER kernel: BTRFS warning (device sde1): csum failed root 5 ino 295563 off 2114744320 csum 0xc5bda441 expected csum 0x8963dcb1 mirror 2
    Nov 23 09:12:31 VADER kernel: BTRFS warning (device sde1): csum failed root 5 ino 295563 off 2114744320 csum 0xc5bda441 expected csum 0x8963dcb1 mirror 1
    Nov 23 09:12:31 VADER kernel: BTRFS warning (device sde1): csum failed root 5 ino 295563 off 2114744320 csum 0xc5bda441 expected csum 0x8963dcb1 mirror 2
    Nov 23 09:12:31 VADER kernel: BTRFS warning (device sde1): csum failed root 5 ino 295563 off 2114744320 csum 0xc5bda441 expected csum 0x8963dcb1 mirror 1
    Nov 23 09:12:31 VADER kernel: BTRFS warning (device sde1): csum failed root 5 ino 295563 off 2114744320 csum 0xc5bda441 expected csum 0x8963dcb1 mirror 2
    Nov 23 09:12:31 VADER kernel: BTRFS warning (device sde1): csum failed root 5 ino 295563 off 2114744320 csum 0xc5bda441 expected csum 0x8963dcb1 mirror 1
    Nov 23 09:12:31 VADER kernel: BTRFS warning (device sde1): csum failed root 5 ino 295563 off 2114744320 csum 0xc5bda441 expected csum 0x8963dcb1 mirror 2

     

    So could be cache drive(s) given out... 😞

    Share this comment


    Link to comment
    Share on other sites
    9 hours ago, vader75 said:

    So could be cache drive(s) given out...

    Not necessarily, one of the cache devices might just be out of syn, run a scrub and make sure there are no uncorrectable errors, you should also post the diagnostics.

    Share this comment


    Link to comment
    Share on other sites

    Also, please attach your full diagnostics with your next post.  Those are required for us to be able to assist.

    Share this comment


    Link to comment
    Share on other sites

    I did try the advice to scrub but that was not a fix. I did notice there were 50 uncorrectable errors on one of the SSDs.

     

    I have removed the SSDs and installed a few mechanical drives in place. No issues after this in the past few weeks. 

     

    Since fixing this would require investment, will wait for the new Samsung 860 to purchase and replace them in pair (getting cheaper).

     

    Until then, will contend with mechanical drives not giving me issues (albeit slower).

     

    Thanks for the help. I will open a new case if I get new failures.

    Edited by vader75

    Share this comment


    Link to comment
    Share on other sites


    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • 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.