Jump to content
  • Unraid OS version 6.7.0-rc1 available


    limetech

    New in Unraid OS 6.7 release:

     

    New Dashboard layout, along with new Settings and Tools icons.  Designed by user @Mex and implemented in collaboration with @bonienl.  We think you will find this is a big step forward.

     

    Time Machine support via SMB.  To enable this feature it is necessary to first turn on Enhanced OS X interoperability on the Settings/SMB page.  Next, select a share to Export for Time Machine in the share SMB Security Settings section.  AFP support is deprecated.

     

    Linux kernel 4.19.  This is the latest Long Term Support kernel.  We will go with this for a while but anticipate
    updating to 4.20 or even 5.0 for Unraid 6.7.0 stable.  Here are some other kernel-related updates:

    • Added TCP "BBR Congestion control" and made it the default.  This should improve network throughput but probably not too many users will notice anything different.
    • Added Bluetooth support in the Linux kernel.  We did not add the user-space tools so this will be mostly useful to support Bluetooth in docker containers.
    • AMD firmware update for Threadripper.

     

    Ignore case in validating user share names.  If there are multiple top-level directories which differ only in case, then we use the first such share name encountered, checking in order: cache, disk1, disk2, ..., diskN.  Additional top-level directories encountered will be ignored.  For example, suppose we have:

    /mnt/cache/ashare
    /mnt/disk1/Ashare
    /mnt/disk2/ashare

    The name of the exported share will be 'ashare' and will consist of a union of /mnt/cache/ashare and /mnt/disk2/ashare.  The contents of /mnt/disk1/Ashare will not show up in /mnt/user/ashare.

     

    If you then delete the contents of /mnt/user/ashare followed by deleting the 'ashare' share itself, this will result in share 'Ashare' becoming visible.  Similar, if you delete the contents of /mnt/cache/ashare (or gets moved), then you will now see share 'Ashare' appear, and it will look like the contents of 'ashare' are missing!  Thankfully very few (if any) users should be affected by this, but handles a corner case in both the presentation of shares in windows networking and storage of share config data on the USB flash boot device.

     

    New vfio-bind method.  Since it appears that the xen-pciback/pciback kernel options no longer work, we introduced an alternate method of binding, by ID, selected PCI devices to the vfio-pci driver. This is accomplished by specifying the PCI ID(s) of devices to bind to vfio-pci in the file 'config/vfio-pci.cfg' on the USB flash boot device.  This file should contain a single line that defines the devices:

    BIND=<device> <device> ...

    Where <device> is a Domain:Bus:Device.Function string, for example,

    BIND=02:00.0

    Multiple device should be separated with spaces.

     

    The script /usr/local/sbin/vfio-pci is called very early in system start-up, right after the USB flash boot device is
    mounted but before any kernel modules (drivers) have been loaded.  The function of the script is to bind each specified device to the vfio-pci driver, which makes them available for assignment to a virtual machine, and also prevents the Linux kernel from automatically binding them to any present host driver.

     

    In addition, and importantly, this script will bind not only the specified device(s), but all other devices in the same IOMMU group as well.  For example, suppose there is an NVIDIA GPU which defines both a VGA device at 02:00.0 and an audio device at 02.00.1.  Specifying a single device (either one) on the BIND line is sufficient to bind both device to vfio-pci.  The implication is that either all devices of an IOMMU group are bound to vfio-pci or none of them are.

     

    Added 'telegram' notification agent support - thank you @realies

     

    Finally, we updated several base packages, including move to Samba 4.9 and docker 18.09, and fixed a number of minor bugs.

     

    Version 6.7.0-rc1 2019-01-21

    Base distro:

    • aaa_elflibs: version 15.0 (rev 3)
    • acpid: version 2.0.31
    • adwaita-icon-theme: version 3.30.1
    • at: version 3.1.23
    • at-spi2-atk: version 2.30.0
    • at-spi2-core: version 2.30.0
    • atk: version 2.30.0
    • bin: version 11.1 (rev 3)
    • bluez: version 4.101
    • bluez firmware: version 1.2
    • bridge-utils: version 1.6
    • btrfs-progs: version v4.19.1
    • ca-certificates: version 20181210
    • cairo: version 1.16.0
    • cifs-utils: version 6.8
    • coreutils: version 8.30 (rev 4)
    • curl: version 7.63.0
    • cyrus-sasl: version 2.1.27
    • dbus: version 1.12.12
    • dhcpcd: version 7.0.8
    • diffutils: version 3.7
    • dmidecode: version 3.2
    • dnsmasq: version 2.80
    • docker: version 18.09.1
    • e2fsprogs: version 1.44.5
    • etc: version 15.0 (rev 9)
    • ethtool: version 4.19
    • file: version 5.35
    • findutils: version 4.6.0
    • fribidi: version 1.0.5
    • gdbm: version 1.18.1
    • gdk-pixbuf2: version 2.38.0
    • git: version 2.20.1
    • glibc-zoneinfo: version 2018g
    • glib2: version 2.58.2
    • gnutls: version 3.6.5 (CVE-2018-16868)
    • gptfdisk: version 1.0.4
    • graphite2: version 1.3.13
    • grep: version 3.3
    • gtk+3: version 3.24.2
    • gzip: version 1.10
    • harfbuzz: version 2.3.0
    • haveged: version 1.9.4
    • hdparm: version 9.58
    • hostname: version 3.21
    • hwloc: version 1.11.11
    • icu4c: version 63.1
    • inotify-tools: version 3.20.1
    • intel-microcode: version 20180807a
    • iproute2: version 4.19.0
    • iptables: version 1.8.2
    • iputils: version s20180629
    • irqbalance: version 1.5.0
    • jansson: version 2.12
    • kernel-firmware: version 20181218_0f22c85
    • keyutils: version 1.6
    • libSM: version 1.2.3
    • libX11: version 1.6.7
    • libarchive: version 3.3.3
    • libcap-ng: version 0.7.9
    • libdrm: version 2.4.96
    • libedit: version 20181209_3.1
    • libepoxy: version 1.5.3
    • libestr: version 0.1.11
    • libevdev: version 1.6.0
    • libgcrypt: version 1.8.4
    • libgpg-error: version 1.33
    • libjpeg-turbo: version 2.0.1
    • libnftnl: version 1.1.2
    • libpcap: version 1.9.0
    • libpng: version 1.6.36
    • libpsl: version 0.20.2
    • libpthread-stubs: version 0.4 (rev 3)
    • librsvg: version 2.44.11
    • libtirpc: version 1.1.4
    • libvirt: version 4.10.0
    • libwebp: version 1.0.1
    • libxcb: version 1.13.1
    • lm_sensors: version 3.5.0
    • logrotate: version 3.15.0
    • lvm2: version 2.03.02
    • lzip: version 1.20
    • lz4: version 1.8.3
    • mc: version 4.8.22
    • mesa: version 18.3.0
    • miniupnpc version: 2.1
    • nano: version 3.2
    • ncurses: version 6.1_20181110
    • netatalk: version 3.1.12 (CVE-2018-1160)
    • nettle: version 3.4.1 (CVE-2018-16869)
    • nghttp2: version 1.35.1
    • nginx: version 1.14.2 (+ nchan 1.2.3) (CVE-2018-16843, CVE-2018-16844, CVE-2018-16845)
    • ntp: version 4.2.8p12 (rev 5)
    • openldap-client: version 2.4.47
    • pciutils: version 3.6.2
    • perc2: version 10.32
    • php: version 7.2.13
    • pixman: version 0.36.0
    • pkgtools: version 15.0 (rev 23)
    • pv: version 1.6.6
    • qemu: version 3.1.0
    • rpcbind: version 1.2.5
    • rsyslog: version 8.40.0
    • samba: version 4.9.4 (CVE-2018-14629, CVE-2018-16841, CVE-2018-16851, CVE-2018-16852, CVE-2018-16853, CVE-2018-16857)
    • sed: version 4.7
    • shadow: version 4.6
    • shared-mime-info: version 1.10
    • smartmontools: version 7.0
    • spice: version 0.14.1
    • spice-protocol: version 0.12.14
    • sqlite: version 3.26.0
    • sudo: version 1.8.26
    • sysvinit-scripts: version 2.1 (rev 24)
    • sysvinit: version 2.93
    • tar: version 1.30 (rev 3)
    • tree: version 1.8.0
    • ttyd: version 1.4.2
    • util-linux: version 2.33
    • wget: version 1.20
    • xauth: version 1.0.10 (rev 3)
    • xfsprogs: version 4.19.0
    • wget: version 1.20.1
    • xkeyboard-config: version 2.25
    • xterm: version 341
    • zstd: version 1.3.8

    Linux kernel:

    • version: 4.19.16
    • OOT Intel 10Gbps network driver: ixgbe: version 5.5.3
    • OOT Tehuti 10Gbps network driver: tn40xx: version 0.3.6.17
    • added drivers:
    • CONFIG_USB_SERIAL_CH341: USB Winchiphead CH341 Single Port Serial Driver
    • added TCP BBR congestion control kernel support and set as default:
    • CONFIG_NET_KEY: PF_KEY sockets
    • CONFIG_TCP_CONG_BBR: BBR TCP
    • CONFIG_NET_SCH_FQ: Fair Queue
    • CONFIG_NET_SCH_FQ_CODEL: Fair Queue Controlled Delay AQM (FQ_CODEL)
    • added Bluetooth kernel support:
    • CONFIG_BT: Bluetooth subsystem support
    • CONFIG_BT_BREDR: Bluetooth Classic (BR/EDR) features
    • CONFIG_BT_RFCOMM: RFCOMM protocol support
    • CONFIG_BT_RFCOMM_TTY: RFCOMM TTY support
    • CONFIG_BT_BNEP: BNEP protocol support
    • CONFIG_BT_BNEP_MC_FILTER: Multicast filter support
    • CONFIG_BT_BNEP_PROTO_FILTER: Protocol filter support
    • CONFIG_BT_HIDP: HIDP protocol support
    • CONFIG_BT_HS: Bluetooth High Speed (HS) features
    • CONFIG_BT_LE: Bluetooth Low Energy (LE) features
    • CONFIG_BT_HCIBTUSB: HCI USB driver
    • CONFIG_BT_HCIBTUSB_AUTOSUSPEND: Enable USB autosuspend for Bluetooth USB devices by default
    • CONFIG_BT_HCIBTUSB_BCM: Broadcom protocol support
    • CONFIG_BT_HCIBTUSB_RTL: Realtek protocol support
    • CONFIG_BT_HCIUART: HCI UART driver
    • CONFIG_BT_HCIUART_H4: UART (H4) protocol support
    • CONFIG_BT_HCIUART_BCSP: BCSP protocol support
    • CONFIG_BT_HCIUART_ATH3K: Atheros AR300x serial support
    • CONFIG_BT_HCIUART_AG6XX: Intel AG6XX protocol support
    • CONFIG_BT_HCIUART_MRVL: Marvell protocol support
    • CONFIG_BT_HCIBCM203X: HCI BCM203x USB driver
    • CONFIG_BT_HCIBPA10X: HCI BPA10x USB driver
    • CONFIG_BT_HCIVHCI: HCI VHCI (Virtual HCI device) driver
    • CONFIG_BT_MRVL: Marvell Bluetooth driver support
    • CONFIG_BT_ATH3K: Atheros firmware download driver
    • md/unraid: version 2.9.5 (kernel BUG if read phase of read/modify/write with FUA flag set fails on stripe with multiple read failures)
    • patch: PCI: Quirk Silicon Motion SM2262 NVMe controller reset
    • patch: support Mozart 395S chip

    Management:

    • add early vfio-bind utility
    • fix: docker log rotation
    • fix: inconsistent share name case
    • fix: terminal instances limited to 8 (now lifted)
    • restore PHP E_WARNING in /etc/php/php.ini
    • support Apple Time Machine via SMB
    • update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt}
    • webgui: New icon reference
    • webgui: Added new font icons
    • webgui: added new case icons
    • webgui: Revamped dashboard page
    • webgui: Replaced orb png icons by font-awesome
    • webgui: Position context menu always left + below icon
    • webgui: Do not capitalize path names in title of themes Azure and Gray
    • webgui: Allow plugins to use font awesome for icon
    • webgui: sort notification agents alphabetically, add telegram notifications
    • webgui: Dashboard: use disk thresholds for utlization bars
    • webgui: VM manager: remove and rebuild USB controllers
    • webgui: Fixed: slots selection always disabled after "New Config"
    • webgui: Fix Background color when installing container
    • webgui: Fixed share/disk size calculation when names include space
    • webgui: Add log-size and log-file options to docker run command
    • webgui: Escape quotes on a containers template
    • webgui: Prevent update notification if plugin is not compatible
    • webgui: other GUI enhancements

    Edited by limetech

    • Like 5
    • Upvote 6


    User Feedback

    Recommended Comments



    Updated with no Issues on my Threadripper system.

    patch_level=0x08001137 is new microcode.

     

    Nice new icons, and the new dashboard is sexy

     

    One nit pick, can the Container size button be moved beside Add container button?

     

    It's out of place on the end.

     

    Also bash-5.0.002 is out and fixes some security issues.

    Edited by Dazog

    Share this comment


    Link to comment
    Share on other sites

    updated & all is great, I love the new Dashboard.

    Great work guys.

    Share this comment


    Link to comment
    Share on other sites

    Excellent Job everyone the new dashboard is fantastic. Nice to get proper Temp placement and realtime utilization across all aspects on the dashboard.

     

    Share this comment


    Link to comment
    Share on other sites

    For those that don't want to upgrade to RC, can somebody do a few screenshots and let us see?

     

    And do a quick review? That would be awesome.

    Share this comment


    Link to comment
    Share on other sites

    I have a suggestion about the new dashboard.

     

    I would love to be able to rearrange the tiles, and turn them on or off completely.

    • Like 1
    • Upvote 3

    Share this comment


    Link to comment
    Share on other sites

    new dash looks great! only issue I found was my plex docker (plexinc repository) wont start :( just gets a pop up with "server error"

    • Like 1

    Share this comment


    Link to comment
    Share on other sites

    Updated without issue on backup/test server.

     

    I'll add my thumbs up for the new dashboard as well; really nice. 👍

     

    Obviously, plugin authors (dockers as well?) will need to update their plugins with the new icon style.  Until that happens, the mixture of old and new icon styles on the settings and plugin pages is a bit of a visual jumble.  I am sure that will all get sorted in time.

    • Upvote 1

    Share this comment


    Link to comment
    Share on other sites

    I love the new update and the updated theme looks great. However, I have one issue with the update. Under the UPS panel, it will not show the actual watts that's being used. Now if you go to UPS Settings, it shows. Anyway we can add "UPS Load" showing the actual watts?

     Overall, great work LimeTech.

    Edited by xkraz

    Share this comment


    Link to comment
    Share on other sites

    Anyone else having troubles with python from nerdtools? I can't pip install anything (SSL errors)

    Share this comment


    Link to comment
    Share on other sites

    Updated.. my dreams of having a fixed threadripper cache native supported dashed sadly. QEMU 3.1 doesn't seem to have the fix either. For some reason it broke my USB controller though for my gaming machine. Machine won't boot with it put in the VM.

     

    Edit:

     

    Reverting sadly due to being able to figure out why the passthrough of the usb controller is causing the machine to fail booting.

     

    Edit 2:

     

    Interestingly when I reverted back it doesn't fix it either.. Time to play the guessing game #_#..

     

    Edit 3:

    Unplugged all my usb devices and plugged them in one at a time. For some reason my astro gaming headset is causing my VM to not boot. Very strange..

    Edited by Jerky_san

    Share this comment


    Link to comment
    Share on other sites

    Just updated my test / backupserver. Everything went smooth.

    When i first read all the posts about new gui, i thought the the whole gui got a rewamp 🙄 but the new dashboard looks good. 

     

    +1 for Jonathanm suggestion. 

    2 hours ago, jonathanm said:

    I have a suggestion about the new dashboard.

     

    I would love to be able to rearrange the tiles, and turn them on or off completely.

    Share this comment


    Link to comment
    Share on other sites

     

    I read in the patch notes that:

    Quote

    New vfio-bind method.  Since it appears that the xen-pciback/pciback kernel options no longer work, we introduced an alternate method of binding, by ID, selected PCI devices to the vfio-pci driver. This is accomplished by specifying the PCI ID(s) of devices to bind to vfio-pci in the file 'config/vfio-pci.cfg' on the USB flash boot device.  This file should contain a single line that defines the devices:

    Currently I have the following on my Syslinux Configuration:

    kernel /bzimage
    append vfio-pci.ids=10de:1b81,10de:10f0 pci=noaer modprobe.blacklist=nouveau initrd=/bzroot

    Which passes through my nVidia card as well as blacklists it from the nouveau driver...  If I am reading that correctly, everyone with passthrough will need to change these after 6.7.0 to something like:

    kernel /bzimage
    append BIND=01:00.0 pci=noaer modprobe.blacklist=nouveau initrd=/bzroot

    Am I reading that correctly?  Or does this only affect vfio from the booted command line?

    Edited by Warrentheo

    Share this comment


    Link to comment
    Share on other sites

    im also guessing what todo ;)

     

    updated and everything seems to work so far, passthrough nvidia and USB onboard without changing anything yet.

     

    currently i have this in my flash config

     

    kernel /bzimage
    append pcie_acs_override=downstream isolcpus=2,3,4,5,8,9,10,11 vfio-pci.ids=8086:a2af vfio-pci.ids=1106:3483 initrd=/bzroot

     

    when i read this correct i remove the vfio part here and create a file called vfio-pci in /config

     

    then i would add those 4 entries to vfio my 2 usb controllers and 2 nvidia cards ?

     

    BIND=00:14:0 07:00:0 01:00.0 04:00.0

     

    so these should be free for VM´s, just a little worried about IOMMU group 5 cause the Signal processing ... is included ...

     

    IOMMU group 5:[8086:a2af] 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller

    [8086:a2b1] 00:14.2 Signal processing controller: Intel Corporation 200 Series PCH Thermal Subsystem

     

    IOMMU group 20:[1106:3483] 07:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01)

     

    IOMMU group 15:[10de:1b81] 01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1)

    [10de:10f0] 01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)

     

    IOMMU group 18:[10de:1d01] 04:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1)

    [10de:0fb8] 04:00.1 Audio device: NVIDIA Corporation GP108 High Definition Audio Controller (rev a1)

     

    Share this comment


    Link to comment
    Share on other sites
    1 hour ago, perhansen said:

    When i first read all the posts about new gui, i thought the the whole gui got a rewamp

    There are (subtile) enhancements in several places in the GUI. The most obvious enhancement is the Dashboard of course.

    1 hour ago, perhansen said:

    +1 for Jonathanm suggestion. 

    Please make a feature request if you have a suggestion.

    This RC is to comment on the current implementation and report any bugs.

    Share this comment


    Link to comment
    Share on other sites
    1 hour ago, Warrentheo said:

     

    I read in the patch notes that:

    Currently I have the following on my Syslinux Configuration:

    
    kernel /bzimage
    append vfio-pci.ids=10de:1b81,10de:10f0 pci=noaer modprobe.blacklist=nouveau initrd=/bzroot

    Which passes through my nVidia card as well as blacklists it from the nouveau driver...  If I am reading that correctly, everyone with passthrough will need to change these after 6.7.0 to something like:

    
    kernel /bzimage
    append BIND=01:00.0 pci=noaer modprobe.blacklist=nouveau initrd=/bzroot

    Am I reading that correctly?  Or does this only affect vfio from the booted command line?

    Using the vfio--pci kernel parameter in syslinux.cfg is an alternate approach to binding the vfio-pci driver to a device. In this case the device is specified using its vendor:product ID which is not unique if you have more than one of the same device.  This method still works fine if this restriction is acceptable.

     

    The method we added was to specify devices to bind to vfio-pci driver based on their PCI bus ID.  This is done via config/vfio-pci.cfg file on your usb flash boot device, instead of using vfio-pci kernel parameter.  The advantage of this method is that you can have multiple devices of exact same type and select which one(s) to pass through to VM's.  The disadvantage is that the PCI ID's for a device can change if you change which slot a device is plugged into, or make other h/w change such as replacing the motherboard.

     

    In your case you don't have to change anything.  But that 'modprobe.blacklist' parameter is unnecessary since Unraid OS (currently) does not include that driver.

    Share this comment


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

    when i read this correct i remove the vfio part here and create a file called vfio-pci in /config

     

    then i would add those 4 entries to vfio my 2 usb controllers and 2 nvidia cards ?

     

    BIND=00:14:0 07:00:0 01:00.0 04:00.0

     

    so these should be free for VM´s, just a little worried about IOMMU group 5 cause the Signal processing ... is included ...

    Correct.  I would be interested in your results doing exactly that and verify that everything works correctly.  re: the Signal processor: It is my understanding that for proper operation all the devices of an IOMMU group must be isolated (bound to vfio-pci) or none of them.  Maybe you can move that USB controller to another slot in order to put into its own IOMMU group?

    Share this comment


    Link to comment
    Share on other sites

    Updated fine after not reading the release notes 5 minutes before I had to leave for work (I obviously like to live dangerously..), all worked fine, back up and running with any issues at all. Liking the new interface, many thanks for your work all.

    Edited by J89eu

    Share this comment


    Link to comment
    Share on other sites
    6 hours ago, MarkGlover said:

    just gets a pop up with "server error"

    This happens due to file system corruption. Try a repair or easier delete the existing docker image and recreate it.

    Share this comment


    Link to comment
    Share on other sites

    @limetech 

    I have these 2 nics as part of the motherboard

    [8086:1539] 04:00.0 Ethernet controller:
    [8086:1539] 06:00.0 Ethernet controller:

    I was using in the syslinux configuration:

    xen-pciback.hide=(06:00.0)

    to stop Unraid from using that nic for itself as it had the same id as another nic on the motherboard as above.

     

    I have upgraded to 6.7 yet the nic is still hidden from the OS and it passes through fine to the vm.

    So the is this something that works now. But this kernel option will no longer work

    in future/final 6.7 so we are moving to the config/vfio-pci.cfg file in preparation?

    Share this comment


    Link to comment
    Share on other sites

    Upgraded from v6.6.6 with no problems. Love the new look of the Dashboard and other visual enhancements throughout the WebUI. Thanks and a job well done to all those who worked on this release and provided valuable feedback!!!

    Share this comment


    Link to comment
    Share on other sites

    Would a kind soul care to post a screenshot of the new dashboard for those of us not running RC versions?

     

    Edit: Never mind, someone on Reddit posted some. Looks really nice!

     

    Off the bat, the only thing that sticks out at me is that the tile on the top left - server description - seemed to be taking up a lot of space, and the information is largely duplicated on the right side of the banner. Might be worth thinking about condensing/removing some of this to free up space for the main interest items.

     

    qN8qEet.png

    3lccRv8.png

    Edited by -Daedalus
    • Like 1
    • Upvote 1

    Share this comment


    Link to comment
    Share on other sites
    Mex

    Posted (edited)

    This is from my design file, so it differs a little bit from the implemented solution, but it should give you a general feel about how it looks. (Header/menu and bottom statusbar is unchanged aside from icons)

     

    Edit: So I should remember to refresh before posting. Anyway you might not have seen it yet, but the logo on the "server description" tile can be edited, and we have included a selection of popular cases to start you off!

     

    image.thumb.png.89f8401b86b0062f327bfea50ff9297a.png

     

    Edited by Mex
    • Like 6
    • Upvote 1

    Share this comment


    Link to comment
    Share on other sites
    44 minutes ago, -Daedalus said:

    Might be worth thinking about condensing/removing some of this to free up space for the main interest items.

    All the tiles can be minimised/collapsed so they dont have to take up a lot of space

    Share this comment


    Link to comment
    Share on other sites



    Guest
    This is now closed for further comments

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