June 4, 20179 yr Important: If you want to report an issue, please start a new topic in this board. The main purpose of the 6.4 release is to improve some components that will be necessary for upcoming major features in 6.5. Hopefully the 6.4.0-rc series will be short. Note: please use plugin install method of upgrading a server to the next branch as described in this post. If you install by extracting from the release zip file, note there are now 4 "bz" files to copy. Here are some highlights of this release: Improved shfs/mover The LimeTech user share file system (shfs) has been improved in two areas. First, we now make use of FUSE read_buf/write_buf methods. This should result in significant throughput increases. Second, the mover script/move program no longer uses rsync to move files/directories between the cache pool and the parity array. Instead the move program invokes a new shfs ioctl() call. This should result in complete preservation of all metadata including atime and mtime. While this function has been fairly extensively tested, please keep an eye on mover activities - there shouldn't be any data loss, but it's a fairly significant code change. Also note: the /mnt/user0 mount point is no longer needed and has been removed. nginx http server We now use the nginx webserver as the front-end to the unRAID OS Management Utility (aka, webGui). The emhttp process has been changed to a daemon (emhttpd) listening at a unix socket. Incorporating nginx provides several features: Multi-threaded access, though emhttpd is still single-threaded. https (SSL) support. At present unRAID OS will generate a self-signed certificate. https works but you will get a scary warning from your browser about not being able to verify the certificate. No worries. nchan (websocket) support. We have only just begun the process of converting many of the browser javascript polling functions to an event-driven websocket paradigm. This opens the door for us to create something like a process manager where we can have several background operations in process, all monitored in real-time via webGui dashboard. linux 4.11 kernel - should provide better Ryzen support among other improvements. IPv6 support We want to again, give a big "thank you" to bonienl who has greatly improved unRAID OS networking with the addition of IPv6 support. Give it a try and report any issues. Other Two new webGUI themes: Azure and Gray. Again, thanks to bonienl. Expanded driver support (QLogic) and more hardware monitoring support. Many more misc. improvements Change log: Base distro: acpid: version 2.0.28 adwaita-icon-theme: version 3.24.0 apcupsd: version 3.14.14 (rev2, added modbus-usb support) at-spi2-atk: version 2.24.0 at-spi2-core: version 2.24.0 atk: version 2.24.0 btrfs-progs: version 4.10.2 cairo: version 1.14.8 coreutils: version 8.27 cryptsetup: version 1.7.5 curl: version 7.54.0 (CVE-2017-7468, CVE-2017-2629) dbus: version 1.10.16 dejavu-fonts-ttf: version 2.37 dhcpcd: version 6.11.5 docker: version 17.05.0-ce dosfstools: version 4.1 e2fsprogs: version 1.43.4 etc: version 14.2 (rev10) ethtool: version 4.10 eudev: version 3.2.2 file: version 5.30 flex: version 2.6.4 fontconfig: version 2.12.1 freetype: version 2.7.1 gd: version 2.2.4 gdbm: version 1.13 gdk-pixbuf2: version 2.36.6 glibc: version 2.25 glibc-zoneinfo: version 2017b glib2: version 2.52.1 gnome-themes-standard: version 3.22.3 gnutls: version 3.5.10 (CVE-2017-5334, CVE-2017-5335, CVE-2017-5336, CVE-2017-5337) gptfdisk: version 1.0.1 grep: version 3.0 gtk+3: version 3.22.12 harfbuzz: version 1.4.6 hdparm: version 9.51 htop: version 2.0.2 iproute2: version 4.10.0 iptables: version 1.6.1 irqbalance: version 1.2.0 jemalloc: version 4.5.0 kernel-firmware: 20170330 keyutils: version 1.5.10 kmod: version 24 libarchive: version 3.3.1 libcroco: version 0.6.12 libdrm: version 2.4.80 libedit: version 20160903_3.1 libepoxy: version 1.4.2 libevdev: version 1.5.6 libevent: version 2.1.8 libgcrypt: version 1.7.5 libgudev: version 231 libjpeg-turbo: version 1.5.1 liblogging: version 1.0.6 libnetfilter_conntrack: version 1.0.6 libnftnl: version 1.0.7 libnl3: version 3.2.29 libpcap: version 1.8.1 libpciaccess: version 0.13.5 libpng: version 1.6.29 (CVE-2016-10087) libpthread-stubs: version 0.4 librsvg: version 2.40.17 libseccomp: version 2.3.2 libssh2: version 1.8.0 libtasn1: version 4.10 libusb-compat: version 0.1.5 libvirt: version 3.2.0 libX11: version 1.6.5 libXfont2: version 2.0.1 libXi: version 1.7.9 libXpm: version 3.5.12 lvm2: version 2.02.170 lz4: version 1.7.5 mc: version 4.8.19 mesa: version 17.0.5 mozilla-firefox: version 53.0.2 (CVE-2017-5031, CVE-2017-5433, CVE-2017-5435, CVE-2017-5436, CVE-2017-5461, CVE-2017-5459, CVE-2017-5466, CVE-2017-5434, CVE-2017-5432, CVE-2017-5460, CVE-2017-5438, CVE-2017-5439, CVE-2017-5440, CVE-2017-5441, CVE-2017-5442, CVE-2017-5464, CVE-2017-5443, CVE-2017-5444, CVE-2017-5446, CVE-2017-5447, CVE-2017-5465, CVE-2017-5448, CVE-2016-10196, CVE-2017-5454, CVE-2017-5455, CVE-2017-5456, CVE-2017-5469, CVE-2017-5445, CVE-2017-5449, CVE-2017-5450, CVE-2017-5451, CVE-2017-5462, CVE-2017-5463, CVE-2017-5467, CVE-2017-5452, CVE-2017-5453, CVE-2017-5458, CVE-2017-5468, CVE-2017-5430, CVE-2017-5429) nano: version 2.8.2 ncurses: version 6.0 netatalk: version 3.1.11 nettle: version 3.3 nfs-utils: version 2.1.1 nginx: version 1.12.0 ntfs-3g: version 2017.3.23 ntp: version 4.2.8p10 (CVE-2017-6464, CVE-2017-6463, CVE-2017-6458, CVE-2017-6460, CVE-2016-9042, CVE-2017-6462, CVE-2017-6451, CVE-2017-6455, CVE-2017-6452, CVE-2017-6459) openssh: version 7.5p1 (CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012) openssl: version 1.0.2k (CVE-2017-3731, CVE-2017-3732, CVE-2016-7055) pango: version 1.40.5 pciutils: version 3.5.4 php: version 7.1.4 procps-ng: version 3.3.12 qemu: version 2.9.0 (CVE-2017-2615, CVE-2017-2630) rsyslog: version 8.26.0 samba: version 4.6.4 (CVE-2017-7494, CVE-2017-2619) + patch for Time Machine fullsync support sed: version 4.4 sessreg: version 1.1.1 shadow: version 4.2.1 (rev2) (CVE-2017-2616) shared-mime-info: version 1.7 sqlite: version 3.16.2 sudo: version 1.8.19p2 util-linux: version 2.29.2 (CVE-2017-2616) wget: version 1.19.1 xauth: version 1.0.10 xf86-input-evdev: version 2.10.5 xf86-input-keyboard: version 1.9.0 xf86-input-mouse: version 1.9.2 xf86-input-synaptics: version 1.9.0 xf86-video-mga: version 1.6.5 xfsprogs: version 4.10.0 xorg-server: version 1.19.3 xterm: version 327 xz: version 5.2.3 zlib: version 1.2.11 Linux kernel: version 4.11.3 added IPv6 support added QLogic Ethernet support: CONFIG_BNA: QLogic BR-series 1010/1020/1860 10Gb Ethernet Driver support CONFIG_QLA3XXX: QLogic QLA3XXX Network Driver Support CONFIG_QLCNIC: QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support CONFIG_QLGE: QLogic QLGE 10Gb Ethernet Driver Support CONFIG_NETXEN_NIC: NetXen Multi port (1/10) Gigabit Ethernet NIC added squashfs to support mounting /boot/bzmodules, /boot/bzfirmware additional config options: CONFIG_BLK_DEV_PCIESSD_MTIP32XX: Block Device Driver for Micron PCIe SSDs CONFIG_BNXT: Broadcom NetXtreme-C/E support CONFIG_CMA: Contiguous Memory Allocator CONFIG_MTD: Memory Technology Device support CONFIG_NUMA_BALANCING: Memory placement aware NUMA scheduler CONFIG_NUMA_BALANCING_DEFAULT_ENABLED: Automatically enable NUMA aware memory/task placement expanded set of included hwmonitor modules md/unraid version: 2.8.0 accommodate kernel 4.11 api changes bug fix: if one disabled disk and another invalid disk, should not be able to unassign third disk modules now compressed with XZ Management: create ntp and avahi users if missing replace cpuload daemon with websocket endpoint firmware now loaded on-demand from 'bzfirmware' file located on USB boot device force correcting-fsck on USB boot flash before mounting integrate nginx http-server including php-fpm and nchan support modules now loaded on-demand from 'bzmodules' file located on USB boot device support https with auto-generated self-signed certificates update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} emhttp: detect "unraidsafemode" boot and prevent array autostart if set emhttp: eliminate "/mnt/user0" shfs mount point. emhttp: fix 'btrfs check' running status not detected correctly emhttp: if valid old key on same usb flash device as Trial key, offer to replace key emhttp: invoke emhttpd daemon listening on local unix socket shfs: Full atim/mtim preservation. shfs: implement ioctl() functions to move objects shfs: utilize FUSE read_buf/write_buf methods mover: use shfs ioctl() instead of 'rsync' webGui: added new themes 'Azure' and 'Gray' webGui: allow custom IP addresses for individual Docker containers webGui: changed screen width to automatic with minimum of 1080 webGui: networking now allows multi bonds and multi bridge groups webGui: new watchdog service with websockets instead of ajax polling webGui: utilize pubsub/cpuload nchan websocket endpoint to update cpu load info webGui: IPv6 networking and routing table management webGui: correct case of cache device assignment not being preserved across array restart webGui: Upgrade tooltipster to version 4.2.3 webGui: Fixed file read errors when system is started but array is stopped webGui: Fixed persisting the show banner value after applying disk settings webGui: Fixed regression error in erroneous display of disk table on Dashboard webGui: Registration page refinements
June 4, 20179 yr Installed with no issues. There are some changes in CA that are unlocked when running 6.4. See the CA thread for details
June 4, 20179 yr 19 minutes ago, limetech said: First, we now make use of FUSE read_buf/write_buf methods. This should result in significant throughput increases. Thanks for this change. This has increased my write speed to the SSD cache (from an unassigned SSD) from ~140 MB/s to ~230 MB/s ( 20 GB file going through a Windows VM) This is all using my very (very) crappy hardware. Edited June 4, 20179 yr by Squid
June 4, 20179 yr Some heads up information The new themes GRAY and AZURE work scrollbarless. Scrolling can be done using the mouse-wheel, or double-finger motion on touchpad or swiping using a touch screen Chrome, Safari and Edge support scrollbar suppression using CSS coding. Firefox, however needs to install an addon, called "hidescrollbars" Dockers can now be assigned to custom networks, using macvlan technology. Every interface at docker service start up with an assigned IP address (can be both IPv4 or IPv6) will be automatically included in the list of custom networks and made available to each container. This allows containers to run on different networks or different IP addresses. The latter one can be useful when multiple containers use the same host port and you don't want to do port translation Containers linked to a custom network can have either a fixed or dynamic address assignment. The Docker IPAM functionality which hands out dynamic addresses is not aware of any DHCP server however, to avoid address conflicts with dynamic assignments, the user can assign an address pool for each available custom network. See Settings -- Docker, stop the Docker service first the make the address pool assignment(s) Network function allows the use of IPv4 only, IPv6 only (not recommended) or both. An additiional "Routing Table" tab on the network settings shows all known subnets and allows to add or remove subnets too (use with care, aka know what you are doing) Multiple bond interfaces may be created. bond0 is reserved for the communication of unRAID itself, but subsequent bond interfaces can be assigned as needed (there is no limitation in the number of physical interfaces - though it has been tested with up to six interfaces only)
June 4, 20179 yr 2 minutes ago, bonienl said: The new themes GRAY and AZURE work scrollbarless. Scrolling can be done using the mouse-wheel, or double-finger motion on touchpad or swiping using a touch screen How about keyboard? Does up/down arrow work? Believe it or not, some of the systems I interact with do NOT have mouse-wheel or touch.
June 4, 20179 yr Just now, jonathanm said: How about keyboard? Does up/down arrow work? Believe it or not, some of the systems I interact with do NOT have mouse-wheel or touch. Yes, keyboard arrow keys work too (sorry forgot to mention that)
June 4, 20179 yr Can somebody throw up a few screen shots of the new interface or is it pretty close to the old interface?
June 4, 20179 yr 1 minute ago, kizer said: Can somebody throw up a few screen shots of the new interface or is it pretty close to the old interface? White / Black Themes are identical - just fills the window appropriately Azure / Gray screenshots can be found here Edited June 4, 20179 yr by Squid
June 4, 20179 yr Thanks I knew Azure was different. Just didn't know if what we are used to with 6+ is the same. I'm going to guess it is with a few whatever is buried under the hood changes.
June 4, 20179 yr Thanks for this change. This has increased my write speed to the SSD cache (from an unassigned SSD) from ~140 MB/s to ~230 MB/s ( 20 GB file going through a Windows VM) This is all using my very (very) crappy hardware.Does this also increase write speeds for non cache drive servers?Sent from my iPhone using Tapatalk
June 4, 20179 yr Author 1 minute ago, pras1011 said: Does this also increase write speeds for non cache drive servers? Probably not noticeably to a parity-protected data disk because writes in that case will be throttled by read/modify/write to storage.
June 4, 20179 yr Write speeds are the only problem with unraid. But I still love unraid better than raid!Sent from my iPhone using Tapatalk
June 4, 20179 yr Just now, pras1011 said: Does this also increase write speeds for non cache drive servers? Sent from my iPhone using Tapatalk 1 minute ago, limetech said: Probably not noticeably to a parity-protected data disk because writes in that case will be throttled by read/modify/write to storage. Pretty much exactly what I've found.
June 5, 20179 yr Excellent, I shall let you be Guinea pigs and upgrade at the weekend. Hopefully my date change issue is solved!!
June 5, 20179 yr So...Disk Speed. 6.3.4 gave 847MB/s on my Samsung NVMe cache drive. 6.4.0rc2 gives the expected 2400MB/s. Nice.
June 5, 20179 yr 21 hours ago, limetech said: First, we now make use of FUSE read_buf/write_buf methods. This should result in significant throughput increases. So exciting for above change, when I upgrade to a powerful CPU / System recently, I got serious disk array throughput issue that ceiling ~700MB/s R/W, it will worse if increase in data disks. May I know what level can be reach after FUSE read_buf/write_buf methods ? Preious post said parity protect array won't enjoy this. Edited June 5, 20179 yr by Benson
June 5, 20179 yr Author Hey I forgot to mention something about this Prerelease board. The reason we give a prerelease its own forum board is so that different issues can be posted as separate topics. That was the big problem with posting beta/rc topics on the Announcements board: all the various issues are tangled together in one massive topic. So I am going to lock this thread now and start moving some posts around. Ok, done now.
June 5, 20179 yr Updated from 6.3.3 -> 6.4.0-rc2 without any issues. Nice WebUI update. Everything is running smoothly. Good work team :-)
June 5, 20179 yr Looking forward to update this weekend. Lots of improvements!!! Excellent work, thank you!
June 6, 20179 yr On 6/4/2017 at 0:36 PM, limetech said: This opens the door for us to create something like a process manager where we can have several background operations in process, all monitored in real-time via webGui dashboard. I'm excited if this means we can get a client server model where the unRaid server collects data and publishes it via an API, and any client can then use it. The webGui can then be a separate process on the server, or elsewhere, or a client app etc.
June 6, 20179 yr 15 hours ago, Benson said: So exciting for above change, when I upgrade to a powerful CPU / System recently, I got serious disk array throughput issue that ceiling ~700MB/s R/W, it will worse if increase in data disks. May I know what level can be reach after FUSE read_buf/write_buf methods ? Preious post said parity protect array won't enjoy this. They enjoy it if you use "disk settings-> Tunable (md_write_method): reconstructive write". This avoids the read/modify/write bottleneck and gives me full speed writing to the array. Read/modify/write will spin-up the parity disks and the disk being written to, whereas reconstructive write will spin up all array disks while writing. You can control the spin-up/recontructive write behavior using the turbo write plugin. On my system reconstuctive write is about 3 times faster than read/modify/write (50mb/s vs. 150mb/s).
June 6, 20179 yr 1 hour ago, Videodr0me said: They enjoy it if you use "disk settings-> Tunable (md_write_method): reconstructive write". This avoids the read/modify/write bottleneck and gives me full speed writing to the array. Read/modify/write will spin-up the parity disks and the disk being written to, whereas reconstructive write will spin up all array disks while writing. You can control the spin-up/recontructive write behavior using the turbo write plugin. On my system reconstuctive write is about 3 times faster than read/modify/write (50mb/s vs. 150mb/s). There are bottleneck on R/W, the disk array will ceiling at ~700MB/s, those can't overcome by reconstructive write mode. Anyway, today just try 6.4rc2. The 1st image show still have bottleneck, a parity protected array will max at 733MB, 4 data disks already reach the max, last disk got ~4.5MB/s). With this limitation, the array write speed will also affect, it worse if more more data disks. The 2nd image just show all disk / system could run in their max speed. ( 1.6GB/s + 224MB/s, parity check+cache disk read) Edited June 6, 20179 yr by Benson
June 6, 20179 yr 51 minutes ago, Benson said: There are bottleneck on R/W, the disk array will ceiling at ~700MB/s Never came across such bottleneck, but not quite sure I follow what's happening when you're hitting it, can you better explain what you're doing on the 1st screenshot?
Archived
This topic is now archived and is closed to further replies.