November 18, 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. Notable changes (-rc13): Correct handling of SMART ID 190. Replaced 'tabs' for 'spaces' in the make_bootable.bat file (Windows doesn't like tabs). Notable changes (-rc12a): None, just bug fixes, well updated linux kernel minor patch release Notable changes (-rc11i): Let's Encrypt SSL certificate renewal: if your certificate is within 30 days of expiration the Renew button on Settings/Identification/SSLCertificate Settings page will be enabled. LE certs have a lifetime of 90 days but it's free to renew. We are working on a configurable daemon to make this automatic. All encryption passphrase/keyfile handling is managed on the Main page. For now the Encryption Settings page is gone but will eventually return as a way of changing the default cipher settings. Also gone is the Restricted Start setting introduced in the last release (bad idea). Yet another attempt to reliably report NVMe temperatures. 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 split-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_rc13 2017-11-18 Changes Management: Replaced 'tabs' for 'spaces' in the make_bootable.bat file (Windows does not like tabs) Correct handling of SMART ID 190 webgui: Add SMART temperature reading for SAS devices webgui: SystemInformation page: Use MB as calculation unit + code enhancement Version 6.4.0_rc12a 2017-11-17 Changes Linux kernel: version 4.13.13 (with kvm_svm_obey_guest_pat.patch: https://patchwork.kernel.org/patch/10027525/) nginx: Revert "redirect https requests to the domain name in unraid cert" Management: emhttp: if both SMART ID 190 (Airflow_Temperature_Cel) and 194 (Temperature_Celsius) present, prefer 194 webgui: Fix regression error in SMART acknowledgement on dashboard board webgui: Bring Encryption status on Dashboard page inline with Main page
November 18, 20178 yr 19 minutes ago, pras1011 said: Is it safe to use the 6.4 software now? Yes it is safe.
November 18, 20178 yr Update: The following issue below has been resolved and not related to unRAID. On 11/18/2017 at 10:39 AM, limetech said: Correct handling of SMART ID 190 Not sure if 190 is the same issue as reported here, will test and report! UPDATE: Nope, still present. Must not be for this issue. Edited November 19, 20178 yr by Lev updated with resolution.
November 18, 20178 yr Anyone else using EFI having an issue with this update? The flash drive went unrecognizable in the system. I can read it on my computer.
November 18, 20178 yr 17 minutes ago, bcjenkins said: Anyone else using EFI having an issue with this update? The flash drive went unrecognizable in the system. I can read it on my computer. I am using EFI and have no problem with the update.
November 18, 20178 yr 10 minutes ago, bonienl said: I am using EFI and have no problem with the update. I remade the drive in the utility and all is well.
November 18, 20178 yr Thanks for the update on a weekend, temperatures are showing correctly now!Sent from my SM-G955U using Tapatalk
November 19, 20178 yr I realize you don't need 10,000 confirmations, but since I was so active on the other thread I wanted to close the loop and say that my temps are back to normal now. Thanks!Sent from my ONEPLUS A3000 using Tapatalk
November 19, 20178 yr Author 33 minutes ago, ljm42 said: I realize you don't need 10,000 confirmations, but since I was so active on the other thread I wanted to close the loop and say that my temps are back to normal now. Thanks! Sent from my ONEPLUS A3000 using Tapatalk Thanks. We appreciate all feedback!
November 19, 20178 yr I just upgraded to rc13 and when I booted up and started my array the webgui died on me. Nothing is showing up on the console and I have restarted twice and still have no webgui. Not sure what to try next.
November 19, 20178 yr This morning my SSD started screaming... I had no idea what was going on. I took a huge air duct and piped it straight into the server room (closet) from my window. It is damn 41F in there now, cold as hell. It was still screaming saying it was 61C and I thought something was wrong on my end because I didn't get an update notification. Then I came here and read there is a new page.. so updated and the SSD is now at 33C. On a good note, I hit REBOOT and it actually rebooted. Full blown reboot. First time since week 2 of me being on UnRaid. So I got that going for me, which is nice.
November 19, 20178 yr This might be a plugin issue but I get this blank update notification when updating all plugins via the update all plugins button. To be fair this issue has been around for a while not just this RC.
November 19, 20178 yr 2 hours ago, Lebowski said: This might be a plugin issue but I get this blank update notification when updating all plugins via the update all plugins button. To be fair this issue has been around for a while not just this RC. AFAIK this is related to a plugin, but honestly I can't remember which one.
November 19, 20178 yr 5 hours ago, greg2895 said: I just upgraded to rc13 and when I booted up and started my array the webgui died on me. Nothing is showing up on the console and I have restarted twice and still have no webgui. Not sure what to try next. Take your USB stick out and check it in a Windows machine for any corruption.
November 19, 20178 yr If I upgrade from stable to this version can I upgrade to stable when is released?
November 19, 20178 yr 5 minutes ago, etsi said: If I upgrade from stable to this version can I upgrade to stable when is released? Yes, you can. Under Tools -> Update OS you'll need to select the stable branch instead of next.
November 19, 20178 yr This is the regular crash I experienced on rc9f approximately once or twice a week, at seemingly random times. I use a Ryzen 1700 CPU, so this is with the append rcu_nocbs=0-11 initrd=/bzroot in the syslinux file as per this thread: Last night I updated to rc13, forgot to put in that line in the syslinux file (which is now in a syslinux folder for some reason?) and woke up to this crash: I have now inserted "rcu_nocbs=0-15" into bot the syslinux.cfg and the syslinux.cfg~ files. I was used to there only being one of them, at the root of the flash. I wonder what the next crash will look like. Any help much appreciated. And I hope this can help development somehow. Diagnostics attached: hal9000-diagnostics-20171119-1609.zip Edited November 19, 20178 yr by JohanSF Corrected rcu_nocbs=0-11 to rcu_nocbs=0-15, just a wrong copy-paste, my file is correct.
November 19, 20178 yr 6 minutes ago, JohanSF said: Any help much appreciated. Changes to the syslinux file can be done via the GUI, no need to edit multiple files manually. Post a screenshot of Main -> Flash device -> Syslinux configuration
November 19, 20178 yr 2 minutes ago, bonienl said: Changes to the syslinux file can be done via the GUI, no need to edit multiple files manually. Post a screenshot of Main -> Flash device -> Syslinux configuration I had no idea you could do that! Here are the contents: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append rcu_nocbs=0-15 initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest Is this enough or is a screenshot of that whole screen needed? Edited November 19, 20178 yr by JohanSF
November 19, 20178 yr 12 minutes ago, JohanSF said: Is this enough or is a screenshot of that whole screen needed? No, this is enough and append statement is correct. I presume your system was rebooted after the statement was added.
November 19, 20178 yr 17 minutes ago, bonienl said: No, this is enough and append statement is correct. I presume your system was rebooted after the statement was added. Yes. I will post a new pic of the screen next time it crashes. I also think I should mention that after rebooting and before I start the array, the syslog is flooded with this line: [Date and name of server] root: error: /plugins/advanced.buttons/AdvancedButtons.php: wrong csrf_token But this stops when the array is started. Right now I'm just ignoring it, because I like this plugin. Edited November 19, 20178 yr by JohanSF
November 19, 20178 yr 1 hour ago, JohanSF said: also think I should mention that after rebooting and before I start the array, the syslog is flooded with this line: [Date and name of server] root: error: /plugins/advanced.buttons/AdvancedButtons.php: wrong csrf_token That normally means you have a browser window open somewhere from before the last reboot. However since you say it stops when you start the array I am not sure this is the case here.
Archived
This topic is now archived and is closed to further replies.