Jump to content
  • [6.10.2] Massive performance issues / No array access / No dockers


    D.Romeleitis
    • Minor

    Hello,

     

    since 6.10-RC3 I have problems. With the stable version it is still the same :

    Sytem is up, Array is started.

    No network access to array possible. Dockers are not coming up.

    The GUI seems very slow (especially when there are network checks on it)

    Diagnostics can't be created (not via webUI or terminal on server).

    Terminal window over webUI shows "502 bad gateway".

    More informations can be found here https://forums.unraid.net/topic/124129-massive-performance-issues-since-610-rc3/

     

    Please help...

     

    Kind regards,

    Daniel




    User Feedback

    Recommended Comments

    I added the pci=noaer to normal and safe mode :
    image.thumb.png.47850913ca47d040c02fdd482a2693b5.png

     

    Now I will update from 6.10.0-RC2 to 6.10.2-RC3.

    Hope I will be able to run diagnostics. Last time it didn't work... This was only possible with 6.10.0-RC2

    Link to comment

    Updated...

     

    Dashboard site is loading very slow. After some minutes it is fully loaded. Is it a problem of one content of the site?

    image.thumb.png.725e64b72a4462825e8670745ac56308.png

     

    Main, USB, Shares, Users and Settings tabs are loaded quick.

    Plugin tab is loaded normal, but Status of plugings keep in "checking" state. 

    Docker tab is loading slow, after some minutes site is loaded, but all dockers seems to be stopped :

    image.thumb.png.d600483b139ad8ecae2298b5dba1c8a3.png

     

    Apps tab is loading very slow (Updating content). After several minutes content is showed. 

    Stats tab is very fast. Graphs are shown correctly. 

    Tools tab is very fast. 

    Downloading diagnostics is not possible. Tried it over WebUI and on console directly on server side. 

    image.png.a5d9cc78bf51b118c3a854124195dd8e.png

    Terminal in WebUI is not possible (502 Bad Gateway) 

    Accessing the Array over the network is not possible... 

     

    After the update 3 processes are using a lot of CPU 20220530_121709.thumb.jpg.c27480b518ebd8b4900841a71d0645e0.jpg

     

    I hope these information can help. 

     

    I remembered that long time ago I edited the go file with powertop settings :

    #!/bin/bash
    # Start the Management Utility
    /usr/local/sbin/emhttp &
    chmod -R 777 /dev/dri
    # load keyboard layout
    loadkeys de-latin
    # reduce power consumption
    powertop --auto-tune
    
    # -------------------------------------------------
    # disable haveged as we trust /dev/random
    # https://forums.unraid.net/topic/79616-haveged-daemon/?tab=comments#comment-903452
    # -------------------------------------------------
    #/etc/rc.d/rc.haveged stop
    
    # -------------------------------------------------
    # powertop tweaks
    # -------------------------------------------------
    
    # Enable SATA link power management
    for i in /sys/class/scsi_host/host*/link_power_management_policy; do
        echo 'med_power_with_dipm' > $i
    done
    
    # Runtime PM for I2C Adapter (i915 gmbus dpb)
    for i in /sys/bus/i2c/devices/i2c-*/device/power/control; do
        echo 'auto' > $i
    done
    
    # Autosuspend for USB device
    for i in echo /sys/bus/usb/devices/*/power/control; do
        echo 'auto' > $i
    done
    
    # Runtime PM for disk
    for i in /sys/block/sd*/device/power/control; do
        echo 'auto' > $i
    done
    
    # Runtime PM for PCI devices
    for i in /sys/bus/pci/devices/????:??:??.?/power/control; do
        echo 'auto' > $i
    done
    
    # Runtime PM for port ata od PCI devices
    for i in /sys/bus/pci/devices/????:??:??.?/ata*/power/control; do
        echo 'auto' > $i
    done
    
    # Disable wake on lan
    for i in /sys/class/net/eth?; do
        ethtool -s  $(basename $i) wol d

     

    Edited by D.Romeleitis
    Link to comment
    3 hours ago, D.Romeleitis said:

    Now I will update from 6.10.0-RC2 to 6.10.2-RC3.

    Hope I will be able to run diagnostics. Last time it didn't work... This was only possible with 6.10.0-RC2

    Why would you want to use the rc3 release when the Stable version (which supersedes it) is available?

    Link to comment
    2 hours ago, itimpi said:

    Why would you want to use the rc3 release when the Stable version (which supersedes it) is available?

    I tried the stable 6.10.1. And now next version 6.10.2-RC3.

    I have always the same effect since 6.10.0-RC3. 6.10.0-RC2 was the last version where I had no problem. Something must have been changed from RC2 to RC3.

    Link to comment
    3 hours ago, trurl said:

    Use the stock go file

    Stock is the go file I posted without everything starting with : ?

    # -------------------------------------------------
    # powertop tweaks
    # -------------------------------------------------

     

    Link to comment
    3 minutes ago, D.Romeleitis said:

    I tried the stable 6.10.1. And now next version 6.10.2-RC3.

    I have always the same effect since 6.10.0-RC3. 6.10.0-RC2 was the last version where I had no problem. Something must have been changed from RC2 to RC3.

    As far as I know there is no rc3 for 6.10.2

     

    3 minutes ago, D.Romeleitis said:

    Stock is the go file

    Only this:

    #!/bin/bash
    # Start the Management Utility
    /usr/local/sbin/emhttp &

     

    Link to comment

    Oh my god... I found the solution...

     

    I was getting out of ideas so I tried some other things. First I wanted to update the BIOS of the mainboard.

    I got stucked several times when I wanted to do it via QFlash. Every time I selected the USB stick (tried a lot...) it hanged up. I remembered that Gigabyte can be updated with QFlash Plus. So I had to remove everything from the mainboard (Memory, CPU, NVMe, HDDs, Grapfic Card). Then put the USB stick in the Flash Port (marked white at the backplate). The firmware file have to be renamed from e.g. W480MVISIONW.F21 to GIGABYTE.bin. After the flash it came up with Version F21 (I had F20 before).

     

    During the first restart I recognized that there was some error messages with network. SO I restarted with GUI.

    Here it came up, everything was fast, but no network connection.

    Next I remembered that there are 2 network ports on the board. 1 x 1Gbit and 1 x 2.5 Gbit. Since BIOS update I always used the 1GBit port(everything was fine since 6.10.0-RC2). So I tried to give the other port a chance...

     

    And bam... Now it is working fast like RC2 and before. So I finally updated from 6.10.2-RC2 to stable 6.10.2.

     

    I suggest that there was some kernel update from RC2 to RC3 and up which activated the 2.5GBit port and did some crazy stuff with 1GBit port.

    Link to comment


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