October 28, 20178 yr Upgrading: We have changed the way one checks for new unRAID OS releases. Please refer to Update OS below. Bugs: If you want to report an issue, please start a new topic in this board. This is a bug-fix/improvement release. Notable changes (-rc10b): Finally looks like the AMD Ryzen GPU pass-through performance issue has been solved. We applied this patch and it does indeed appear to solve the problem. Fixed issue in the 'mover' where it wasn't handling slit-levels correctly in moving files from cache to array. Further refinements in handling encryption keyfile. Added new config setting Settings/Disk Settings/Restricted Start [Yes/No]. When set to Yes, array will not Start if there are encrypted volumes and the encryption key is missing (this is the default). If set to No and encryption key is missing, array will Start but encrypted volumes will not be Mounted and also cannot be Formatted - any share data stored therein simply won't be available. After attempted array Start with missing/wrong keyfile, you can enter the passphrase/upload keyfile directly from Main page. If there are any encrypted volumes in your server, we recommend setting "Settings/Disk Settings/Enable auto start" to Yes. Following boot of course there will be no keyfile present so autostart will fail. But in this case s/w also now knows there are encrypted devices and you will see right on the Main page a place to enter the encryption passphrase or upload a keyfile. Numerous package updates, bug fixes and webGui enhancements. Notable changes (-rc9f): Improved handling of encryption passphrase/keyfile. When Starting array with encrypted volumes, you only need to enter the encryption passphrase once on the Encryption Settings page - no more confusing "passphrase confirmation". If no encrypted devices exist and you're trying to add some, then it will ask for passphrase confirmation. Introduce new Disk Setting called 'Restricted Start - Yes/No'. When set to 'Yes' then array will not Start if the encryption key is missing. If set to 'No' then array will Start (including autostart) but encrypted volumes will not be 'mounted', meaning shares and/or share data stored on them will not be accessible. The default (and normal) setting for this is 'Yes'. The Let's Encrypt SSL provisioning is only available when 'Use SSL/TLS' on Identification page is set to 'Auto'. Also, provisioning the cert no longer triggers complete restart of "services". If using 'https' all 'http' is redirected to 'https'. If not using 'https', all 'https' is redirected to 'http'. The result of this is you can always enter servername in browser address bar to get to webGui, for example "Tower/" or "Tower.local" should always get you to the webGui. In the case of SSL-enabled LE certificate, you will get redirected to the <hash>.unraid.net URL. Added an 'Update DNS' button on Identification page. If the IP address of your server changes and you're usng the LE certificate, you can click this button to tell unraid.net to update the DNS setting. We have set TTL to 60 seconds so it might take this long to see the update. Of course you have to already have the webGui open to do this. Finally fixed reporting of temperature for NVMe devices (hopefully). Updated OVMF firmware, tested with various OS types, seems to work. Other misc. fixes an improvements, refer to Changes below. We're at the end of life for linux kernel 4.12. Next release will move to 4.13 kernel. Secure Access (-rc8q): Probably some explanation is in order. The “major” feature we wanted to add into unRAID version 6.4 was block level device encryption. However to get there we realized there needs to exist a secure way of entering information such as passphrases. Hence phase 1 consisted of integrating nginx in order to leverage its support of SSL/TLS (https). Besides the benefit of https support, integration of nginx also lets us utilize websocket technology (which is an ongoing integration), and lets us greatly improve the overall responsiveness of the webGui. Phase 1 integration of nginx in unRAID only supports self-signed SSL certificates. While in general, this may be OK to provide encrypted connections between a browser and a server in a trusted LAN, relying on self-signed certs is not good practice and is theoretically vulnerable to MITM attacks. With this release we have completed Phase 2 of nginx https integration by providing the ability for our users to provision a free SSL Certficate from Let’s Encrypt. To obtain your certificate go to Settings/Identification, scroll to the bottom and click Provision. In one operation this will allocate your certificate, upload it to your server, and switch nginx to redirect all http to https. After clicking anywhere else in the webGui you should see a nice green lock icon in your browser address bar! The other thing you’ll notice in your address bar is a very funny looking URL consisting of a 40-hex-character subdomain of unraid.net. We have set up a LimeTech DNS server that will resolve that URL to your servers IP address on your local network. That FQDN is unique to your certificate. When your browser resolves that URL it is given your local IP address which it then uses to perform the https connection handshake. For this reason, we recommend that you give your server a static IP address because if the IP address changes, the browser will not be able to connect to your server. This is like locking your keys in the car! We plan on implementing a small daemon which wakes up upon such IP address change and tells the LimeTech DNS server to update its A-record, but this has not been done yet. NOTE: if you do lock your keys in the car, the coat-hanger fix to restore http access is to telnet/ssh into the server and type: rm /boot/config/ssl/certs/certificate_bundle.pem /etc/rc.d/rc.nginx reload (You might also have to clear your browser cache.) Following re-enable of http, you can again Provision a certificate which will update the DNS entry. Device block level encryption (-rc8q): We have implemented full-device encryption as follows. In unRAID, encryption is selected as another type of file system. For example, with array Stopped, click on a Device link and then click on File system type. Three new “types” are available: xfs – encrypted btrfs – encrypted reiserfs – encrypted [should we get rid of this one?] If you change the File system type to one of these and then Start the array you will notice the device appears Unmountable and the Format button is available. Formatting the device will result in creating an encrypted partition on that device with the specified file system type. ALL PREVIOUS DATA ON THAT DEVICE WILL BE DESTROYED. Hence it is not possible, in this release, to encrypt in-place. We plan to add a utility in a future release to accomplish this however. The other thing you’ll notice when you click Format is that it may fail because there is no encryption key. In this case, click on Settings/Encryption Settings and enter in a passphrase to be used to secure your encrypted devices. At present we let you enter either a passphrase or upload a file which contains your passphrase (or binary data). DO NOT FORGET YOUR PASSPHRASE OR LOSE YOUR KEYFILE. Once a partition is encrypted, if you forget your passphrase or lose your keyfile, your data is forever lost - unless you know someone very high up in the NSA Also note that array Autostart following server boot will not succeed if any devices are encrypted. This is because the keyfile (passphrase) is kept in RAM and thus lost upon reboot. This means that following system reboot you must log into the webGui, go to Tools/Encryption and enter your passphrase (or upload your keyfile). Yes this is a nuisance and we have a few ideas for automating this, but at least you now have secure https access! In the case of a btrfs cache pool, all devices comprising the pool will be encrypted. For this release, we highly recommend using encryption only on a test server with test data which has been backed up. We plan on many more refinements in future releases. 4Kn Device Support (-rc8q): Yeah should work now. Other notes (-rc8q): The /usr/local/sbin/emhttp line in your /boot/config/go file is no longer used to specify the ports where the webGui listens for connections. Instead you must configure these on the Identification page. Alternately if you need to set this up prior to server boot, you may add the port settings in /boot/config/ident.cfg. Please refer to /usr/local/sbin/emhttp script for more information if you care about this. It used to be that merely Starting the array would re-write a “unRAID standard partition layout”. This surprises some users because one would expect nothing to be written to a new device unless Format was invoked. This has been changed so that nothing is written to a device unless Format is invoked (except for Parity devices – those will still be written upon array Start if parity sync is indicated). Moving devices around between cache pool and array or unassigned is handled much better now. There are numerous webGui fixes and improvements. Upgraded linux kernel and several base packages. Where are releases -rc8a-rc8p you might ask? Those were non-public test releases. Credits (-rc8q): Thanks to @jonp for his work in securing us a Certifiate Authority (Let's Encrypt). Thanks to @eschultz for an incredible amount of work involved in setting up DNS servers and integrating with Let's Encrypt API, among other vital tasks in this release. Thanks to @bonienl for his continued dynamix amazing refinements and networking/IPv6 expertise. USB Flash boot device backup function (-rc7) Added "Flash backup" button on the flash device info page (Main/flash). Click this button to download a zip file with the entire contents of your USB Flash boot device. This zip file may be used to restore to a new unRAID USB Flash boot device either manually, or using our nifty new unRAID USB Creator tool. Linux 4.12 kernel (-rc7) - should provide better Ryzen support among other improvements. UEFI support (-rc5) It is now possible configure UEFI boot mode to boot unRAID OS. The make_bootable.bat (Windows), make_bootable_mac (MacOS) and make_bootable_linux (Linux) scripts will output a prompt: Permit UEFI boot mode [Y/N]: If answered with 'Y' a new directory is included on the USB flash boot device called 'EFI'. The presence of this directory along with its contents, and along with some additional linux kernel options permit UEFI boot. This is done in such a way that you could choose either BIOS (legacy) or UEFI to boot off your USB flash device (that is, even if you answer 'Y' here you can still configure your motherboard to use Legacy boot). If answered with 'N' the directory and contents are still created, but named 'EFI-' (a dash at the end). This will prevent UEFI firmware from considering this device. You can manually rename the 'EFI-' directory to 'EFI' and permit possible UEFI boot (and rename back to 'EFI-' to prevent it again). Note: Even if the 'EFI' directory exists, whether or not your motherboard actually uses UEFI to boot is determined by BIOS settings. In addition, some motherboards may present a strongly worded warning along the lines of "The system found unauthorized changes on the firmware, operating system or UEFI drivers." In this case look for a "Secure Boot" BIOS setting and change to "Other OS" or "Disable". If you update your server using Check for updates on the Plugin page, an 'EFI-' directory and files will be automatically created on your USB flash boot device. If you prepare a new USB flash using this release, the 'EFI-' directory and files will also be included. If you use the "manual" method of updating by copying the bz* files from the release zip, beware you will need to manually also copy over the 'EFI-' directory (and modify the first line of syslinux.cfg and copy it to 'EFI-/boot' directory). There is also a webGui setting to permit UEFI boot located on the 'flash' device information page in the 'Syslinux Configuration' section. Update OS (-rc5) Instead of bundling an "unRAID Server" plugin on the Plugins page, there is a new page on the Tools menu in the About section called 'Update OS'. Here you can check for a new unRAID OS release as well as switch between the latest release in the stable branch or the next branch. In addition there is a separate control on the Notification Settings page that configures whether or not to automatically check for updates. enabling https (-rc3) To enable https support it's necessary to edit your 'config/go' file on your USB flash boot device. Use the -p option to specify the port(s) and optionally include the -r option to redirect http request from your browser to using https. Here's the detailed usage: # Usage: # emhttp [-r] [-p port [,sslport]] [OPER] # OPER is start or stop. Default is start. # By default nginx will be setup to listen only at port 80 (http). # The -p option may be used to define different listening ports and/or setup nginx # to listen at a specified port for https. The -r option may be used to setup # nginx so that any http request is redirected to https (this requires that both # ports have been specified with -p option). For example, to have nginx listen # at both standard ports but redirect all http to https use: # emhttp -rp 80,443 # To listen at only port 443 use: # emhttp -p ,443 # Note: the stop operation is only "safe" if the array has already been stopped # (this will be fixed). Improved shfs/mover (-rc1) 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. nginx http server (-rc1) 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. IPv6 support (-rc1) 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 (-rc1) Two new webGUI themes: Azure and Gray. Again, thanks to bonienl. Expanded driver support (QLogic) and more hardware monitoring support. Kernel modules and firmware are left on the Flash in a squashfs loopback and loaded into RAM on demand. Many more misc. improvements Version 6.4.0_rc10b 2017-10-27 Changes Base distro: adwaita-icon-theme: version 3.26.0 at-spi2-atk: version 2.26.0 at-spi2-core: version 2.26.0 atk: version 2.26.0 btrfs-progs: version v4.13.2 cifs-utils: version 6.7 coreutils: version 8.28 (CVE-2017-7476) curl: version 7.56.0 (CVE-2017-1000254) dbus: version 1.10.24 dnsmasq: version 2.78 (CVE-2017-13704, CVE-2017-14491, CVE-2017-14492, CVE-2017-14493, CVE-2017-14494, CVE-2017-14495, CVE-2017-14496) docker: version 17.09.0-ce eudev: version 3.2.4 file: version 5.32 firefox: version 56.0.1 (CVE-2017-7793, CVE-2017-7817, CVE-2017-7818, CVE-2017-7819, CVE-2017-7824, CVE-2017-7805, CVE-2017-7812, CVE-2017-7814, CVE-2017-7813, CVE-2017-7825, CVE-2017-7815, CVE-2017-7816, CVE-2017-7821, CVE-2017-7823, CVE-2017-7822, CVE-2017-7820, CVE-2017-7811, CVE-2017-7810) fontconfig: version 2.12.6 gd: version 2.2.5 (CVE-2017-6362, CVE-2017-7890) gdk-pixbuf2: version 2.36.11 glib2: version 2.54.1 (rev2) glibc-solibs: version 2.26 (rev3) glibc: version 2.26 (rev3) gtk+3: version 3.22.24 harfbuzz: version 1.5.1 hicolor-icon-theme: version 0.17 iproute2: version 4.13.0 kmod: version 24 (rev2) libcap-ng: version 0.7.8 (rev2) libgudev: version 232 libidn2: version 2.0.4 libnl3: version 3.4.0 libpng: version 1.6.34 librsvg: version 2.40.19 libvirt-php: version 0.5.4 libvirt: version 3.8.0 libxml2: version 2.9.6 libxslt: version 1.1.31 lvm2: version 2.02.175 mesa: version 17.2.2 mpfr: version 3.1.6 nginx: version 1.12.2 ntp: version 4.2.8p10 (rev2) openssh: version 7.6p1 p11-kit: version 0.23.9 pango: version 1.40.12 php: version 7.1.10 qemu: version 2.10.1 (CVE-2017-13672, CVE-2017-13673, CVE-2017-14167) reiserfsprogs: version 3.6.27 samba: version 4.6.8 (CVE-2017-12150, CVE-2017-12151, CVE-2017-12163) disable asynchronous read I/O in /etc/samba/smb.conf sudo: version 1.8.21p2 util-linux: version 2.30.2 xfsprogs: version 4.13.1 xorg-server: version 1.19.4 (CVE-2017-13721, CVE-2017-13723) Linux kernel: version 4.13.10 (with kvm_svm_obey_guest_pat.patch: https://patchwork.kernel.org/patch/10027525/) additional modules: CONFIG_MEDIA_SUPPORT: Multimedia support, ease media builds for CHBMB CONFIG_EDAC: EDAC (Error Detection And Correction) reporting CONFIG_EDAC_AMD64: AMD64 (Opteron, Athlon64) EDAC CONFIG_EDAC_I7CORE: Intel i7 Core (Nehalem) processors EDAC CONFIG_EDAC_SBRIDGE: Intel Sandy-Bridge/Ivy-Bridge/Haswell Integrated MC EDAC CONFIG_EDAC_SKX: Intel Skylake server Integrated MC EDAC md/unraid version: 2.9.1 Management: update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} console-gui: rc.nginx: add port|portssl|use_ssl subcommands use rc.nginx to obtain configured http port emhttp: corrections handling encrypted device status with array Stopped emhttp: correctly handle SAS devices that include spaces in serial number strings emhttp: accept "auto" as file system type for initial cache pool mover: fix incorrect selection of target disk network: fix incorrect metric assignment for VLANs network: fix missing static gateway assignment for VLANs webgui: add extra warning to Format confirmation checkbox webgui: add in device identifier and unRaid assignment to SMART filename webgui: add unRAID icon to vm manager webgui: addition of Error Correction Type information webgui: display dynamically rendered back to top icon webgui: encryption benchmark: highlight default settings webgui: fix Docker exec from replacing + with a space webgui: fix smart controller type arguments webgui: fix VLAN icon alignment for all themes webgui: improved formatting of iommu groups webgui: make System Devices page more responsive webgui: normalize NVMe attributes list webgui: prevent cron error entering syslog webgui: round disk sizes to the nearest unit webgui: show parity and mover schedules unconditionally, but give warning when missing items webgui: show shares when array is online and has formatting disks webgui: support tooltipster CSS on bottom / left / right webgui: take both parity disks in consideration on scheduler page webgui: use user selected number notation in footer messages webgui: change footer: "Array Formatting" to "Array Started • Formatting device(s)" webgui: do not log actual csrf token values when missing or wrong webgui: encryption refinements: allow setting on Main webgui: fix version sorting in plugins list webgui: improve SMART Attributes display for NVMe and certain SAS devices webgui: make Parity Check and Mover Settings unconditional webgui: updated tablesorter to version 2.29.0 webgui: enable device info page link for disabled non-present devices webgui: fix bug where single cpu 0 line was skipped in display of CPU Thread Pairings on System Devices page. webgui: Improved selection of DHCP ranges for macvlan networks
October 28, 20178 yr One request, since you're now using btrfs-progs 4.13 could you turn on reiserfs support for btrfs-convert? This could be useful for some users wanting to convert from reiserfs. 31 minutes ago, limetech said: webgui: normalize NVMe attributes list webgui: improve SMART Attributes display for NVMe and certain SAS devices Was hopping this finally fixed my NVMe temp display, but not yet
October 28, 20178 yr 17 minutes ago, johnnie.black said: Was hopping this finally fixed my NVMe temp display, but not yet What exact smartctl command is required to read temps from your NVMe device?
October 28, 20178 yr Author 24 minutes ago, johnnie.black said: turn on reiserfs support for btrfs-convert How do I do that?
October 28, 20178 yr 11 minutes ago, limetech said: How do I do that? During the build, though I don't know exactly what that means , from the wiki, including the typo : btrfs-convert is used to convert existing source filesystem image to a btrfs filesystem in-place. The original filesystem image is accessible in subvolume named like ext2_saved as file image. Supported filesystems: ext2, ext3, ext4 — original feature, always built in reiserfs — since version 4.13, opptinally built, requires libreiserfscore 3.6.27
October 28, 20178 yr 22 minutes ago, bonienl said: What exact smartctl command is required to read temps from your NVMe device? As discussed in the rc9 thread it only responds to nvme0 not to nvme0n1: The Intel NVMe are also the same: Some devices like the Samsung respond to both: But IIRC nobody posted that it only responds to nvme0n1, so nvme0 should work for all NVMe devices.
October 28, 20178 yr Updated. thanks for pushing this out so quick. I'm sure a lot of AMD users wanted to test this.
October 28, 20178 yr Author 6 minutes ago, johnnie.black said: As discussed in the rc9 thread it only responds to nvme0 not to nvme0n1 Do you suppose that all devices which respond to nvme0n1 will also respond to nvme0?
October 28, 20178 yr 1 minute ago, bonienl said: "nvme0" is used to read the attributes, not sure what is going wrong. Are you sure? On the GUI for SMART attributes it shows "NVMe Status 0x4002", that's the output when you use nvme0n1 instead of nvme0: smartctl -A /dev/nvme0n1 smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.13.10-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF SMART DATA SECTION === Read NVMe SMART/Health Information failed: NVMe Status 0x4002
October 28, 20178 yr 1 minute ago, limetech said: Do you suppose that all devices which respond to nvme0n1 will also respond to nvme0? IIRC nobody posted that it only responds to nvme0n1, some only work with nvme0, others work with both.
October 28, 20178 yr 25 minutes ago, johnnie.black said: Are you sure? On the GUI for SMART attributes it shows "NVMe Status 0x4002", that's the output when you use nvme0n1 instead of nvme0 Right, that's a bug in attributes reading. Need to correct that. Thanks I don't have a NVMe device in my unRAID servers, can you tell me if this works (read status of device)? hdparm -C /dev/nvme0 For completeness can you also show the disks array, see Tools -> Vars -> [disks] Edited October 28, 20178 yr by bonienl
October 28, 20178 yr Fixed. Ty for release, all went smooth for me. Edited October 28, 20178 yr by marshy919
October 28, 20178 yr 37 minutes ago, bonienl said: I don't have a NVMe device in my unRAID servers, can you tell me if this works (read status of device)? root@Tower1:~# hdparm -C /dev/nvme0 /dev/nvme0: drive state is: unknown For this It's the same if I use nvme0n1 38 minutes ago, bonienl said: For completeness can you also show the disks array, see Tools -> Vars -> [disks] [disks] => Array ( [parity] => Array ( [idx] => 0 [name] => parity [device] => sdd [id] => TOSHIBA_HDWD130_37F65K8AS [size] => 2930266532 [status] => DISK_OK [rotational] => 1 [luksState] => 0 [format] => GPT: 4K-aligned [temp] => * [numReads] => 282003 [numWrites] => 116 [numErrors] => 0 [type] => Parity [color] => green-blink [exportable] => no [fsType] => auto [fsStatus] => - [fsColor] => grey-off [spindownDelay] => -1 [spinupGroup] => [deviceSb] => [idSb] => TOSHIBA_HDWD130_37F65K8AS [sizeSb] => 2930266532 ) [disk1] => Array ( [idx] => 1 [name] => disk1 [device] => sde [id] => TOSHIBA_HDWD130_27F16UDAS [size] => 2930266532 [status] => DISK_OK [rotational] => 1 [luksState] => 0 [format] => GPT: 4K-aligned [temp] => * [numReads] => 231329 [numWrites] => 115 [numErrors] => 0 [type] => Data [color] => green-blink [exportable] => yes [fsType] => btrfs [fsStatus] => Mounted [fsColor] => green-on [comment] => [fsSize] => 2929538112 [fsFree] => 46350348 [spindownDelay] => -1 [spinupGroup] => [deviceSb] => md1 [idSb] => TOSHIBA_HDWD130_27F16UDAS [sizeSb] => 2930266532 ) [disk2] => Array ( [idx] => 2 [name] => disk2 [device] => sdf [id] => TOSHIBA_HDWD130_37F65K5AS [size] => 2930266532 [status] => DISK_OK [rotational] => 1 [luksState] => 0 [format] => GPT: 4K-aligned [temp] => * [numReads] => 324958 [numWrites] => 0 [numErrors] => 0 [type] => Data [color] => green-blink [exportable] => yes [fsType] => btrfs [fsStatus] => Mounted [fsColor] => green-on [comment] => [fsSize] => 2928454752 [fsFree] => 54722888 [spindownDelay] => -1 [spinupGroup] => [deviceSb] => md2 [idSb] => TOSHIBA_HDWD130_37F65K5AS [sizeSb] => 2930266532 ) [disk3] => Array ( [idx] => 3 [name] => disk3 [device] => sdg [id] => TOSHIBA_HDWD130_37F6M2TAS [size] => 2930266532 [status] => DISK_OK [rotational] => 1 [luksState] => 0 [format] => GPT: 4K-aligned [temp] => * [numReads] => 324522 [numWrites] => 0 [numErrors] => 0 [type] => Data [color] => green-blink [exportable] => yes [fsType] => btrfs [fsStatus] => Mounted [fsColor] => green-on [comment] => [fsSize] => 2928477472 [fsFree] => 46494404 [spindownDelay] => -1 [spinupGroup] => [deviceSb] => md3 [idSb] => TOSHIBA_HDWD130_37F6M2TAS [sizeSb] => 2930266532 ) [disk4] => Array ( [idx] => 4 [name] => disk4 [device] => sdh [id] => TOSHIBA_HDWD130_37F6M86AS [size] => 2930266532 [status] => DISK_OK [rotational] => 1 [luksState] => 0 [format] => GPT: 4K-aligned [temp] => * [numReads] => 259489 [numWrites] => 0 [numErrors] => 0 [type] => Data [color] => green-blink [exportable] => yes [fsType] => btrfs [fsStatus] => Mounted [fsColor] => green-on [comment] => [fsSize] => 2928568192 [fsFree] => 50390648 [spindownDelay] => -1 [spinupGroup] => [deviceSb] => md4 [idSb] => TOSHIBA_HDWD130_37F6M86AS [sizeSb] => 2930266532 ) [disk5] => Array ( [idx] => 5 [name] => disk5 [device] => sdb [id] => TOSHIBA_HDWD130_37G510KAS [size] => 2930266532 [status] => DISK_OK [rotational] => 1 [luksState] => 0 [format] => GPT: 4K-aligned [temp] => * [numReads] => 305387 [numWrites] => 0 [numErrors] => 0 [type] => Data [color] => green-blink [exportable] => yes [fsType] => btrfs [fsStatus] => Mounted [fsColor] => green-on [comment] => [fsSize] => 2927752384 [fsFree] => 186576788 [spindownDelay] => -1 [spinupGroup] => [deviceSb] => md5 [idSb] => TOSHIBA_HDWD130_37G510KAS [sizeSb] => 2930266532 ) [disk6] => Array ( [idx] => 6 [name] => disk6 [device] => sdc [id] => TOSHIBA_HDWD130_37G6RHMAS [size] => 2930266532 [status] => DISK_OK [rotational] => 1 [luksState] => 0 [format] => GPT: 4K-aligned [temp] => * [numReads] => 315468 [numWrites] => 0 [numErrors] => 0 [type] => Data [color] => green-blink [exportable] => yes [fsType] => btrfs [fsStatus] => Mounted [fsColor] => green-on [comment] => [fsSize] => 2927470880 [fsFree] => 278476340 [spindownDelay] => -1 [spinupGroup] => [deviceSb] => md6 [idSb] => TOSHIBA_HDWD130_37G6RHMAS [sizeSb] => 2930266532 ) [parity2] => Array ( [idx] => 29 [name] => parity2 [device] => [id] => [size] => 0 [status] => DISK_NP_DSBL [rotational] => [luksState] => 0 [format] => - [temp] => * [numReads] => 0 [numWrites] => 0 [numErrors] => 0 [type] => Parity [color] => grey-off [exportable] => no [fsType] => auto [fsStatus] => - [fsColor] => grey-off [spindownDelay] => -1 [spinupGroup] => [deviceSb] => [idSb] => [sizeSb] => 0 ) [cache] => Array ( [idx] => 30 [name] => cache [device] => nvme0n1 [id] => TOSHIBA-RD400_664S107XTPGV [size] => 500107576 [status] => DISK_OK [rotational] => 0 [luksState] => 0 [format] => MBR: 4K-aligned [temp] => * [numReads] => 2127767 [numWrites] => 368766 [numErrors] => 0 [type] => Cache [color] => green-on [exportable] => yes [fsType] => btrfs [fsStatus] => Mounted [fsColor] => yellow-on [comment] => [fsSize] => 499292096 [fsFree] => 166044464 [spindownDelay] => -1 [spinupGroup] => nvme0 [deviceSb] => nvme0n1p1 [idSb] => TOSHIBA-RD400_664S107XTPGV [sizeSb] => 500107576 [uuid] => cea535d2-33f9-4cf2-9ff0-0b51826d48a1 ) [flash] => Array ( [idx] => 54 [name] => flash [device] => sda [id] => DataTraveler_2.0 [size] => 7569376 [status] => DISK_OK [rotational] => 0 [luksState] => 0 [format] => unknown [temp] => * [numReads] => 145 [numWrites] => 403 [numErrors] => 0 [type] => Flash [color] => green-on [exportable] => yes [fsType] => vfat [fsStatus] => Mounted [fsColor] => yellow-on [comment] => unRAID Server OS boot device [fsSize] => 7557136 [fsFree] => 7088528 ) )
October 28, 20178 yr 6 minutes ago, bonienl said: What happens when you quit your browser and restart it? Yeah tried another PC and it worked. Reset chrome fixed the issue for me on this PC. I'm still not "secure" though. I'm unable to provision, renew or update (all blanked out buttons) Certificate issuer: O=Self-signed, OU=unRAID, CN=Tower Certificate expiration: Sep 2 08:30:57 2027 GMT
October 28, 20178 yr Author 3 minutes ago, marshy919 said: I'm unable to provision, renew or update (all blanked out buttons) Is Use SSL/TLS set to "Auto"?
October 28, 20178 yr NVME as an unassigned still wont show correctly. The plugin however works fine. Edited October 28, 20178 yr by Lebowski
October 28, 20178 yr 10 minutes ago, Lebowski said: NVME as an unassigned still wont show correctly. This is expected, the Dashboard status doesn't include temperature reading for unassigned devices. I'll make an update to include this.
October 28, 20178 yr 26 minutes ago, Lebowski said: it's also showing as offline? It is shown as offline because its status reading is "unknown".
October 28, 20178 yr 1 hour ago, limetech said: Is Use SSL/TLS set to "Auto"? Originally was on Auto and not giving HTTPS secure info. Changing to Yes, resetting chrome and then back to Auto fixed the issue. I'm "secure" now. Thanks
October 28, 20178 yr Just upgraded from rc9f no new issues, running unsecured and no encrypted drives. Webpage feels snappier overall when transitioning between pages. Also running a win 10 VM with AMD GPU passed through that booted no issues all on an Ryzen 1700 on an Asus Crosshair 6. One minor thing that I did notice and has been ongoing for awhile is when on the dashboard and left clicking the running apps to view the respective webgui it will always take you to the ip of the device compared to the dns name. Not sure if this can be a setting to disable the IP from being used and stick with the dns name or not if some people prefer to use the IP of the server?
October 28, 20178 yr Containers may have their own IP address, which is not resolvable. Accessing containers by IP address ensures they are always accessable.
October 28, 20178 yr I just upgraded to rc10b and while in general it seems ok, I have two issues: 1. After downloading/installing the upgrade via web menu and rebooting via Dynamix System Button, unRAID came up with "unclean shutdown" and wanting to do a parity check. 2. The GUI for entering the passphrase has reverted to the one before rc9, forcing you to enter the passphrase two times for unlocking. Is this intention or a regression? I prefer the rc9 variant.
Archived
This topic is now archived and is closed to further replies.