altyne

Members
 View Profile  See their activity

  • Posts

    13

  • Joined

  • Last visited

 Content Type 

Report Comments posted by altyne

    [6.11.5] Unraid crash (kernel: BUG: Bad rss-counter state mm:00000000f7646224 type:MM_SHMEMPAGES val:1)

    in Stable Releases

    Posted

    1 hour ago, Bebbo said:

    As the bug appears to originate within huge_memory.c, would it be worth turning off transparent huge pages and seeing if that cures the issue? There seems to be a lot of issues with hugepages at the moment and looking at the kernel forums there seem to be unresolved issues with splitting pages, particularly with Docker as it also uses hugepages if they are enabled.

     

    See this post for details on turning off THP - https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/?do=findComment&comment=21761

     

    Alternatively you could add transparent_hugepage=never to the end of your flash drive syslinux config (Main -> Flash -> syslinux configuration -> Unraid OS -> add to end of append statement 'append initrd=/bzroot transparent_hugepage=never')

     

    Currently it is disabled.hub.pages.disabled.png.a1d702b46ac4dde86c7fa1e2a5488883.png

     

    [6.11.5] Unraid crash (kernel: BUG: Bad rss-counter state mm:00000000f7646224 type:MM_SHMEMPAGES val:1)

    in Stable Releases

    Posted

    1 hour ago, JorgeB said:

    Call trace doesn't give many clues, at least not to me, if you can boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes could be a hardware problem, if it doesn't start turning on the other services one by one.

    all VM's are disabled . Only dockers instances are running. I cannot stop all dockers and sits for a whole couple weeks to observe since I use a lot of self hosted services. 

     

    This is also the dilemma I cannot pin point the root cause. 

    [6.9.2] Parity checking scheduling not working

    in Stable Releases

    Posted · Edited by altyne

    42 minutes ago, Squid said:

    Yes

    @Squid

    I know the reason. Just now we have  experience a brownout; it happens only a few seconds. Just now parity checking is running. During that time around 08:22:21AM , I didn't know we have a power outage and I was sleeping. Thanks to all. I need to protect my server with UPS since occasionally brownout occurs in my place.

    [6.9.2] Parity checking scheduling not working

    in Stable Releases

    Posted

    26 minutes ago, Squid said: 
    Jan  1 08:22:21 NightOwl emhttpd: unclean shutdown detected

     

    That cron setting is correct that's listed

     

    Dec 1st @ 2:30 am

     

    Since it's correct, and it's running at random times, it would appear that your system is randomly rebooting. (Confirmed by your diagnostics)  Maybe the system event log in the BIOS would shed some light on what's going on.

     I didn't shutdown my machine. Its running 24x7. That's the reason  the parity check was triggered?