• Unraid OS version 6.10.0-rc2 available


    limetech

    6.10.0 Summary of Changes and New Features

     

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

     

    Note: In order to permit ongoing development, some changes/features are marked experimental.  This means underlying support is included in the release, but high level functionality or UI has not been included yet.

     

    UPC and My Servers Plugin - [rc2] reworded

    The most visible new feature is located in the upper right of the webGUI header.  We call this the User Profile Component, or UPC.  The UPC allows a user to associate their server(s) and license key(s) with their Unraid Community forum account, also known as an Unraid.net account.

     

    Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key.  All key purchases and upgrades are also handled exclusively via the UPC.

     

    Signing-in provides these benefits:

    1. My Servers Dashboard - when logged into the forum a new My Servers menu item appears. Clicking this brings up a Dashboard which displays a set of tiles representing servers associated with this account.  Each tile includes a link to bring up the servers webGUI on your LAN.  Install the My Servers plugin to provide real-time status and other advanced features (see below).
    2. Notification of critical security-related updates.  In the event a serious security vulnerability has been discovered and patched, we will send out a notification to all email addresses associated with registered servers.
    3. Posting privilege in a new set of My Servers forum boards.
    4. No more reliance on email and having to copy/paste key file URLs in order to install a license key - keys are delivered and installed automatically to your server.

     

    Once a license key has been provisioned, it is not necessary to remain signed-in, though there is no particular reason to sign-out.

    [rc2]  Exception:  A server must be signed-in to Provision and Renew a Let's Encrypt SSL certificate.

     

    My Servers Plugin

    My Servers is what we call our set of cloud-based or cloud-enabled services and features that integrate with your Unraid server(s).  Once installed here are some of the features of My Servers:

    • Real-time Status - with the plugin installed each server tile on the My Servers Dashboard will display real-time status such as whether the server is online or offline, storage utilization and other information. 
    • Remote Access link - if enabled, a link is displayed on the My Servers Dashboard to bring up a server webGUI remotely over the Internet.
    • Automatic Flash Backup - every registered server is provided with a private git repo initially populated with the contents of your USB flash boot device (except for certain files which contain private information such as passwords).  Thereafter, configuration changes are automatically committed.  A link is provided to download a custom zip file that can be fed as input to the USB Flash Creator tool to move your configuration to a new USB flash device.

     

    My Servers is an optional add-on, installed through Community Apps or via direct plugin URL.  Detailed instructions can be found here.

     

    If you have installed the My Servers plugin, signed-in servers will maintain a websocket connection to a cloud-based Lime Technology proxy server for the purpose of relaying real-time status.

     

    Security Changes

    • It is now mandatory to define a root password.  We also created a division in the Users page to distinguish root from other user names.  The root UserEdit page includes a text box for pasting SSH authorized keys.
    • For new configurations, the flash share default export setting is No.
    • For all new user shares, the default export setting is No.
    • For new configurations, SMBv1 is disabled by default.
    • For new configurations, telnet, ssh, and ftp are disabled by default.
    • We removed certain strings from Diagnostics such as passwords found in the 'go' file.

     

    Virtualization

    Both libvirt and qemu have been updated.  In addition qemu has been compiled with OpenGL support, and [rc2] ARM emulation (experimental).

     

    [rc2] To support Windows 11 which requires TPM and Secure boot, we have added TPM emulation; and, added a "Windows 11" VM template which automatically selects TPM-aware OVMF bios.  Also, here are instructions for upgrading a Windows 10 VM to Windows 11.  Special thanks to @ich777 who researched and determined what changes and components were necessary to provide this functionality.

     

    The built-in FireFox browser available in GUI-mode boot is built as an AppImage and located in the bzfirmware compressed file system image.  This saves approximately 60MB of RAM.

     

    The Wireguard plugin has been integrated into webGUI, that is, no need for the plugin.  If you had the plugin installed previously, it will be uninstalled and moved to the "Plugins/Plugin File Install Errors" page. No action is needed unless you want to press the Delete button to remove it from that page. Your WireGuard tunnels and settings will be preserved.

     

    Simplified installation of the Community Apps plugin.  The webGUI automatically includes the Apps menu item, and if CA is not already installed, the page offers an Install button.  No need to hunt for the plugin link.

     

    Let's Encrypt SSL provisioning change.  In previous releases code that provisions (allocates and downloads) a LE SSL certificate would first test if DNS Rebinding Protection was enforced on the user's LAN; and, if so, would not provision the certificate.  Since there are other uses for a LE certificate we changed the code so that provision would always proceed.  Next, we changed the logic behind the Auto selection of "Use SSL/TLS" setting on the Management Access page.  Now it is only possible to select Auto if both a LE certificate has been provisioned and DNS Rebinding Protection is not enforced.  This is a subtle change but permits certain My Servers features such as Remote Access.

     

    Linux Kernel

    Upgrade to [rc2] Linux 5.14.15 kernel which includes so-called Sequoia vulnerability mitigation.

     

    In-tree GPU drivers are now loaded by default if corresponding hardware is detected:

    • amdgpu
    • ast
    • i915
    • radeon

     

    These drivers are required mostly for motherboard on-board graphics used in GUI boot mode.  Loading of a driver can be prohibited by creating the appropriate file named after the driver:

    echo "blacklist i915" > /boot/config/modprobe.d/i915.conf

    Alternately, the device can be isolated from Linux entirely via the System Devices page.  Note that in Unraid OS 6.9 releases the in-tree GPU drivers are blacklisted by default and to enabling loading a driver you need to create an empty "conf" file.  After upgrading to Unraid OS 6.10 you may delete those files, or leave them as-is.  This change was made to greatly improve the Desktop GUI experience for new users.

     

    Added support for Intel GVT-g, which lets you split your Intel i915 iGPU into multiple virtual GPUs and pass them through to multiple VMs, using @ich777's Intel-GVT-g plugin.

     

    Added support for gnif/vendor-reset.  This simplifies @ich777's AMD Vendor Reset plugin which permits users to get their AMD video cards to reset properly.

     

    [rc2] Added so-called "add-relaxable-rmrr-5_8_and_up.patch" modified for our kernel
      https://github.com/kiler129/relax-intel-rmrr/blob/master/patches/add-relaxable-rmrr-5_8_and_up.patch

    Thanks to @ich777 for pointing this out,

     

    [rc2] Enabled additional ACPI kernel options
    [rc2] Updated out-of-tree drivers

    [rc2] Enabled TPM kernel modules (not utilized yet) - note this is for Unraid host utilizing physical TPM, not emulated TPM support for virtual machnes.

     

    Base Packages

    Virtually the entire base package set has been updated.

     

    [rc2] For SMB: Samba version 4.15 SMB3 multi-channel is no longer marked "experimental" and is enabled by default.

     

    [rc2] Per request we added the mcelog package.  With inclusion of this package, if you have an AMD processor you may see this error message in the system log:

    mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead.

    We're not sure what to make of this.  It appears mcelog is begin deprecated in favor of rasdaemon.  This is something we need to research further.

     

    Other improvements available in 6.10, which are maybe not so obvious to spot from the release notes and some of these improvements are internal and not really visible:

     

    Event driven model to obtain server information and update the webGUI in real-time

    • The advantage of this model is its scalability. Multiple browsers can be opened simultaneously to the webGUI without much impact
    • In addition stale browser sessions won't create any CSRF errors anymore
    • People who keep their browser open 24/7 will find the webGUI stays responsive at all times

     

    Docker labels

    • Docker labels are added to allow people using Docker compose to make use of icons and GUI access
    • Look at a Docker 'run' command output to see exactly what labels are used

     

    Docker custom networks

    • A new setting for custom networks is available. Originally custom networks are created using the macvlan mode, and this mode is kept when upgrading to version 6.10
    • The new ipvlan mode is introduced to battle the crashes some people experience when using macvlan mode. If that is your case, change to ipvlan mode and test. Changing of mode does not require to reconfigure anything on Docker level, internally everything is being taken care off.

     

    Docker bridge network (docker0)

    • docker0 now supports IPv6. This is implemented by assigning docker0 a private IPv6 subnet (fd17::/64), similar to what is done for IPv4 and use network translation to communicate with the outside world
    • Containers connected to the bridge network now have both IPv4 and IPv6 connectivity (of course the system must have IPv6 configured in the network configuration)
    • In addition several enhancements are made in the IPv6 implementation to better deal with the use (or no-use) of IPv6

     

    Plugins page

    • The plugins page now loads information in two steps. First the list of plugins is created and next the more time consuming plugin status field is retrieved in the background. The result is a faster loading plugins page, especially when you have a lot of plugins installed

     

    Dashboard graphs

    • The dashboard has now two graphs available. The CPU graph is displayed by default, while the NETWORK graph is a new option under Interface (see the 'General Info' selection)
    • The CPU graph may be hidden as well in case it is not desired
    • Both graphs have a configurable time-line, which is by default 30 seconds and can be changed independently for each graph to see a longer or shorter history.
    • Graphs are updated in real-time and are useful to observe the behavior of the server under different circumstances

     

    Other Changes

    • We switched to a better-maintained version of the WSD server component called wsdd2 in an effort to eliminate instances where the wsd daemon would start consuming 100% of a CPU core.  [rc2] Automatically restrict wsdd to listen only at the primary network interface (br0, bond0, or eth0, depending on config).
    • Fixed issue where you couldn't create a docker image on a share name that contains a space.
    • Fixed issue where 'mover' would not move to a pool name that contains a space.
    • Fixed issue in User Share file system where permissions were not being honored.
    • We increased the font size in Terminal and [rc2] fixed issue with macOS Monterey.
    • [rc2] Fixed jumbo frames not working.
    • [rc2] sysctl: handle net.netfilter.nf_conntrack_count max exceeded (increase setting to 131072) - hattip to Community Member @DieFalse

    • [rc2] Mover will create '.partial' file and then rename upon completion.

    • [rc2] Check bz file sha256sums at boot time.

     

    Credits

    Special thanks to all our beta testers and especially:

    @bonienl for his continued refinement and updating of the Dynamix webGUI.

    @Squid for continued refinement of Community Apps and associated feed.

    @dlandon for continued refinement of Unassigned Devices plugin and patience as we change things under the hood.

    @ich777 for assistance and passing on knowledge of Linux kernel config changes to support third party drivers and other kernel-related functionality via plugins.

    @SimonF for refinements to System Devices page and other webGUI improvements.  We intend to merge your mover progress changes during this RC series.

     


     

    Version 6.10.0-rc2 2021-11-01 (vs. 6.10.0-rc1)

     

    Base distro:

    • acpid: version 2.0.33
    • at-spi2-core: version 2.42.0
    • bind: version 9.16.22
    • btrfs-progs: version 5.14.2
    • ca-certificates: version 20211005
    • cifs-utils: version 6.14
    • coreutils: version 9.0
    • cryptsetup: version 2.4.1
    • curl: version 7.79.1
    • dhcpcd: version 9.4.1
    • dnsmasq: version 2.86
    • docker: version 20.10.9
    • e2fsprogs: version 1.46.4
    • ethtool: version 5.14
    • file: version 5.41
    • fribidi: version 1.0.11
    • fuse3: version 3.10.5
    • gd: version 2.3.3
    • gdbm: version 1.22
    • git: version 2.33.1
    • glib2: version 2.70.0
    • glibc-zoneinfo: version 2021e
    • gnutls: version 3.7.2
    • grep: version 3.7
    • gzip: version 1.11
    • harfbuzz: version 3.0.0
    • haveged: version 1.9.15
    • htop: version 3.1.1
    • iproute2: version 5.14.0
    • jansson: version 2.14
    • json-glib: version 1.6.6
    • libXi: version 1.8
    • libarchive: version 3.5.2
    • libedit: version 20210910_3.1
    • libepoxy: version 1.5.9
    • libgcrypt: version 1.9.4
    • libgudev: version 237
    • libjpeg-turbo: version 2.1.1
    • libssh: version 0.9.6
    • libssh2: version 1.10.0
    • libtpms: version 0.9.0
    • libvirt: version 7.8.0
    • libvirt-php: version 0.5.6a
    • libwebp: version 1.2.1
    • libxkbcommon: version 1.3.1
    • lvm2: version 2.03.13
    • mc: version 4.8.27
    • mcelog: version 179
    • nano: version 5.9
    • ncurses: version 6.3
    • nghttp2: version 1.46.0
    • nginx: version 1.19.10
    • ntfs-3g: version 2021.8.22
    • openssh: version 8.8p1
    • openssl: version 1.1.1l
    • openssl-solibs: version 1.1.1l
    • pam: version 1.5.2
    • pango: version 1.48.10
    • pcre2: version 10.38
    • php: version 7.4.24
    • qemu: version 6.1.0
    • samba: version 4.15.0
    • sudo: version 1.9.8p2
    • swtpm: version 0.6.1
    • ttyd: version 20211023
    • usbutils: version 014
    • util-linux: version 2.37.2
    • wget: version 1.21.2
    • wireguard-tools: version 1.0.20210914
    • wsdd2: version 1.8.6
    • xfsprogs: version 5.13.0
    • xkeyboard-config: version 2.34
    • xrdb: version 1.2.1
    • xterm: version 369

     

    Linux kernel:

    • version 5.14.15
    • restore CONFIG_X86_X32: x32 ABI for 64-bit mode
    • added so-called "add-relaxable-rmrr-5_8_and_up.patch" modified for this kernel
    • added several ACPI-related CONFIG settings
    • added CONFIG_TCG_TPM and associated TPM chip drivers
    • added CONFIG_NFSD_V4: NFS server support for NFS version 4
    • added CONFIG_USB_NET_AQC111: Aquantia AQtion USB to 5/2.5GbE Controllers support
    • added NFS_V4: NFS client support for NFS version 4
    • oot: md/unriad: version 2.9.19
    • oot: nvidia: version 470.63.01 [via plugin]
    • oot: r8125:version 9.006.04
    • oot: r8152: version 2.15.0

     

    Management:

    • emhttpd: fix regression: user shares should be enabled by default
    • emhttpd: minimize information transmitted by 'stock' UpdateDNS function
    • firefox: version 91.0.r20210823123856 (AppImage)
    • mover: append '.partial' suffix to filename when move in-progess
    • rc.mcelog: mcelog added to base distro
    • rc.nginx: support custom wildcard self-signed certs
    • rc.S: check bz file sha256 during initial boot
    • sysctl: handle net.netfilter.nf_conntrack_count max exceeded (increase setting to 131072)
    • wsdd2: listen only on active interface by default (br0, bond0, or eth0)
    • webgui: remove 'My Servers' skeleton page
    • webgui: present CA-signed certificate subject as a link
    • webgui: Relax update frequency a bit
    • webgui: Docker: Only save templates as v2
    • webgui: Fix pools display on Main page when empty pool exists
    • webgui: Escape double quotes in text input submit
    • webgui: Add 'root' folder protection to filetree
    • webgui: Support multi-language in filetree display
    • webgui: Use background checking for flash corruption
    • webgui: Proactive script security hardening
    • webgui: Diagnostics: add check for DNS Rebinding Protection
    • webgui: Diagnostics: privatize routable IPs
    • webgui: Diagnostics: add url details
    • webgui: Docker: Fix incorrect caching when deleting / recreating image
    • webgui: Silence PHP error on syslinux page if flash drive is missing
    • webgui: various Multi-language corrections
    • webgui: VM Manager: added Windows 11 template and OVMF TPM
    • webgui: VM Manager: add virtio-win-0.1.208.iso download link
    • webgui: Sign-in required to provision/renew Unraid LE SSL certificate
    • Like 10
    • Thanks 4



    User Feedback

    Recommended Comments



    On 2/7/2022 at 11:39 AM, Noim said:

    For me there are two broken things:

     

    1. The array page:

    501003976_Screenshot2022-02-07at18_36_32.thumb.png.72ac597373e0e1229d94b98a6436de8e.png

     

    2. The cpu stats:

    2025339045_Screenshot2022-02-07at18_36_43.png.52e41299d12f4e88a23cca0c19e9247b.png

     

     

    I see the same issue on multiple devices and different browsers

    Link to comment
    On 2/8/2022 at 2:29 PM, Noim said:

    And it just brakes randomly sometimes. After some time it starts working again, and then randomly brakes again. 

     

     

    Version 1.34.81 Chromium: 97.0.4692.99 (Official Build) (x86_64) Brave

     

    And no request gets blocked if I look into dev tools. 

     

    And I also expect there should be some kind of ws message. I think this is why it shows nothing:

    193802698_Screenshot2022-02-08at14_27_30.thumb.png.9ba1bd2771cc115e7a86052e7513fa3a.png

     

    Maybe I am dum and did something wrong, but dk what. 


    So far it didn't brake in safari. 

     

     

    This happens only with Brave, it sometimes gets stuck and appears to be a bug with this browser.

    The solution is to completely close the browser (close any open pages) and re-open the browser again. Clearing the cache doesn’t work.

    Link to comment

    Hi!
    One of the issues I have preventing me from using UnRaid on my main PC is a Christmas tree effect since I cannot use OpenRGB to set a color of the RGB (I'm using a fixed color) and have rainbows all around.

    Required kernel patch for SMBus support (https://github.com/P3R-CO/openrgb-container) was requested multiple times by many people. Will it be finally integrated? Is it this much trouble to include it?

    Alternatively (as a temporary solution) - did someone make a step-by-step instruction on how to update UnRaid's kernel with this patch (could not find it)?

     

     

    Regards,

    Daniel

    Edited by DhanOS
    Link to comment

    Thanks for giving us ipvlan. 

     

    I wish this was available a few years ago.  No more macvlan unraid lockups since upgrading to 6.10.0-rc2 and switching to ipvlan.

     

    My machine was locking up every second day, but now I haven't had a lockup for over a month.

     

     

    • Like 2
    Link to comment

    I am not sure if this is an issue with rc2 or just in general.  but it seems while the management access screen shows the cert as not expiring until next month, the browser is showing it has already expired.

     

    image.thumb.png.4312d2ab393b7d8bf5f0c72f3bc9dfc6.png

    image.png.c8c4ff18731fb1c1aa490474dae27bb8.png

    Link to comment
    5 minutes ago, dorgan said:

    I am not sure if this is an issue with rc2 or just in general.  but it seems while the management access screen shows the cert as not expiring until next month, the browser is showing it has already expired.

    I was able to work around this by viewing the source, removing the disabled attribute from the renew button and then clicking on the renew button.

    Link to comment
    On 2/27/2022 at 8:05 PM, DhanOS said:

    Hi!
    One of the issues I have preventing me from using UnRaid on my main PC is a Christmas tree effect since I cannot use OpenRGB to set a color of the RGB (I'm using a fixed color) and have rainbows all around.

    Required kernel patch for SMBus support (https://github.com/P3R-CO/openrgb-container) was requested multiple times by many people. Will it be finally integrated? Is it this much trouble to include it?

    Alternatively (as a temporary solution) - did someone make a step-by-step instruction on how to update UnRaid's kernel with this patch (could not find it)?

     

     

    Regards,

    Daniel

    If you have a supported system (https://github.com/liquidctl/liquidctl#supported-devices) you might want to look at image.png

    • Like 1
    Link to comment

    Hi All

    I normally jump on the RC's when they come out but 6.10 i have not mainly because im down to one server now.  I am curious when rc3 is coming rc2 came out back in September usually the updates are much faster than this. I hope its not a sign that unraid is losing focus or having other business related issues

    Link to comment

    Are there any nightly builds of 6.10 that we can use to test with? Lack of Alder Lake support is killing me.

    Edited by flyize
    Link to comment

    Not sure why RC cycle takes sooooo long this time around.
    Wonder if they are waiting for something specific, or there is an issue that cannot yet be resolved (or reverted)...

     

    Edited by NLS
    Link to comment
    1 hour ago, Can0n said:

    I am curious when rc3 is coming rc2 came out back in September usually the updates are much faster than this.

     

    It's still been 4 months, but note that RC2 didn't come out until November.

    • Like 1
    Link to comment

    From Unraid monthly newsleter email send about 1 week ago,  Community Manager Spencer J said: "we are still wrapping up some final changes to an internal rc3 version so be on the lookout for a new public 6.10-rc3 release coming soon."

    Link to comment

    my guess is that because this is a full version release from 9x to 10, there are a lot of changes and upgrades to test.  The dot releases 9.x to 9.x were pretty fast.  I remember the old 4x to 5x took a long time too.   The important thing is that it's solid with as few bugs as possible when they do release it.  :)

    Link to comment

    It seems that running the RC2 I'm limited in reads from my array and cache to about 750 Mb/s. Rolling back to 6.9 gets me back to 1 Gb/s. Went back and forth a few times and can constantly reproduce it. No issues with writes though.

    Link to comment
    40 minutes ago, stuoningur said:

    It seems that running the RC2 I'm limited in reads from my array and cache to about 750 Mb/s. Rolling back to 6.9 gets me back to 1 Gb/s. Went back and forth a few times and can constantly reproduce it. No issues with writes though.

    Did you report it as a bug?

    Link to comment
    2 hours ago, optiman said:

    Did you report it as a bug?

    I foolishly believed reporting in the thread was the way to go, but I reported it now separately as well.

    Link to comment
    51 minutes ago, stuoningur said:

    I foolishly believed reporting in the thread was the way to go, but I reported it now separately as well.

    good to do both.  And if you didn't already, be sure to attach your diag file

    • Upvote 1
    Link to comment
    5 hours ago, NLS said:

    Not sure why RC cycle takes sooooo long this time around.
    Wonder if they are waiting for something specific, or there is an issue that cannot yet be resolved (or reverted)...

     

    I know I saw this elsewhere but the primary delay seems to be the Slackware dependency.  Slackware finally revised to 15 and RC2 looking at /etc/os-release was using a Slackware 15 RC.  Slackware 15 didn't get officially released until the beginning of Feb 2022.  Slackware is still pushing updates like they are going out of style as well.  That said, Slackware is known to prioritize stability and they hadn't done a major point release since 2016 (14.2) and 2012 is when 14 came out so it was a major upgrade from a dependency perspective.

     

    I imagine a full regression and any development for Unraid's work on top of that simply takes time.  I'm equally frustrated since have had RC2 and there have been various KPs popping up from time-to-time.  Unraid has announced a copy of times they are getting close so I imagine they are.  That said, risking data isn't my idea of a good time although the hypocrite in me is running a RC so not sure what that says.

     

    Anyways, I have no inside knowledge but wanted to share what is buried elsewhere in the forums, etc.

    Edited by txwireless
    Link to comment
    1 hour ago, k2U79!KvW9AXpwAc said:

     

    I started a thread in the Security forum to discuss this vulnerability:

     

     

     

    I just read that last night i hope so too current 6.9.2 kernel is impacted by it

     

    Link to comment
    On 3/7/2022 at 9:34 AM, manHands said:

     

    It's still been 4 months, but note that RC2 didn't come out until November.



    Actually it was posted here in September not November hence the 6 months since release

    image.png.503a7f9eb443ef050627922acf162fdb.png

    Link to comment
    3 minutes ago, Can0n said:



    Actually it was posted here in September not November hence the 6 months since release

    image.png.503a7f9eb443ef050627922acf162fdb.png

    They tend to pre-prepare posts for a release and only make them visible once they become available. If you scroll down in the first post you'll see that the date of RC2 is 2021-11-01.

    Link to comment
    2 minutes ago, Taddeusz said:

    They tend to pre-prepare posts for a release and only make them visible once they become available. If you scroll down in the first post you'll see that the date of RC2 is 2021-11-01.



    not in my experience I have always been able to see the updated RC same day it was posted

    the first post did not mention it was now available it was about putty and RSA keys may need to be updated.

    image.thumb.png.7762a154a258119f3404efe4427e8538.png

    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.