• Unraid OS version 6.9.0-rc2 available


    limetech

    As always, prior to updating, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

     

    Hopefully spin-up/down sorted:

    • External code (docker containers) using 'smartctl -n standby' should work ok with SATA drives.  This will remain problematic for SAS until/unless smartmontools v7.2 is released with support for '-n standby' with SAS.
    • SMART is unconditionally enabled on devices upon boot.  This solves problem where some newly installed devices may not have SMART enabled.
    • Unassigned devices will get spun-down according to 'Settings/Disk Settings/Default spin down delay'.

     

    Updated to 5.10 Linux kernel (5.10.1).

     

    Updated docker.

     

    Fixed bug joining AD domains.

     


     

    Version 6.9.0-rc2 2020-12-18 (vs -rc1)

    Base distro:

    • bind: verison 9.16.8
    • docker: version 19.03.14
    • krb5: version 1.18.2

    Linux kernel:

    • version 5.10.1

    Management:

    • emhttpd: fix external 'smartctl -n standby' causing device spinup
    • emhttpd: enable SMART on devices upon startup
    • emhttpd: unassigned devices spin-down according to global default
    • emhttpd: restore 'poll_attributes' event callout
    • smb: fixed AD join issue
    • webgui: do not try to display SMART info that causes spin-up for devices that are spun-down
    • webgui: avoid php syntax error if autov() source file does not exist

    Edited by limetech

    • Like 8
    • Thanks 4


    User Feedback

    Recommended Comments



    on only one of my 2 servers I am seeing kcompactd0 eat up 100% cpu approx every two days  it makes the webgui completely unresponsive and cannot get diagnostics at all (let it run 24 hours before i had to power cycle the server)

    kill command doesnt work and unable to do much else

    only started about a week ago and not sure what is the cause since i cant run diagnostics

    • Like 1
    Link to comment
    Share on other sites
    On 12/24/2020 at 3:19 PM, Draic said:

    I have increased the poll timer and will report back, but these settings weren't an issue on stable release

    Hi @Draic

     

    Do you have anything running Telegraf and if so did you see this.

     

     

    Link to comment
    Share on other sites

    Just wanted to note that I have upgraded to 6.9rc2 from 6.8.3 without issues. Server has been up for 5 days without problem. Thanks for the update.

    • Like 1
    Link to comment
    Share on other sites
    12 minutes ago, shaunmccloud said:

    Will a recording of my server's IPMI KVM console help figure out the cause of my RC2 kernel panics on boot?

    Yes but please post in a separate bug report.

    Link to comment
    Share on other sites

    I'm having lots of problems that haven't ever existed until RC2. I've been doing steady updates to RC builds since 2019. My file shares are slow now to browse, and docker containers cannot find updates and the only way to fix the slow SMB shares is to turn off all virtual machines. CPU usage on a 16 core 32 thread CPU is low, and nothing has changed except RC2. Something seems wrong with hypervisor, it's making the system unresponsive. 

    Link to comment
    Share on other sites

    With the RC2, my drives keep waking up, apparently because Unraid is pulling smart data:

     

    Dec 29 00:03:47 Tower emhttpd: spinning down /dev/sdd
    
    Dec 29 00:07:22 Tower emhttpd: read SMART /dev/sdd

     

    Is there any way to keep this from happening? I didn't have this problem with Beta 35.

     

    EDIT:

     

    Oh, and another thing: Twice now my Docker image seemed to be broken (got a weird error message that looked like something about the webgui was broken: "Docker service wont start"), but instead of having to rebuild the image, a restart fixed it. That didn't happen either with Beta 35.

     

    EDIT2:
     

    Just to make sure I disabled telegraf - my disks still wake up due to smart readings according to the log.

     

    Edited by Pillendreher
    Link to comment
    Share on other sites

    Updated yesterday. 

     

    Due to the hard lockups I've experienced before and because I needed to upgrade a disk, I updated everything, rebooted and then shutdown.

     

    Replaced the disk, which is currently rebuilding with no issues thus far.

    Link to comment
    Share on other sites
    22 hours ago, limetech said:

    Yes but please post in a separate bug report.

    Ok, will do.  Might not be until January 2nd due to having to move other plans up now :(

    Link to comment
    Share on other sites

    Upgraded my Unraid Server (which runs inside ESXi) to RC2 about a day ago.
    Everything is working nicely so far!
    Including spin down/up of disks. :)

    (note I do not use any dockers nor Vm's in UNRAID, it is a pretty simple setup with an LSI 2008 in IT mode, 5x 8TB HDD's Array, 1x 500GB cache SSD and 1x 6TB share unassigned devices)

    Link to comment
    Share on other sites

    I'm still seeing no logging whatsoever with 6.9.0-rc2 (started with 6.9.0-beta25 I believe).  The log button (upper-right console toolbar button) opens an empty window.  DMESG does have output, however.  The "/var/log/messages" file is empty, as is "/var/log/syslog".

    Edited by Holytoledo
    Link to comment
    Share on other sites
    17 minutes ago, Holytoledo said:

    I'm still seeing no logging whatsoever with 6.9.0-rc2 (started with 6.9.0-beta25 I believe).  The log button (upper-right console toolbar button) opens an empty window.  DMESG does have output, however.  The "/var/log/messages" file is empty, as is "/var/log/syslog".

    Post your diagnostics (even though the syslog will be empty)  Maybe some clue would be in there for why

    Link to comment
    Share on other sites

    Try for the heck of it deleting /config/rsyslog.cfg and /config/rsyslog.conf on the flash drive and then rebooting...

    Link to comment
    Share on other sites
    On 12/27/2020 at 11:35 PM, Can0n said:

    on only one of my 2 servers I am seeing kcompactd0 eat up 100% cpu approx every two days  it makes the webgui completely unresponsive and cannot get diagnostics at all (let it run 24 hours before i had to power cycle the server)

    kill command doesnt work and unable to do much else

    only started about a week ago and not sure what is the cause since i cant run diagnostics

     

    I'm seeing the same thing. I suspect this is what happens before my machine hangs ans I can't even ping it. I had to hard power boot the host as well.

    Link to comment
    Share on other sites

    There seems to be a problem with MacOS. I am on latest Catalina with all Updates.

    When I access my media share with around 3700 files I get a spinning wheel and my Mac finder can't list the files.

    While I can see folders - with some delay - listing files within a folder takes forever - even when there are only 10 files in the folder...

    This was good with RC1.

    Accessing Unraid from my windows machine works just fine.

     

    Edited by typewriter
    Link to comment
    Share on other sites
    On 12/28/2020 at 12:46 PM, Denisson said:

    I'm having lots of problems that haven't ever existed until RC2. I've been doing steady updates to RC builds since 2019. My file shares are slow now to browse, and docker containers cannot find updates and the only way to fix the slow SMB shares is to turn off all virtual machines. CPU usage on a 16 core 32 thread CPU is low, and nothing has changed except RC2. Something seems wrong with hypervisor, it's making the system unresponsive. 

    I had to revert back to RC1 because SMB was really unstable, and docker wouldn't check for updates. Now everything is back to normal. 

    Link to comment
    Share on other sites

    Just thought I would pop on here to say that I managed to update to 6.9rc2 from 6.8.3 without any apparent issues so far. My server has been offline due to house move. I had stumbled upon the nvidia unraid plugin issues and noticed it had become deprecated in the support thread. This led to me browsing the forums to see what happened and I read all about the fall out... :(

     

    So I decided to go straight to 6.9rc2. I don't normally deviate from stable releases but I went with this one to get the nvidia support back. Happy to report it all seems to work nicely and I've verified nvidia NVENC HW transcoding is back working again inside my plex docker for multiple streams being offloaded back to the GPU. 

    Link to comment
    Share on other sites

    not a bug but may a general question about the SMART actions lately

    i wonder a little why there are these smart actions without activity ... and how long it takes to spindown ....

     

    as sample

    ...

    Dec 30 05:54:24 AlsServer emhttpd: read SMART /dev/sdb

    Dec 30 05:54:42 AlsServer emhttpd: read SMART /dev/sdd

    Dec 30 05:54:54 AlsServer emhttpd: read SMART /dev/sdc

    Dec 30 08:23:59 AlsServer emhttpd: read SMART /dev/sdc

    Dec 30 23:00:49 AlsServer emhttpd: read SMART /dev/sdd <<- here i really had access to a file for 30 minutes

    --- spindown 7 hours later ... manually triggered by me today morning ....

    Dec 31 05:51:23 AlsServer emhttpd: spinning down /dev/sdd

    --- now again spinup and still running while there should be no activity ...

    Dec 31 07:37:20 AlsServer emhttpd: read SMART /dev/sdc

    Dec 31 07:37:35 AlsServer emhttpd: read SMART /dev/sdb

     

    when i spin them down its all good until the next SMART Trigger coming ... is this meanwhile by purpose ? i know we need access to the drive to get SMART values, but extra spinning up the disks only therefore ? cant be done while the disk is active anyway ?

     

    when the disk would be really active due activity, lets say plex is accessing the file due playback, then triggering the spindown wont help as its immediately up again as plex needs the access, thats why i wonder why a manual spindown is always fine when i see no activity and the auto spindown sometimes just doesnt come, even better would be to avoid these spinups with no activity.

     

    i triggered now the diags in case of interest, and this also spinups the discs also due SMART ;) but i see its by demand ...

    save system variables. + SMART reports

    alsserver-diagnostics-20201231-0807.zip

    Link to comment
    Share on other sites
    3 hours ago, alturismo said:

    not a bug but may a general question about the SMART actions lately

    i wonder a little why there are these smart actions without activity ... and how long it takes to spindown ....

     

    as sample

    ...

    Dec 30 05:54:24 AlsServer emhttpd: read SMART /dev/sdb

    Dec 30 05:54:42 AlsServer emhttpd: read SMART /dev/sdd

    Dec 30 05:54:54 AlsServer emhttpd: read SMART /dev/sdc

    Dec 30 08:23:59 AlsServer emhttpd: read SMART /dev/sdc

    Dec 30 23:00:49 AlsServer emhttpd: read SMART /dev/sdd <<- here i really had access to a file for 30 minutes

    --- spindown 7 hours later ... manually triggered by me today morning ....

    Dec 31 05:51:23 AlsServer emhttpd: spinning down /dev/sdd

    --- now again spinup and still running while there should be no activity ...

    Dec 31 07:37:20 AlsServer emhttpd: read SMART /dev/sdc

    Dec 31 07:37:35 AlsServer emhttpd: read SMART /dev/sdb

     

    when i spin them down its all good until the next SMART Trigger coming ... is this meanwhile by purpose ? i know we need access to the drive to get SMART values, but extra spinning up the disks only therefore ? cant be done while the disk is active anyway ?

     

    when the disk would be really active due activity, lets say plex is accessing the file due playback, then triggering the spindown wont help as its immediately up again as plex needs the access, thats why i wonder why a manual spindown is always fine when i see no activity and the auto spindown sometimes just doesnt come, even better would be to avoid these spinups with no activity.

     

    i triggered now the diags in case of interest, and this also spinups the discs also due SMART ;) but i see its by demand ...

    save system variables. + SMART reports

    alsserver-diagnostics-20201231-0807.zip 134.84 kB · 0 downloads

    Same here. I reckon something went wrong during a modification of how smart information is gathered (If I remember correctly I read something regarding SMART in the changelog)

    Link to comment
    Share on other sites

    My logs are also being spammed with this:

     

    Dec 31 17:29:53 Fileserver emhttpd: read SMART /dev/sda

     

    The funny part is /dev/sda is an external USB3 enclosure mounted via Unassigned Devices.  SMART data will never be available for that device.  

     

    image.png.633f18b7f69e860e8cf7ec64a80c3503.png

    Edited by Holytoledo
    Link to comment
    Share on other sites

    any chance this was resolved in rc2 @limetech?

     

    Here are diags from beta 30:
    https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/2/?tab=comments#comment-10968

     

    And here are the results of `hexdump -C -n 512 /dev/sdh`

    https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/3/?tab=comments#comment-10972

     

    limetech said: Thanks, yes that explains it.  Probably, with -beta25 and even earlier releases, if you click on the device from Main and then look at 'Partition format' it will say 'GPT: 4KiB-aligned (factory erased)' - that (factory erased) shouldn't be there.  Will fix for next release.

    Link to comment
    Share on other sites

    hp ml350p kernel panic after boot. booting into safe mode with no plugins allows boot. Not sure which was causing the issue as I manually nuked them all and only reinstalled a few that I know I use regularly. I know this isn't that helpful, but reporting nonetheless.

    Link to comment
    Share on other sites

    I have been experiencing network issues while on 6.9rc2.  My dockers will stop being able to be reached by any GUI, my transfers speeds slow down to a crawl and i lose access to the console GUI.  It eventually comes back on by itself.  This occurs multiple times in a day.  I have an Intel SFP+ card using the ixgbe drivers.  I have checked the logs when it comes back up and nothing stands out.  I have since reverted back to 6.9rc1 and it does not seem to be an issue there.

    Link to comment
    Share on other sites



    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.