• Unraid OS version 6.6.0-rc1 available


    limetech
    • Closed

    Please report only issues/bugs which are new in the prerelease.

     

    We've been holding back on this release a few days waiting for updated Intel ixgbe (10Gbit) OOT driver which builds correctly with 4.18 kernel.  But no update yet so this release uses 4.17.19 kernel.

     

    Every major subsystem has been updated.  In addition @bonienl has added some really cool features and update the default themes to match our new branding.

     

    Release notes:

    Version 6.6.0-rc1 2018-08-31

    Base distro:

    • aaa_base: version 14.2 (rev 5)
    • aaa_elflibs: version 15.0 (rev 2)
    • acl: version 2.2.53
    • acpid: version 2.0.29
    • adwaita-icon-theme: version 3.28.0
    • appres: version 1.0.5 (rev 2)
    • at-spi2-atk: version 2.26.2
    • at-spi2-core: version 2.28.0
    • at: version 3.1.20 (rev 5)
    • atk: version 2.28.1
    • attr: version 2.4.48
    • avahi: version 0.7 (rev2)
    • bash: version 4.4.023
    • bin: version 11.1 (rev 2)
    • bridge-utils: version 1.5 (rev 2)
    • btrfs-progs: version v4.17
    • bzip2: version 1.0.6 (rev 3)
    • ca-certificates: version 20180409
    • cairo: version 1.15.12
    • celt051: version 0.5.1.3 (rev 2)
    • cifs-utils: version 6.7 (rev 2)
    • coreutils: version 8.29 (rev 2)
    • cpio: version 2.12 (rev 2)
    • cpufrequtils: version 08 (rev 2)
    • cryptsetup: version 1.7.5 (rev 2)
    • curl: version 7.61.0 (CVE-2018-1000300, CVE-2018-1000301, CVE-2018-0500)
    • cyrus-sasl: version 2.1.27_rc8
    • db48: version 4.8.30 (rev 4)
    • dbus: version 1.12.8
    • dcron: version 4.5
    • dejavu-fonts-ttf: version 2.37 (rev 4)
    • dhcpcd: version 7.0.6
    • diffutils: version 3.6 (rev 2)
    • dmidecode: version 3.1 (rev 2)
    • dnsmasq: version 2.79 (rev 2)
    • docker: version 18.06.1-ce
    • e2fsprogs: version 1.44.2
    • ebtables: version 2.0.10 (rev 2)
    • editres: version 1.0.7 (rev 2)
    • elvis: version 2.2_0 (rev 4)
    • encodings: version 1.0.4 (rev 2)
    • etc: version 15.0 (rev 6)
    • ethtool: version 4.17
    • eudev: version 3.2.5 (rev2)
    • file: version 5.33
    • findutils: version 4.4.2 (rev 2)
    • flex: version 2.6.4 (rev 3)
    • floppy: version 5.5 (rev 2)
    • fontconfig: version 2.12.6 (rev 2)
    • freetype: version 2.9 (rev 2)
    • fribidi: version 1.0.4
    • fuse: version 2.9.7 (rev3)
    • gawk: version 4.2.1 (rev 2)
    • gd: version 2.2.5 (rev2)
    • gdbm: version 1.15
    • gdk-pixbuf2: version 2.36.12
    • genpower: version 1.0.5 (rev 3)
    • getty-ps: version 2.1.0b (rev 4)
    • glew: version 2.1.0 (rev 2)
    • glib2: version 2.56.1
    • glibc-solibs: version 2.27 (rev 4)
    • glibc-zoneinfo: version 2018e (rev 3)
    • glibc: version 2.27 (rev 4)
    • glu: version 9.0.0 (rev 2)
    • gmp: version 6.1.2 (rev 2)
    • gnome-themes-standard: version 3.22.3 (rev 2)
    • gnupg: version 1.4.23 (CVE-2018-12020)
    • gnutls: version 3.6.2 (rev 2)
    • gptfdisk: version 1.0.3 (rev 2)
    • grep: version 3.1 (rev 2)
    • gtk+3: version 3.22.30
    • gzip: version 1.9 (rev 2)
    • harfbuzz: version 1.8.1
    • haveged: version 1.9.2
    • hdparm: version 9.56
    • hicolor-icon-theme: version 0.17 (rev 2)
    • hostname: version 3.18 (rev 2)
    • htop: version 2.2.0
    • icu4c: version 61.1
    • imlib2: version 1.5.1
    • inetd: version 1.79s (rev 11)
    • infozip: version 6.0 (rev 4)
    • inotify-tools: version 3.14 (rev 2)
    • intel-microcode: version 20180807
    • iproute2: version 4.17.0
    • iptables: version 1.6.2 (rev 2)
    • iputils: version s20140519 (rev 2)
    • kernel-firmware: version 20180814_f1b95fe
    • keyutils: version 1.5.10 (rev 2)
    • kmod: version 25 (rev 2)
    • lbzip2: version 2.5
    • less: version 530 (rev 3)
    • libaio: version 0.3.111
    • libarchive: version 3.3.2 (rev 3)
    • libcap-ng: version 0.7.8 (rev 3)
    • libcgroup: version 0.41 (rev 5)
    • libcroco: version 0.6.12 (rev 2)
    • libdaemon: version 0.14 (rev2)
    • libdmx: version 1.1.4
    • libdrm: version 2.4.92
    • libedit: version 20180525_3.1
    • libee: version 0.4.1 (rev 2)
    • libepoxy: version 1.4.3 (rev 2)
    • libestr: version 0.1.10 (rev 2)
    • libevdev: version 1.5.9 (rev 2)
    • libevent: version 2.1.8 (rev 3)
    • libfastjson: version 0.99.8 (rev2)
    • libffi: version 3.2.1 (rev 2)
    • libfontenc: version 1.1.3 (rev 2)
    • libgcrypt: version 1.8.3 (CVE-2018-0495)
    • libgpg-error: version 1.31
    • libgudev: version 232 (rev 2)
    • libICE: version 1.0.9 (rev 3)
    • libidn: version 1.35
    • libjpeg-turbo: version 1.5.3 (rev 2)
    • liblogging: version 1.0.6 (rev2)
    • libmnl: version 1.0.4 (rev 3)
    • libnetfilter_conntrack: version 1.0.7
    • libnfnetlink: version 1.0.1 (rev 2)
    • libnftnl: version 1.1.0
    • libnl3: version 3.4.0 (rev 2)
    • libpcap: version 1.8.1 (rev 2)
    • libpciaccess: version 0.14 (rev 2)
    • libpng: version 1.6.34 (rev 2)
    • libpthread-stubs: version 0.4 (rev 2)
    • librsvg: version 2.42.5
    • libseccomp: version 2.3.3 (rev2)
    • libSM: version 1.2.2 (rev 3)
    • libssh2: version 1.8.0 (rev 3)
    • libtasn1: version 4.13 (rev 2)
    • libtirpc: version 1.0.3 (rev 2)
    • libunistring: version 0.9.10
    • libunwind: version 1.2.1
    • libusb-compat: version 0.1.5 (rev2)
    • libusb: version 1.0.22
    • libvirt-php: version 0.5.4 (rev3)
    • libvirt: version 4.6.0
    • libwebsockets: version 2.4.2
    • libX11: version 1.6.5 (rev 2)
    • libx86: version 1.1 (rev 3)
    • libXau: version 1.0.8 (rev 3)
    • libXaw: version 1.0.13 (rev 2)
    • libxcb: version 1.13 (rev 2)
    • libXcomposite: version 0.4.4 (rev 3)
    • libXcursor: version 1.1.15 (rev 2)
    • libXdamage: version 1.1.4 (rev 3)
    • libXdmcp: version 1.1.2 (rev 3)
    • libXevie: version 1.0.3 (rev 3)
    • libXext: version 1.3.3 (rev 3)
    • libXfixes: version 5.0.3 (rev 2)
    • libXfont2: version 2.0.3 (rev 2)
    • libXfontcache: version 1.0.5 (rev 3)
    • libXft: version 2.3.2 (rev 4)
    • libXi: version 1.7.9 (rev 2)
    • libXinerama: version 1.1.3 (rev 3)
    • libxkbfile: version 1.0.9 (rev 2)
    • libxml2: version 2.9.8 (rev 2)
    • libXmu: version 1.1.2 (rev 3)
    • libXpm: version 3.5.12 (rev 2)
    • libXrandr: version 1.5.1 (rev 2)
    • libXrender: version 0.9.10 (rev 2)
    • libXres: version 1.2.0 (rev 2)
    • libxshmfence: version 1.3 (rev 2)
    • libxslt: version 1.1.32 (rev 2)
    • libXt: version 1.1.5 (rev 2)
    • libXtst: version 1.2.3 (rev 2)
    • libXxf86dga: version 1.1.4 (rev 3)
    • libXxf86misc: version 1.0.3 (rev 3)
    • libXxf86vm: version 1.1.4 (rev 3)
    • listres: version 1.0.4 (rev 2)
    • lm_sensors: version 3.4.0 (rev 2)
    • logrotate: version 3.14.0 (rev 2)
    • lsof: version 4.91
    • lsscsi: version 0.29
    • lvm2: version 2.02.177
    • lz4: version 1.8.2
    • mc: version 4.8.21
    • mesa: version 18.1.2
    • mkfontdir: version 1.0.7 (rev 2)
    • mkfontscale: version 1.1.3 (rev 2)
    • mozilla-firefox: version 61.0.2 (CVE-2018-12359, CVE-2018-12360, CVE-2018-12361, CVE-2018-12358, CVE-2018-12362, CVE-2018-5156, CVE-2018-12363, CVE-2018-12364, CVE-2018-12365, CVE-2018-12371, CVE-2018-12366, CVE-2018-12367, CVE-2018-12368, CVE-2018-12369, CVE-2018-12370, CVE-2018-5186, CVE-2018-5187, CVE-2018-5188)
    • mpfr: version 4.0.1 (rev 2)
    • mtdev: version 1.1.5 (rev 2)
    • nano: version 2.9.8
    • ncompress: version 4.2.4.4 (rev 2)
    • ncurses: version 6.1_20180616
    • net-tools: version 20170208_479bb4a (rev 2)
    • netatalk: version 3.1.11 (rev2)
    • nettle: version 3.4 (rev 2)
    • network-scripts: version 15.0
    • nghttp2: version 1.32.0 (CVE-2018-1000168)
    • nginx: version 1.14.0
    • ntfs-3g: version 2017.3.23 (rev 2)
    • ntp: version 4.2.8p12 (CVE-2016-1549, CVE-2018-12327)
    • numactl: version 2.0.11 (rev2)
    • openldap-client: version 2.4.46
    • openssh: version 7.7p1
    • openssl-solibs: version 1.1.0i
    • openssl10-solibs: version 1.0.2o
    • openssl: version 1.1.0i (CVE-2018-0732, CVE-2018-0737)
    • p11-kit: version 0.23.12
    • pango: version 1.42.1
    • patch: version 2.7.6 (rev 3) (CVE-2018-1000156)
    • pciutils: version 3.5.6 (rev 2)
    • pcre: version 8.42
    • php: version 7.2.8
    • pixman: version 0.34.0 (rev 2)
    • pkgtools: version 15.0 (rev 20)
    • pm-utils: version 1.4.1 (rev 6)
    • procps-ng: version 3.3.15 (CVE-2018-1124, CVE-2018-1126, CVE-2018-1125, CVE-2018-1123, CVE-2018-1122)
    • qemu: version 3.0.0
    • reiserfsprogs: version 3.6.27 (rev2)
    • rpcbind: version 0.2.4 (rev 4)
    • rsync: version 3.1.3 (rev 2)
    • rsyslog: version 8.36.0
    • samba: version 4.8.4 (CVE-2018-1139, CVE-2018-1140, CVE-2018-10858, CVE-2018-10918, CVE-2018-10919)
    • sed: version 4.5
    • sessreg: version 1.1.1 (rev 2)
    • setxkbmap: version 1.3.1 (rev 2)
    • shadow: version 4.2.1 (rev 4)
    • shared-mime-info: version 1.9 (rev 2)
    • spice: version 0.14.0 (rev2)
    • sqlite: version 3.24.0
    • ssmtp: version 2.64 (rev5)
    • startup-notification: version 0.12 (rev 3)
    • sudo: version 1.8.23
    • sysfsutils: version 2.1.0 (rev 2)
    • sysvinit-scripts: version 2.1 (rev 12)
    • sysvinit: version 2.90
    • talloc: version 2.1.13
    • tar: version 1.30 (rev 2)
    • tcp_wrappers: version 7.6 (rev 2)
    • tdb: version 1.3.15 (rev 2)
    • telnet: version 0.17 (rev 4)
    • tevent: version 0.9.36 (rev 2)
    • traceroute: version 2.1.0 (rev 2)
    • transset: version 1.0.2 (rev 2)
    • tree: version 1.7.0 (rev 2)
    • ttyd: version 1.4.0 (rev2)
    • usbredir: version 0.7.1 (rev2)
    • usbutils: version 010
    • utempter: version 1.1.6 (rev 3)
    • util-linux: version 2.32
    • vala: version 0.28.1 (rev2)
    • vbetool: version 1.2.2 (rev 2)
    • vsftpd: version 3.0.3 (rev 5)
    • vte3: version 0.44.3 (rev2)
    • wget: version 1.19.5 (CVE-2018-0494)
    • which: version 2.21 (rev 2)
    • xauth: version 1.0.10 (rev 2)
    • xcb-util: version 0.4.0 (rev 3)
    • xclock: version 1.0.7 (rev 3)
    • xdpyinfo: version 1.3.2 (rev 2)
    • xdriinfo: version 1.0.6 (rev 2)
    • xev: version 1.2.2 (rev 2)
    • xf86-input-evdev: version 2.10.6
    • xf86-input-keyboard: version 1.9.0 (rev 3)
    • xf86-input-mouse: version 1.9.3
    • xf86-input-synaptics: version 1.9.1
    • xf86-video-ast: version 1.1.5 (rev 5)
    • xf86-video-mga: version 1.6.5 (rev 3)
    • xf86-video-vesa: version 2.4.0 (rev 3)
    • xfsprogs: version 4.16.1
    • xhost: version 1.0.7 (rev 2)
    • xinit: version 1.4.0 (rev 2)
    • xkbcomp: version 1.4.2
    • xkbevd: version 1.1.4 (rev 2)
    • xkbutils: version 1.0.4 (rev 3)
    • xkeyboard-config: version 2.22 (rev 2)
    • xkill: version 1.0.5 (rev 2)
    • xload: version 1.1.3 (rev 2)
    • xlsatoms: version 1.1.2 (rev 2)
    • xlsclients: version 1.1.4 (rev 2)
    • xmessage: version 1.0.5 (rev 2)
    • xmodmap: version 1.0.9 (rev 2)
    • xorg-server: version 1.20.0 (rev 2)
    • xprop: version 1.2.3 (rev 2)
    • xrandr: version 1.5.0 (rev 2)
    • xrdb: version 1.1.1 (rev 2)
    • xrefresh: version 1.0.6 (rev 2)
    • xset: version 1.2.4 (rev 2)
    • xsetroot: version 1.1.2 (rev 2)
    • xsm: version 1.0.4 (rev 2)
    • xterm: version 333
    • xtrans: version 1.3.5 (rev 2)
    • xwd: version 1.0.7 (rev 2)
    • xwininfo: version 1.1.4 (rev 2)
    • xwud: version 1.0.5 (rev 2)
    • xz: version 5.2.4
    • zlib: version 1.2.11 (rev 2)

    Linux kernel:

    • version 4.17.19
    • intel ixgbe: version 5.3.7
    • intel ixgbevf: version 4.3.5
    • highpoint r750: version 1.2.11
    • highpoint rr3740a: version 1.17.0
    • added per customer request:
      • CONFIG_BLK_DEV_SKD: STEC S1120 Block Driver
      • CONFIG_BNXT: Broadcom NetXtreme-C/E support
      • CONFIG_CHR_DEV_ST: SCSI tape support
    • changed from built-in to module:
      • CONFIG_BLK_DEV_SR: SCSI CDROM support
    • removed CONFIG_SENSORS_IT87: ITE IT87xx and compatibles
    • it87: version 20180709 groeck Linux Driver for ITE LPC chips (https://github.com/groeck/it87)
    • set CRYPTO_DEV_SP_PSP=N otherwise udev deadlocks on threadripper

    Management:

    • Docker: add optional per-container wait before starting
    • Enable IPv6 for NTP
    • rc.cpufreq: For CPUs using intel_pstate, always use the performance governor.
      • This also provides power savings on Intel processors while avoiding the ramp-up lag present when using the powersave governor (which is the default if ondemand is requested on these machines).
    • restore docker custom networks upon docker start
    • update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt}
    • webgui: docker: Correct docker container icon name generation
    • webgui: docker: added cpu load and memory load display
    • webgui: docker: added shell/bash selection for console
    • webgui: docker: Make cpu-load and mem-load only visible in advanced mode
    • webgui: Show accumulated encryption status
    • webgui: Prevent openbox from clipping
    • webgui: Plugins: Show support thread if present
    • webgui: Remove control codes, and extended ascii characters from plugin urls on install
    • webgui: Update link for privileged help text
    • webgui: fix regex matching for unraid.net domain name validation when using new openssl1.1
    • webgui: docker: Prevent arbitrary bash execution or redirection on docker create/run commands
    • webgui: Plugins: Preserve support link when updating plugin
    • webgui: diagnostics: Replace consecutive repeated lines in syslog
    • webgui: Remove empty entries when storing individual disk settings
    • webgui: docker: fix connect container console to new window
    • webgui: Use timeout in command execution of diagnostics
    • webgui: Fixed 'Update All Containers' button sometimes hidden in docker list
    • webgui: Added version control in docker API calls
    • webgui: Show docker allocations in column format
    • webgui: fix css help button in themes azure and gray
    • webgui: Added docker autostart wait period
    • webgui: Added CPU selection to docker container edit section
    • webgui: Verify internet access using NCSI method
      • NCSI = network connection status indicator. This method tries to access a specific Microsoft site to test internet access. The same method is used in Windows.
    • webgui: Added docker autostart wait period
    • webgui: New CPU pinning functionality
    • webgui: Change wording on dashboard page "memory total usable"
    • webgui: Include meminfo in diagnostics
    • webgui: Docker containers page: show container starting up message
      • Starting docker service and auto-starting containers has been decoupled. This lets the docker page return as soon as the service is ready. The container overview page shows a new message, and will automatically reload to update the status until all containers are auto-started
    • webgui: VMs: preserve XML custom settings in VM config updates
    • webgui: dockerMan: Avoid filename collisions on FAT32
    • webgui: Extract disk log from multiple rotated logs
    • webgui: theme-match marketing site

     

    Edited by limetech

    • Like 9



    User Feedback

    Recommended Comments



    Hi,

    I hope that this hasn't been already reported I don't think it has but I have only really skim read this post so apologies if this has  already been said.

     

    Excellent work as always. love the new look and new features. I find a small error on the vm template manager.

    I find when changing the graphics type from vnc to a gpu the vnc graphics is left in the xml and the gpu added as a second gpu. Also after having vnc graphics there is no option to add a sound card afterwards.

     

    oh and not a bug but thought i would mention it. Would be great in vm manager to have an option to select all vm cores at once then remove the ones not wanted. Would be great for people with high core count and multi cpu servers :)

     

     

    Link to comment
    1 hour ago, gridrunner said:

    Hi,

    I hope that this hasn't been already reported I don't think it has but I have only really skim read this post so apologies if this has  already been said.

     

    Excellent work as always. love the new look and new features. I find a small error on the vm template manager.

    I find when changing the graphics type from vnc to a gpu the vnc graphics is left in the xml and the gpu added as a second gpu. Also after having vnc graphics there is no option to add a sound card afterwards.

     

    oh and not a bug but thought i would mention it. Would be great in vm manager to have an option to select all vm cores at once then remove the ones not wanted. Would be great for people with high core count and multi cpu servers :)

     

     

    Hello Spaceinvader1 big shout out from Canada, love your unraid Tutorials, 64 threads is insane, what CPU/CPUs are you using for that beast?
     

    Link to comment
    5 minutes ago, Can0nfan said:

    Hello Spaceinvader1 big shout out from Canada, love your unraid Tutorials, 64 threads is insane, what CPU/CPUs are you using for that beast?
     

    Hi @Can0nfan. Thank you, glad you like the videos :) 

    I have just put in the new threadripper 2990wx cpu into my server. tbh not quite sure what I will need all those cores for but hey its sure nice having them there! 

    • Upvote 1
    Link to comment

    Hi @gridrunner

     

    First of all big thanks for all your great Unraid tutorials. Helped me a lot to configure my system. I myself use a first gen 1950x so far without any big issues, but what i noticed and earlier reported in this thread, after an upgrade from 6.5.3 to the 6.6.0-rc1 i can't edit any existing VM in the form view without getting an error. Creating one works fine, but not the editing later. Did you upgraded from an earlier version or did you tried a fresh install?

     

    If i remember correctly you had an 1950x before, right? If you still have that chip can you check the following thread and maybe can post your core pairings how it looks on your system.

     

    https://forums.unraid.net/topic/73509-ryzenthreadripper-psa-core-numberings-andassignments/?do=findComment&comment=678031

    Link to comment

    Well... I enabled (and subsequently disabled) ACS override.

     

    I rebooted after disabling and BOOM, flash drive wiped clean!! :(

     

    I'm baffled, guess all I can do is re-image the USB with 6.6 and grab the disk backup off my array and hope for the best?! Never actually tested a fresh USB on my existing unRAID :S

     

    image.thumb.png.cb050ca1de040d2ab535bd6968123663.png

    Link to comment
    1 hour ago, nexusmaniac said:

    Well... I enabled (and subsequently disabled) ACS override.

     

    I rebooted after disabling and BOOM, flash drive wiped clean!! :(

     

    I'm baffled, guess all I can do is re-image the USB with 6.6 and grab the disk backup off my array and hope for the best?! Never actually tested a fresh USB on my existing unRAID :S

     

    image.thumb.png.cb050ca1de040d2ab535bd6968123663.png

     

    See here for the next chapter in this sordid tale:

     

    https://forums.unraid.net/topic/73908-its-all-broken-d/

     

    It is very unclear (unlikely?) whether this user's problems have anything at all to do with this release.

    Link to comment
    On 9/2/2018 at 5:01 PM, Ordspilleren said:

    AFAIK, the solution here is to not use the physical network interface directly. Simply create a macvlan interface for the host to use, just like with the dockers. This enables communication between host and containers. Might be something to consider.

    I've been meaning to try this... gotta find time while I'm around as recovery can be really ugly if doing it remotely without IPMI or similar features.

    Link to comment

    Updated beautifully, no issues with tweaks in VMs. In fact did a passthrough IOMMU with multifunction flag with no issues.

     

    Ryzen 2700 OC 4.1Ghz with 16GB of DDR4 3000. Multiple dockers and VMs.

    Link to comment
    58 minutes ago, John_M said:

    It's not a good idea to overclock a server.

    Depends on what you use it for. Been overclocking with Unraid for years. Tell me you don't overclock your ram to get timings reported on the sticks... Difference in Watts pull and overclockability of AMD within margins and tight CPU OC makes it a completely safe bet in my case. I run 2 gaming VMs off this with CPU pinning and GPU and USB PCI passthrough. 

    Link to comment
    6 hours ago, phbigred said:

    Depends on what you use it for. Been overclocking with Unraid for years. Tell me you don't overclock your ram to get timings reported on the sticks... Difference in Watts pull and overclockability of AMD within margins and tight CPU OC makes it a completely safe bet in my case. I run 2 gaming VMs off this with CPU pinning and GPU and USB PCI passthrough. 

    Overclocking by definition means running above specified safe limits. Safe being defined as what the manufacturer of the part recommends for a normal lifespan.

     

    Running out of spec may initially work fine, but as parts age, things can change. Overclocking can accelerate that aging process, causing premature failure. Servers are designed to be reliable 24/7/365 for years on end. Overclocking is not a good idea if you wish to retain that reliability for the long term.

    • Like 1
    Link to comment

    Has anyone had issues with enabling the VM manager? I've swapped out my cache drive and pressing "Apply" does nothing when re-enabling the VMs!

    Link to comment
    31 minutes ago, J89eu said:

    Has anyone had issues with enabling the VM manager? I've swapped out my cache drive and pressing "Apply" does nothing when re-enabling the VMs!

    Diagnostics

    Link to comment
    7 hours ago, phbigred said:

    Tell me you don't overclock your ram to get timings reported on the sticks

    I don't overclock my RAM, my memory controller, my cores or anything else. On my 1000-series Ryzen systems I run my RAM at DDR-2666 (i.e. 1333 MHz clock) and on my 2000-series Ryzen systems I run my RAM at DDR-2933 (i.e. 1467 MHz clock) as specified by AMD. There's little to be gained and much to be lost by overclocking the 2700X since XFR2 takes it to the limit of the thermal solution anyway.

    • Like 1
    • Upvote 1
    Link to comment
    35 minutes ago, Squid said:

    Diagnostics

    I'm at work currently so only have access on my phone via VPN but I have sent diagnostics via the troubleshooting process on the GUI

    Link to comment
    14 minutes ago, J89eu said:

    I'm at work currently so only have access on my phone via VPN but I have sent diagnostics via the troubleshooting process on the GUI

    Not sure what you mean by the troubleshooting process on the GUI, but it's possible I have missed some feature. Do you mean the Feedback feature?

     

    In any case, none of the usual helpful volunteers on this forum, including the moderators, will receive the diagnostics you sent. They probably get sent to the limited staff at Limetech to deal with. You would likely get a quicker response posting them here on the forum after you get home.

    Link to comment
    1 hour ago, J89eu said:

    I'm at work currently so only have access on my phone via VPN but I have sent diagnostics via the troubleshooting process on the GUI

    What @trurl stated.  But, the reason why I wanted to see the diagnostics is that there's a likely scenario (couple of them actually), but one of them is quite easy to fix and to catch.  If you have Fix Common Problems installed, then go to Tools - Update Assistant.  It explicitly looks for the most like scenario on the VM page not starting as part of upgrading (depending upon which version of unRaid you upgraded from) - Just make sure that VM's are enabled prior to running the Assistant.

    Link to comment

    That was actually just after trying to, I put Yes to enable VMs and click Apply and the button turns orange and just stays like that, I can post another diagnostic though, just bare with me a moment and I'll update this post

    atlas-diagnostics-20180904-1520.zip

    Edited by J89eu
    Link to comment

    ... I just turned on advanced view and thought I'll try and press apply again... It worked... so in basic view it seems the button doesn't work... I forgot all about the advanced view with being on my phone. Sorry for time wasting but perhaps I've highlighted some sort of bug anway!

    Link to comment
    5 minutes ago, J89eu said:

    so in basic view it seems the button doesn't work.

    Unlikely, in basic view certain fields are made invisible, but function wise nothing changes.

     

    I think you found a bug :)

    Edited by bonienl
    Link to comment

    It's strange as I just changed it back to basic view after disabling it again and had the same issue

    Link to comment
    17 minutes ago, J89eu said:

    It's strange as I just changed it back to basic view after disabling it again and had the same issue

    Not strange, but a bug.

    I made a fix. Thanks

    Link to comment



    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.