• Unraid OS version 6.12.0-rc2 available


    limetech

    Please refer to the 6.12.0-rc1 topic for a general overview.

     


    Version 6.12.0-rc2 2023-03-18

    Bug fixes

    • networking: fix nginx recognizing IP address from slow dhcp servers
    • VM Manager: let page load even when PCI devices appear missing or are misassigned
    • webgui: Dashboard fixes:
      • lock the Dashboard completely: Editing/moving only becomes possible when unlocking the page
      • An empty column is refilled when the respective tiles are made visible again, no need to reset everything
      • added a visual "move indicator" on the Docker and VM page, to make clearer that rows can be moved now.
      • change cursor shape when moving is enabled
      • use tile title as index
    • webgui: fix issue displaying Attributes when temperature display set to Fahrenheit
    • zfs: fixed issue importing ZFS pools with additional top-level sections besides the root section

    ZFS Pools

    • Add scheduled trimming of ZFS pools.
    • Replace Scrub button with Clear button when pool is in error state.

    Base Distro

    • php: version 8.2.4

    Linux kernel

    • version 6.1.20
    • CONFIG_X86_AMD_PSTATE: AMD Processor P-State driver

    Misc

    • save current PCI bus/device information in file '/boot/previous/hardware' upon Unraid OS upgrade.
    • Like 12
    • Thanks 3



    User Feedback

    Recommended Comments



    • Featured Comment

    NOTE

     

    Any plugin which has been hacking its way into the dashboard has now been marked as being incompatible.

     

    These plugins:  GPU Stats, Corsair Power Supply, Disk Location and Plex Streams now actually crash the dashboard and it is highly recommended to uninstall them.  They will not be available again via Apps until such time as the respective authors update their plugins to be compatible and notify me of this.

     

    Also ensure that all other plugins are up to date.  Notably, NUT and IPMI (versions from dmacias) will also crash the dashboard, but replacements for these are available within CA (from SimonF)

    • Like 9
    • Thanks 1
    Link to comment

    Hmm... is this a bug? (using RC2)

    Mar 19 02:02:11 Tower kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P28191 } 4018399 jiffies s: 69 root: 0x0/T
    Mar 19 02:02:11 Tower kernel: rcu: blocking rcu_node structures (internal RCU debug):
    Mar 19 02:02:58 Tower kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
    Mar 19 02:02:58 Tower kernel: rcu:      Tasks blocked on level-0 rcu_node (CPUs 0-7): P28191/1:b..l
    Mar 19 02:02:58 Tower kernel:   (detected by 7, t=9421862 jiffies, g=2189581, q=119216478 ncpus=8)
    Mar 19 02:02:58 Tower kernel: task:rsync           state:D stack:0     pid:28191 ppid:28164  flags:0x00004002
    Mar 19 02:02:58 Tower kernel: Call Trace:
    Mar 19 02:02:58 Tower kernel: <TASK>
    Mar 19 02:02:58 Tower kernel: __schedule+0x5a0/0x600
    Mar 19 02:02:58 Tower kernel: schedule+0x8e/0xcc
    Mar 19 02:02:58 Tower kernel: __down_write_common+0x453/0x4e2
    Mar 19 02:02:58 Tower kernel: ? writeback_single_inode+0x134/0x142
    Mar 19 02:02:58 Tower kernel: fuse_flush+0xa6/0x199
    Mar 19 02:02:58 Tower kernel: filp_close+0x2c/0x74
    Mar 19 02:02:58 Tower kernel: put_files_struct+0x63/0xa4
    Mar 19 02:02:58 Tower kernel: do_exit+0x390/0x923
    Mar 19 02:02:58 Tower kernel: ? ksys_write+0x76/0xc2
    Mar 19 02:02:58 Tower kernel: make_task_dead+0x11c/0x11c
    Mar 19 02:02:58 Tower kernel: rewind_stack_and_make_dead+0x17/0x17
    Mar 19 02:02:58 Tower kernel: RIP: 0033:0x14a10aca2ba0
    Mar 19 02:02:58 Tower kernel: RSP: 002b:00007ffd2d99b6a8 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
    Mar 19 02:02:58 Tower kernel: RAX: ffffffffffffffda RBX: 00000000005659c0 RCX: 000014a10aca2ba0
    Mar 19 02:02:58 Tower kernel: RDX: 0000000000040000 RSI: 00000000005659c0 RDI: 0000000000000001
    Mar 19 02:02:58 Tower kernel: RBP: 0000000000000001 R08: 000000000059d9c0 R09: 0000000000000010
    Mar 19 02:02:58 Tower kernel: R10: 000000000000000f R11: 0000000000000202 R12: 0000000000040000
    Mar 19 02:02:58 Tower kernel: R13: 0000000000000000 R14: 0000000000008000 R15: 0000000000d10990
    Mar 19 02:02:58 Tower kernel: </TASK>
    Mar 19 02:03:17 Tower kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P28191 } 4083935 jiffies s: 69 root: 0x0/T
    Mar 19 02:03:17 Tower kernel: rcu: blocking rcu_node structures (internal RCU debug):
    Mar 19 02:04:22 Tower kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P28191 } 4149471 jiffies s: 69 root: 0x0/T
    Mar 19 02:04:22 Tower kernel: rcu: blocking rcu_node structures (internal RCU debug):
    Mar 19 02:05:28 Tower kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P28191 } 4215007 jiffies s: 69 root: 0x0/T
    Mar 19 02:05:28 Tower kernel: rcu: blocking rcu_node structures (internal RCU debug):
    Mar 19 02:05:58 Tower kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
    Mar 19 02:05:58 Tower kernel: rcu:      Tasks blocked on level-0 rcu_node (CPUs 0-7): P28191/1:b..l
    Mar 19 02:05:58 Tower kernel:   (detected by 4, t=9601928 jiffies, g=2189581, q=125084304 ncpus=8)
    Mar 19 02:05:58 Tower kernel: task:rsync           state:D stack:0     pid:28191 ppid:28164  flags:0x00004002
    Mar 19 02:05:58 Tower kernel: Call Trace:
    Mar 19 02:05:58 Tower kernel: <TASK>
    Mar 19 02:05:58 Tower kernel: __schedule+0x5a0/0x600
    Mar 19 02:05:58 Tower kernel: schedule+0x8e/0xcc
    Mar 19 02:05:58 Tower kernel: __down_write_common+0x453/0x4e2
    Mar 19 02:05:58 Tower kernel: ? writeback_single_inode+0x134/0x142
    Mar 19 02:05:58 Tower kernel: fuse_flush+0xa6/0x199
    Mar 19 02:05:58 Tower kernel: filp_close+0x2c/0x74
    Mar 19 02:05:58 Tower kernel: put_files_struct+0x63/0xa4
    Mar 19 02:05:58 Tower kernel: do_exit+0x390/0x923
    Mar 19 02:05:58 Tower kernel: ? ksys_write+0x76/0xc2
    Mar 19 02:05:58 Tower kernel: make_task_dead+0x11c/0x11c
    Mar 19 02:05:58 Tower kernel: rewind_stack_and_make_dead+0x17/0x17
    Mar 19 02:05:58 Tower kernel: RIP: 0033:0x14a10aca2ba0
    Mar 19 02:05:58 Tower kernel: RSP: 002b:00007ffd2d99b6a8 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
    Mar 19 02:05:58 Tower kernel: RAX: ffffffffffffffda RBX: 00000000005659c0 RCX: 000014a10aca2ba0
    Mar 19 02:05:58 Tower kernel: RDX: 0000000000040000 RSI: 00000000005659c0 RDI: 0000000000000001
    Mar 19 02:05:58 Tower kernel: RBP: 0000000000000001 R08: 000000000059d9c0 R09: 0000000000000010
    Mar 19 02:05:58 Tower kernel: R10: 000000000000000f R11: 0000000000000202 R12: 0000000000040000
    Mar 19 02:05:58 Tower kernel: R13: 0000000000000000 R14: 0000000000008000 R15: 0000000000d10990
    Mar 19 02:05:58 Tower kernel: </TASK>

     

    • Like 1
    Link to comment
    1 minute ago, idmanager said:

    Just updated and got a blank dashboard the header at the top and buttons are there but nothing else ? 

    Did you read the first post?

    Link to comment
    2 minutes ago, idmanager said:

    Just updated and got a blank dashboard the header at the top and buttons are there but nothing else ? 

    Nop... that's an issue. I'm getting some panels.

    Link to comment
    2 minutes ago, Jazer said:

    Nop... that's an issue. I'm getting some panels.

    this is the first post

     

    Any plugin which has been hacking its way into the dashboard has now been marked as being incompatible.

     

    These plugins:  GPU Stats, Corsair Power Supply, Disk Location and Plex Streams now actually crash the dashboard and it is highly recommended to uninstall them.  They will not be available again via Apps until such time as the respective authors update their plugins to be compatible and notify me of this

    Edited by SimonF
    Link to comment

    After starting unRAID, I can connect using ssh for a while. After some hours/events, I can't establish new ssh connections anymore. The logs are fine (as I can guess). Old ssh connections are not disconnect and are working properly, but new ones are timed out. I'm not sure if this is 6.12 related - I'm testing on a brand new system.

     

    Mar 19 02:18:28 Tower sshd[8630]: Connection from 192.168.188.106 port 61207 on 192.168.188.111 port 22 rdomain ""
    Mar 19 02:18:28 Tower sshd[8630]: Accepted key RSA SHA256:xxx found at /root/.ssh/authorized_keys:2
    Mar 19 02:18:28 Tower sshd[8630]: Postponed publickey for root from 192.168.188.106 port 61207 ssh2 [preauth]
    Mar 19 02:18:28 Tower sshd[8630]: Accepted key RSA SHA256:xxx found at /root/.ssh/authorized_keys:2
    Mar 19 02:18:28 Tower sshd[8630]: Accepted publickey for root from 192.168.188.106 port 61207 ssh2: RSA SHA256:xxx
    Mar 19 02:18:28 Tower sshd[8630]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
    Mar 19 02:18:34 Tower kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P28191 } 5001439 jiffies s: 69 root: 0x0/T
    Mar 19 02:18:34 Tower kernel: rcu: blocking rcu_node structures (internal RCU debug):
    Mar 19 02:19:40 Tower kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P28191 } 5066975 jiffies s: 69 root: 0x0/T
    Mar 19 02:19:40 Tower kernel: rcu: blocking rcu_node structures (internal RCU debug):
    Mar 19 02:20:28 Tower sshd[8630]: pam_elogind(sshd:session): Failed to create session: Connection timed out
    Mar 19 02:20:28 Tower sshd[8630]: Connection closed by 192.168.188.106 port 61207
    Mar 19 02:20:28 Tower sshd[8630]: Close session: user root from 192.168.188.106 port 61207 id 0
    Mar 19 02:20:28 Tower sshd[8630]: pam_unix(sshd:session): session closed for user root
    Mar 19 02:20:28 Tower sshd[8630]: Transferred: sent 3848, received 3884 bytes
    Mar 19 02:20:28 Tower sshd[8630]: Closing connection to 192.168.188.106 port 61207

     

    Link to comment
    1 hour ago, idmanager said:

    Added dia files but still blank dash and I am not using any of the plugins 

    tower-diagnostics-20230319-1021.zip

     

    These are the plugins you are using, please uninstall any incompatible ones

    ca.backup2.plg - 2023.01.28  (Up to date)  (Incompatible)
    ca.cleanup.appdata.plg - 2022.10.21  (Up to date)
    ca.mover.tuning.plg - 2022.04.13  (Up to date)
    ca.turbo.plg - 2023.03.02  (Up to date)
    ca.update.applications.plg - 2023.02.20  (Up to date)
    community.applications.plg - 2023.03.11  (Up to date)
    controlr.plg - v2022.12.30  (Up to date)
    docker.categorize.plg - 2022.03.10  (Up to date)
    dynamix.cache.dirs.plg - 2023.02.19  (Up to date)
    dynamix.file.manager.plg - 2023.03.17  (Up to date)
    dynamix.local.master.plg - 2023.02.20  (Up to date)
    dynamix.system.info.plg - 2023.02.05  (Up to date)
    dynamix.system.stats.plg - 2023.02.14  (Up to date)
    dynamix.system.temp.plg - 2023.02.04b  (Up to date)
    dynamix.unraid.net.plg - 2023.03.09.1140  (Up to date)
    enhanced.log.plg - 2023.02.01  (Up to date)
    fix.common.problems.plg - 2023.03.04  (Up to date)
    gpustat.plg - 2022.11.30a  (Up to date)  (Incompatible)
    gui-links.plg - 2022.05.29  (Up to date)
    intel-gpu-top.plg - 2023.02.15  (Up to date)
    intel-gvt-g.plg - 2022.05.02  (Up to date)
    NerdTools.plg - 2023.03.11  (Up to date)
    Python3.plg - 2022.08.24  (Up to date)
    theme.engine.plg - 2023.01.17  (Up to date)
    tips.and.tweaks.plg - 2023.02.01  (Up to date)
    unassigned.devices.plg - 2023.03.03  (Up to date)
    unassigned.devices-plus.plg - 2022.11.06  (Up to date)
    unassigned.devices.preclear.plg - 2023.02.26  (Up to date)
    unbalance.plg - v2021.04.21  (Up to date)
    unRAIDServer.plg - 6.12.0-rc2
    upnp-monitor.plg - 2020.01.04c  (Up to date)
    user.scripts.plg - 2023.03.04  (Up to date)

     

    Link to comment

    First time trying to report a bug so here it goes:

    Upgraded to 6.12.0 rc2 after removing all incompatible plugins (in my case GPU Statistics).

    The only thing that doesn't work properly is my Windows 10 VM i440-fx-7.1 which:

    -if it use CPU Passthrough, is very sluggish, it boots in 10 minutes, etc.

    -if I enable CPU Mode Emulated  (QEMU64), it works in an acceptable manner.

     

    Ubuntu and Windows 7 machines work as expected.

     

    Nothing else to report for now.

    Edited by Mihai Olimpiu
    Link to comment

    Just reassigned a miditower for experimental work, and found out that 6.12 has now zfs built-in. Yay! Now, if we can also get MGLRU (cat /sys/kernel/mm/lru_gen/enabled), that would be GREAT! Looking forward to test this out. Great job, keep up the good work.

    Link to comment
    12 minutes ago, isvein said:

    Just me, or does Docker uses forever to check for updates?

    Seems fine to me

    Link to comment
    10 minutes ago, isvein said:

    Here it the "update" just spins for forever sometimes :/

     

    I have never seen this issue, all works fine for me.

    Perhaps there is some corruption in your docker image.

    Have you ever tried to delete the docker image and re-install your containers?

    You can use the restore function of CA to get everything back and start fresh.

     

    Link to comment
    1 hour ago, isvein said:

    Just me, or does Docker uses forever to check for updates?

    I thought the same but then looking at the logs realised that after loading RC2 rendered my docker.img as a read only volume.  btrfs complained of corrupt super block.  Not sure if RC2 related or a coincidence.

     

    Now in the process of rebuilding my docker image.

     

    Edit:  Looks like my entire cache pool/drive is read only and also getting read errors.  Was working before.  Reboot hasn't helped.   Need to dig in and see what's happening.

     

    Diags attached if anyone wants to dig in deeper.

    tdm-diagnostics-20230320-0601.zip

    Link to comment

    Searched through all the comments and couldn't find an answer - also I apologize if this is a dumb question. What does the autotrim feature do? How is it different from scheduling trim?

    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.