• 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



    7 minutes ago, hydkrash said:

    All my shares reside on my ZFS pool.

    Set all those shares to cache=only and select the correct pool, like mentioned they are set to cache=no, meaning only the array device would be used.

    • Like 1
    Link to comment
    2 minutes ago, JorgeB said:

    Set all those shares to cache=only and select the correct pool, like mentioned they are set to cache=no, meaning only the array device would be used.

    OMG that worked! Thank You so much!

    I have to say, that is a really misleading setting.

    Clicking on the share, you can see the files and folders in it.

    But I didn't dawn on me that the ZFS folder would be deemed as the cache pool.

    Link to comment
    9 minutes ago, hydkrash said:

    Clicking on the share, you can see the files and folders in it.

    Read always takes from all sources, but writes go through the filters and settings.

     

    Link to comment
    18 minutes ago, hydkrash said:

    But I didn't dawn on me that the ZFS folder would be deemed as the cache pool.

    When you use the Use Cache setting = Only then you are not really using it as a cache.

     

    Perhaps it would be clearer if the text was redone to be something like "Use Cache/Pool" to make it clearer or maybe simply "Use Pool"?   The current text dates from the days when only a single pool was possible and the option was to use it as a cache or not.

    Link to comment
    1 hour ago, itimpi said:

    Perhaps it would be clearer if the text was redone to be something like "Use Cache/Pool" to make it clearer or maybe simply "Use Pool"?

     

    This ^^ is very important.

     

    "Set all those (ZFS) shares to cache=only" is very confusing.

     

    Link to comment
    On 3/24/2023 at 3:22 PM, infidel said:

    I would do, but Unraid is imploding. I made a couple of videos to demonstrate what I'm having to deal with here:

     

    I've come back to this problem after the weekend and it seems to come down to this:

    According to all the advice I can find (remember, I'm new to Unraid), I've been trying to copy files to /mnt/user/[sharename]

    For some reason, these map to /mnt/disk1/[sharename], disk1 being the 32Gb USB stick I'm using for a data drive.

    If you map a network drive to \\unraidserver\sharename\ it maps to /mnt/user/[sharename], so any files you copy fill up the USB drive rather being copied to the pool.

    When the USB drive is full, all hell breaks loose (see above)

    I don't know how to change this, if it's something I've done, or a bug that needs reporting.

     

    EDIT: Just say the message about setting all shares to cache=only. I don't understand how that would work when I don't have a cache pool at the moment (SSD is in the post).

    Add it to the pile of things I'm still figuring out in RC2, such as if I have a ZFS pool with (presumably) parity striped across all drives in the pool, does changing the Allocation method do anything anymore?

    Edited by infidel
    Link to comment
    7 hours ago, decibelio99 said:

    I have installed your plugin but it doesn't save the data

    Do you have a multi language loaded? Saw a report yesterday setting to english allowed it to work.

    • Haha 1
    Link to comment
    10 minutes ago, infidel said:

    I've come back to this problem after the weekend and it seems to come down to this:

    According to all the advice I can find (remember, I'm new to Unraid), I've been trying to copy files to /mnt/user/[sharename]

    For some reason, these map to /mnt/disk1/[sharename], disk1 being the 32Gb USB stick I'm using for a data drive.

    If you map a network drive to \\unraidserver\sharename\ it maps to /mnt/user/[sharename], so any files you copy fill up the USB drive rather being copied to the pool.

    When the USB drive is full, all hell breaks loose (see above)

    I don't know how to change this, if it's something I've done, or a bug that needs reporting.

    Please post up your diagnostics file.   It will help the Gurus to see what is going on.

     

    EDIT:  Tell us the name of the share involved.

    Edited by Frank1940
    • Like 1
    Link to comment
    4 minutes ago, ChatNoir said:

    One thing you want to do if you're upgrading on a running machine via the manual method is move all of the bz* files from the root of the flash to the previous folder and then extract the zip contents onto the root of the flash.

     

    Simply overwriting (which has been the suggestion in the forums for years) existing bz* files may cause issues / boot failures under certain circumstances

    Link to comment
    28 minutes ago, SimonF said:

    Do you have a multi language loaded? Saw a report yesterday setting to english allowed it to work.

    Yes it worked. Thank you

    • Like 1
    Link to comment
    41 minutes ago, infidel said:

    EDIT: Just say the message about setting all shares to cache=only. I don't understand how that would work when I don't have a cache pool at the moment (SSD is in the post).

    Add it to the pile of things I'm still figuring out in RC2, such as if I have a ZFS pool with (presumably) parity striped across all drives in the pool, does changing the Allocation method do anything anymore?

    If you have a zfs pool that's considered a cache pool, legacy Unraid name.

    Link to comment
    13 minutes ago, decibelio99 said:

    Yes it worked. Thank you

    That should be fixed on 2023.03.27 could you test?

    Link to comment
    18 hours ago, SimonF said:

    That should be fixed on 2023.03.27 could you test?

    Yes, I updated it and now the incompatibility ticket has disappeared 😀

    Link to comment

    Apologies if this is not the right place to ask...but is there an expected time frame when zfs pools can be imported and automatically mounted that were created by Truenas Scale? Or is there an easy way that I can get my pool working with unraid? It's a 2x4 RaidZ1, with Metadata and ZIL vdevs if this matters. I have a lot of data on there so I would prefer not transfer it off the drives if at all possible.

    On the release notes it says that ZFS features/compatibility will be added over 2 releases - I take it that means 6.12 + 6.13? Or do you mean release candidates or minor versions? Sorry if this is a dumb question🙂

    Link to comment

    "cache" in this sense only means "which drives the writing occurs on first" so for ZFS you would select pools as "Cache Only", I have 2 pools, a ssd pool and a platter disk pool, I select each dataset (or share) and mark each as <Pool> Only in cache settings, so each dataset is tied to the pool its on, you should create a pool, create datasets, then mark those datasets as only writing to THAT pool (called cache for the time being)

     

    An unrelated question, would it be possible to get CORS settings in the UI? I know reverse proxies are not supported but we all use them and it would be nice to add the reverse proxy as an allowed origin.

    Link to comment

    there is a minor problem of re-naming a VM. re-naming a vm will change the vDisk Location folder name & Primary vDisk Location path; 6.11.5 doesn't do that as i recall. my current solve is manually change the name of Location folder back to what it was, and then, make sure the Primary vDisk Location point to the right folder.

    Edited by winglam
    Link to comment

    Anyone else having issues with AMD pstates after this update? I get system lockups while the server is not doing anything like I used to when Ryzen systems first came out. They had gone away and have now come back with this build.

    Link to comment
    3 hours ago, mpa4712 said:

    Anyone else having issues with AMD pstates after this update? I get system lockups while the server is not doing anything like I used to when Ryzen systems first came out. They had gone away and have now come back with this build.

    i am fine. running 5950x. i have c state disable and also set "Power Supply Idle Control" to "typical current idle".

    Link to comment
    19 hours ago, mpa4712 said:

    Anyone else having issues with AMD pstates after this update? I get system lockups while the server is not doing anything like I used to when Ryzen systems first came out. They had gone away and have now come back with this build.

     

    I'm waiting for the final release to upgrade.

    What cpufreq-info tells you ? is the driver amd-pstate used ?

    Link to comment
    Mar 29 15:53:02 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 29 15:54:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 29 16:54:03 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 29 16:55:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 29 17:55:03 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 29 17:56:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 29 18:56:03 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 29 18:57:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 29 19:57:03 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 29 19:58:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 29 20:58:03 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 29 20:59:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 29 22:52:03 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 29 22:53:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 29 23:53:02 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 29 23:54:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 30 00:54:02 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 30 00:55:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 30 01:55:02 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 30 01:56:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 30 02:56:03 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 30 02:57:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 30 04:40:39 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 30 04:41:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 30 05:41:02 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 30 05:42:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 30 06:42:02 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 30 06:43:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 30 07:43:02 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 30 07:44:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 30 08:44:02 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 30 09:45:02 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 30 09:46:08 HOME-unRAID emhttpd: read SMART /dev/sde
    Mar 30 10:46:03 HOME-unRAID emhttpd: spinning down /dev/sde
    Mar 30 10:47:08 HOME-unRAID emhttpd: read SMART /dev/sde

    After updating my unraid system to 6.12.0-rc2, the hard drive cannot sleep. I have set the system to automatically sleep after one hour of no read/write activity. However, upon checking the hard drive logs, I discovered that the system automatically wakes it up after it sleeps. What could be causing this?

    Link to comment
    40 minutes ago, BOGu said:

    After updating my unraid system to 6.12.0-rc2, the hard drive cannot sleep.

    Did you do a new config after updating to rc2? There's currently a known issue affecting spin down after doing that.

    Link to comment
    On 3/28/2023 at 8:18 PM, mpa4712 said:

    Anyone else having issues with AMD pstates after this update? I get system lockups while the server is not doing anything like I used to when Ryzen systems first came out. They had gone away and have now come back with this build.

     

    You have to pass amd_pstate=passive at boot to enable it. Just tested it myself.

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