• 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



    Really liking the new GUI look, maybe except the very large orange buttons, like already mentioned by others.

     

    I do have one request, but since there was talk of LT taking over the UD plugin soon not sure if I should still bothering @dlandonwith this, there's a lot of extra space between disks on UD compared to the array disks, the mount/unmount buttons could also be smaller.

     

    P.S. I was expecting (read hoping) for a few new features on 6.6, can we expect some during the various rc releases, à la 6.4 or will it be more like 6.5, i.e. mostly bugs and security fixes?

     

    6.6.thumb.png.6832fa24715c66caf73afe918fe41bf2.png

    Link to comment
    4 hours ago, John_M said:

    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.

    2666 and 2933 are overclocks. You have to use XMR or memory timing adjustments to get it. My RAM is rated at 3200 but run it at 2933. We can agree to disagree on the CPU as I don’t adjust voltage from stock and I run water cooling so my at load temps are 60 degrees C. Is it harder on the chip? Yes, do I really care? No as I can drop in another easy enough. It’s not like I paid $300-$400 for the chip. If I get half the life I’m still ahead.

    Link to comment
    29 minutes ago, phbigred said:

    2666 and 2933 are overclocks. You have to use XMR or memory timing adjustments to get it.

    I'm afraid I don't understand what you're saying. How are they overclocks? What is being overclocked? Do you mean XMP? XMP is disabled by default on AM4 motherboards and the fastest JEDEC timing is used: DDR-2133. I enable XMP and then choose either DDR-2666 or 2933, depending on the CPU (and the RAM, of course - I aim to buy DDR4-3000 at the moment but sometimes 3200 happens to be cheaper. I have some DDR4-2666, which I run at 2666. I buy RAM for each project and always choose from the motherboard vendor's QVL). Nothing is overclocked: the memory controller is in spec and the RAM is spec.

    Link to comment
    1 hour ago, John_M said:

    I'm afraid I don't understand what you're saying. How are they overclocks? What is being overclocked? Do you mean XMP? XMP is disabled by default on AM4 motherboards and the fastest JEDEC timing is used: DDR-2133. I enable XMP and then choose either DDR-2666 or 2933, depending on the CPU (and the RAM, of course - I aim to buy DDR4-3000 at the moment but sometimes 3200 happens to be cheaper. I have some DDR4-2666, which I run at 2666. I buy RAM for each project and always choose from the motherboard vendor's QVL). Nothing is overclocked: the memory controller is in spec and the RAM is spec.

    https://www.tomshardware.com/reviews/ram-overclocking-guide,4693.html

    Memory starts at the lowest most common settings for boards. You don’t get the rate out of the box, you have to set it. I can buy a GPU with an overclock too. Base frequency is what I’m referring to. Been an overclocker for years since my Athlon days. Yes its in spec but your point is moot. It registers at a set frequency when you install it. That’s the base setting. Anything above that even within spec is a overclock of sorts.

    Link to comment
    22 hours ago, John_M said:

    I'm afraid I don't understand what you're saying. How are they overclocks? What is being overclocked? Do you mean XMP? XMP is disabled by default on AM4 motherboards and the fastest JEDEC timing is used: DDR-2133. I enable XMP and then choose either DDR-2666 or 2933, depending on the CPU (and the RAM, of course - I aim to buy DDR4-3000 at the moment but sometimes 3200 happens to be cheaper. I have some DDR4-2666, which I run at 2666. I buy RAM for each project and always choose from the motherboard vendor's QVL). Nothing is overclocked: the memory controller is in spec and the RAM is spec.

    [Edited to address John_M's complaint that I was making unfounded assumptions on his setup.  Bolded blue sentences below have been edited to clarify my original helpful intent.  I never mean to insinuate John_M was in fact overclocking, I had no way to know for sure and thought I had said as much later in my post, so that was a lazy choice of wording on my part.]

    They are not suggesting that you're overclocking the memory.  They are suggesting that you're overclocking the built-in memory controller in your Ryzen CPU.  Depending upon your actual memory configuration, you might be overclocking it by quite a bit, or not at all.

     

    For example, on my Ryzen 7 1800X, I'm running my memory at 2400, which sounds low but it is definitely overclocked.  The RAM itself is rated for 2400, so the RAM isn't overclocked.  But my memory, 4x 16GB sticks, is Dual Rank, so I'm presenting the highest possible memory load on the 1800X.

     

    Here's AMD's non-overclocked supported memory speeds for Ryzen 1st generation:

    • 2666 MHz for 2 Single Rank DIMMs in Dual Channel
    • 2400 MHz for 2 Dual Rank DIMMs in Dual Channel
    • 2133 MHz for 4 Single Rank DIMMs in Dual Channel
    • 1866 MHz for 4 Dual Rank DIMMs in Dual Channel

     

    As you can see, the non-overclocked speed for my memory configuration is 1866.  This is a memory controller limitation, not a RAM limitation.  By running them at 2400MHz, I have a 533MHz overclock on the memory controller.

     

    2666 may or may not be an overclock on your system, depending upon the number of sticks of RAM and whether they are Single Rank or Dual Rank.  But odds are that if you have anything other than 2 sticks of 8GB RAM (which are often Single Rank but not always), you are overclocked.

     

    Paul

    Edited by Pauven
    Caused unintentional offense to another user due to poor choice of wording.
    Link to comment
    2 minutes ago, Pauven said:

    I buy RAM for each project and always choose from the motherboard vendor's QVL). Nothing is overclocked: the memory controller is in spec and the RAM is spec.

    Just a quick followup on this (predicting your next rebuttal):  The motherboard vendor's QVL list includes overclocked speeds.  They are simply communicating that they have successfully tested the memory at that speed, and provided the necessary BIOS support to enable it.

     

    But in the eyes of AMD, if it exceeds the limits I listed above, it is overclocked.

     

    Paul

    Link to comment
    3 hours ago, Pauven said:

    You're not overclocking the memory.  You're overclocking the built-in memory controller in your Ryzen CPU. 

    No, I'm not. Why are you making assumptions about my setup based on your own choices? My 1000 series systems use the first configuration you mention

    3 hours ago, Pauven said:

    2666 MHz for 2 Single Rank DIMMs in Dual Channel

    and neither the RAM nor the memory controller is overclocked, as I have said several times. That's a pair of single rank 8 GiB DIMMs. I know all about bus loading when using unbuffered RAM, thank you. I also know there are overclocked speeds included in the QVL - what I don't do is use any of them. I said that I make sure that the RAM I choose is on the QVL, not that I settle for anything that just happens to be listed there.

    3 hours ago, Pauven said:

    But in the eyes of AMD, if it exceeds the limits I listed above, it is overclocked.

    Therefore, in the eyes of AMD I am not overclocking, as I have repeatedly said.

     

    Paul, I don't disagree with what you're saying, in general. But I do resent your assumption that you know more about what I'm doing than I do. I only ever use a maximum of two DIMMs and if I needed more capacity I would use dual rank if necessary and reduce the speed accordingly, but so far I haven't needed to do that.

     

    3 hours ago, phbigred said:

    You don’t get the rate out of the box, you have to set it.

    Isn't that precisely what I said I do?

    5 hours ago, John_M said:

    [by default] JEDEC timing is used: DDR-2133. I enable XMP and then choose either DDR-2666 or DDR-2933

     

    4 hours ago, phbigred said:

    It registers at a set frequency when you install it. That’s the base setting. Anything above that even within spec is a overclock of sorts.

    JEDEC profiles don't go above DDR-2133 so that's the speed it runs at out of the box. Enable XMP and you can run without overclocking anything at the lower of the rated RAM speed and the rated memory controller speed. The latter depends on the generation of the processor and the number of physical chips loading the bus, as Pauven implied. Anything faster is an overclock.

     

    Enough! This is way off topic.

    Link to comment
    17 hours ago, johnnie.black said:

    Really liking the new GUI look, maybe except the very large orange buttons, like already mentioned by others.

     

    I do have one request, but since there was talk of LT taking over the UD plugin soon not sure if I should still bothering @dlandonwith this, there's a lot of extra space between disks on UD compared to the array disks, the mount/unmount buttons could also be smaller.

     

    P.S. I was expecting (read hoping) for a few new features on 6.6, can we expect some during the various rc releases, à la 6.4 or will it be more like 6.5, i.e. mostly bugs and security fixes?

     

    6.6.thumb.png.6832fa24715c66caf73afe918fe41bf2.png

    It really is time for @limetech to incorporate the UD functionality.  I do not have the time nor the interest in updating UD for the new GUI.

    Link to comment

    So the dynamix.plg is definitely an issue.  That has to be removed before the server will boot up properly.  I fixed that manually.

     

     

    Second issue I run into is the code I have in my GO file to autostart my encrypted array (see below) doesn't seem to be working as the array will not autostart (claiming it's missing the encryption key).

    mkdir -p /unlock
    mount -t cifs -o user=USER,password=PASSWORD,iocharset=utf8 //10.0.10.30/flash/temp /unlock
    cp -f /unlock/temp.png /root/keyfile
    umount /unlock
    rm -r /unlock

     

    EDIT:  When I run the commands manually, it tells me "Couldn't chdir to /unlock: No such file or directory" when I try to mount the cifs share.  I can't cd to it but I can see it in Midnight Commander but there is a period after it so it shows as /unlock.

     

    Edited by IamSpartacus
    Link to comment
    44 minutes ago, IamSpartacus said:

    EDIT:  When I run the commands manually, it tells me "Couldn't chdir to /unlock: No such file or directory" when I try to mount the cifs share.  I can't cd to it but I can see it in Midnight Commander but there is a period after it so it shows as /unlock.

    If somehow the /unlock. was created instead of /unlock that would explain behavior.  What do you mean by "cron job code in your GO file"?  Do you mean those lines are in your 'go' file or that you are setting up an actual cron job to execute?

    Link to comment
    1 minute ago, limetech said:

    If somehow the /unlock. was created instead of /unlock that would explain behavior.  What do you mean by "cron job code in your GO file"?  Do you mean those lines are in your 'go' file or that you are setting up an actual cron job to execute?

     

    Ignore the cron part of that statement, that was a typo.  I just have that code in my GO file.  But I'm not understanding why the /unlock directory is all of a sudden not being created correctly.

    Link to comment
    9 minutes ago, IamSpartacus said:

    Ignore the cron part of that statement, that was a typo.  I just have that code in my GO file.  But I'm not understanding why the /unlock directory is all of a sudden not being created correctly.

     

    Ok I'll copy your code into a test server here and see what happens.  btw: I like this idea of yours to fetch keyfile from another machine (presumably) on your LAN.  This is effective theft protection, assuming thief doesn't take all your machines 😉

    Link to comment
    7 minutes ago, limetech said:

     

    Ok I'll copy your code into a test server here and see what happens.  btw: I like this idea of yours to fetch keyfile from another machine (presumably) on your LAN.  This is effective theft protection, assuming thief doesn't take all your machines 😉

     

    Wish I could take credit but this was @bonienl's code.  In my case, the other machine is actually not on my LAN but instead on the other side of a Site-to-Site VPN I have between mine and my parents' home which is where my second (backup) unRAID server lives 😉.

     

     

    Edited by IamSpartacus
    Link to comment
    26 minutes ago, limetech said:

    Hmm, works for me...

     

    Interesting.  I just tried manually deleting the /unlock. directory and then recreating it.  It successfully created it without the period this time.  I just deleted it again and rebooted so lets see what happens.

    Link to comment

    Ok, still no go on the auto start.  Now I get past the mkdir part but the mount of the cifs share fails.  I get the following error:

     

    mount error(115): Operation now in progress
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

     

    Edited by IamSpartacus
    Link to comment

    Ok, the issue was completely on my end.  I forgot I had made some firewall changes a few months back for my VPN connection.  I haven't had to reboot my server since.  So I just had to allow the CIFS ports in my firewall and now I'm up and running.  My sincere apologies @limetech for wasting your time.

    Edited by IamSpartacus
    Link to comment
    On 9/1/2018 at 12:59 PM, Squid said:

    Couple of times I've seen you post this.  Is there a problem that say my Update Assistant should look for?  Since he was coming from 6.5.3, I thought that an old version of dynamix.plg shouldn't attempt to load since it checked for OS versions.  (Only really ancient versions didn't check the OS version)

    My one server on 6.5.3 did not have an issue (was using the Grey theme prior to install and reboot not sure that had anything to do with it)

    Link to comment

    Hi @limetech ,@jonp, and @eschultz

    One thing I have read  few times and now after checking the Webgui on various monitors and a few browsers I agree the font although the perfect modern font is too large when using Chrome Canary its giant and on Chrome itself the happy point is at a zoom value of about 90% Firefox isn't much better things on my console 15" screen causes quite a bit of scrolling.

    maybe if its not too much trouble build in a font size option into settings to appease the masses? maybe even some font choices too. not too sure how hard that would be to implement.

    Link to comment
    3 hours ago, Can0nfan said:

    things on my console 15" screen causes quite a bit of scrolling.

    On a 24" screen (FHD or QHD) the font size is perfect. Do they still make such tiny low res screens?

    Link to comment

    I have a few small issues.

     

    1.) I also ran into the non boot scenario with the dynamix.plg plugin.

     

    2.) My docker containers no longer have the option to launch their web apps directly when clicking  on them. See screenshot below. 

    image.png.cfdb4aee666da9e9497e962731c238d4.png

     

    3.) When adding a new Docker container my previously used templates are missing.

     

    image.thumb.png.edc16962647e5e0febd9b25bf7223865.png

    Link to comment
    On 9/4/2018 at 6:49 PM, johnnie.black said:

    P.S. I was expecting (read hoping) for a few new features on 6.6,

    What new features are you hoping for?

     

    There are several new features/changes in 6.6. A recap:

    - CPU pinning for Docker Containers

    - One consolidated page to view and set CPU pinning for VMs and containers

    - CPU isolation (rc2)

    - Edit VMs in Form (GUI) mode without loosing XML custom settings

    - Docker containers CPU and memory usage real-time monitoring

    - Modernized GUI themes

    - More and upgraded hardware support

    - Kernel and package updates to the latest versions

    - Various bug fixes and improvements

     

    Link to comment
    13 minutes ago, fatalfurry said:

    I have a few small issues.

    Something wrong with your setup, it looks like the Docker environment is broken. Please post your diagnostics (see tools -> diagnostics).

    image.png.76941d3ee8b77cad7f7a7b90ad8261ae.png

     

    image.png.50ebd2f1f7ae0ee07e1e49c72dcf060d.png

    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.