October 4, 20169 yr Download Clicking 'Check for Updates' on the Plugins page is the preferred way to upgrade. Upgrade Notes If you are upgrading from unRAID Server 6.1.x or earlier, please refer to the Version 6.2.0 release post for important upgrade information. Release Notes This is primarily a maintenance release, where several components have been updated to address CVE's. There are also some bug fixes, particularly with Power Down. Known Issues NFS connectivity issues with some media players. I have fired up an old Popcorn Hour C-200 (great media player btw), and do not see any issues using NFS. I have an idea what this might be, please send me an email: [email protected] and I will send an experimental release for you to try. Reported performance issues with some low/mid range hardware. No movement on this yet. Spindown of SAS and other pure-SCSI devices assigned to the parity-protected array does not work (but SATA devices attached to SAS controller does work). No movement on this yet. If a system extended attribute, eg, system.posix_acl_access, is set on a file on the cache, if that file is targeted by the mover for transfer to the array, and the target array disk file system is ReiserFS, there will be an error in the system log and the file will not be moved. This is a kernel issue that will be resolved in a future 6.2 patch release. unRAID 6.3 does not have this issue. This issue normally does not come up but certain docker containers, e.g., sonarr, might create the conditions where this can occur. Refer also to this defect report. unRAID Server OS Change Log =========================== Version 6.2.1 2016-10-04 ------------------------ Base distro: - curl: version 7.50.3 (CVE-2016-7167) - gnutls: version 3.4.15 (CVE-2015-6251) - netatalk: version 3.1.10 - openssl: version 1.0.2j (CVE-2016-7052, CVE-2016-6304, CVE-2016-6305, CVE-2016-2183, CVE-2016-6303, CVE-2016-6302, CVE-2016-2182, CVE-2016-2180, CVE-2016-2177, CVE-2016-2178, CVE-2016-2179, CVE-2016-2181, CVE-2016-6306, CVE-2016-6307, CVE-2016-6308) - php: version 5.6.26 (CVE-2016-7124, CVE-2016-7125, CVE-2016-7126, CVE-2016-7127, CVE-2016-7128, CVE-2016-7129, CVE-2016-7130, CVE-2016-7131, CVE-2016-7132, CVE-2016-7133, CVE-2016-7134, CVE-2016-7416, CVE-2016-7412, CVE-2016-7414, CVE-2016-7417, CVE-2016-7411, CVE-2016-7413, CVE-2016-7418) Linux kernel: - version 4.4.23 (CVE-2016-0758, CVE-2016-6480) - added config options: - CONFIG_SENSORS_I5500: Intel 5500/5520/X58 temperature sensor Management: - bug fix: For file system type "auto", only attempt btrfs,xfs,reiserfs mounts. - bug fix: For docker.img and libvirt.img, if path on /mnt/ check for mountpoint on any subdir component, not just second subdir. - bug fix: During shutdown force continue if array stop taking too long. - bug fix: Handle case in 'mover' where rsync may move a file but also return error status. - md/unraid: Fix bug where case of no data disks improperly detected. - webGui: Add "Shutdown time-out" control on Disk Settings page. Version 6.2 2016-09-15 ---------------------- - stable release version
October 4, 20169 yr Download Clicking 'Check for Updates' on the Plugins page is the preferred way to upgrade. Upgrade Notes If you are upgrading from unRAID Server 6.1.x or earlier, please refer to the Version 6.2.0 release post for important upgrade information. Release Notes This is primarily a maintenance release, where several components have been updated to address CVE's. There are also some bug fixes, particularly with Power Down. Known Issues NFS connectivity issues with some media players. I have fired up an old Popcorn Hour C-200 (great media player btw), and do not see any issues using NFS. I have an idea what this might be, please send me an email: [email protected] and I will send an experimental release for you to try. Reported performance issues with some low/mid range hardware. No movement on this yet. Spindown of SAS and other pure-SCSI devices assigned to the parity-protected array does not work (but SATA devices attached to SAS controller does work). No movement on this yet. unRAID Server OS Change Log =========================== Version 6.2.1 2016-10-04 ------------------------ Base distro: - curl: version 7.50.3 (CVE-2016-7167) - gnutls: version 3.4.15 (CVE-2015-6251) - netatalk: version 3.1.10 - openssl: version 1.0.2j (CVE-2016-7052, CVE-2016-6304, CVE-2016-6305, CVE-2016-2183, CVE-2016-6303, CVE-2016-6302, CVE-2016-2182, CVE-2016-2180, CVE-2016-2177, CVE-2016-2178, CVE-2016-2179, CVE-2016-2181, CVE-2016-6306, CVE-2016-6307, CVE-2016-6308) - php: version 5.6.26 (CVE-2016-7124, CVE-2016-7125, CVE-2016-7126, CVE-2016-7127, CVE-2016-7128, CVE-2016-7129, CVE-2016-7130, CVE-2016-7131, CVE-2016-7132, CVE-2016-7133, CVE-2016-7134, CVE-2016-7416, CVE-2016-7412, CVE-2016-7414, CVE-2016-7417, CVE-2016-7411, CVE-2016-7413, CVE-2016-7418) Linux kernel: - version 4.4.23 (CVE-2016-0758, CVE-2016-6480) - added config options: - CONFIG_SENSORS_I5500: Intel 5500/5520/X58 temperature sensor Management: - bug fix: For file system type "auto", only attempt btrfs,xfs,reiserfs mounts. - bug fix: For docker.img and libvirt.img, if path on /mnt/ check for mountpoint on any subdir component, not just second subdir. - bug fix: During shutdown force continue if array stop taking too long. - bug fix: Handle case in 'mover' where rsync may move a file but also return error status. - md/unraid: Fix bug where case of no data disks improperly detected. - webGui: Add "Shutdown time-out" control on Disk Settings page. Version 6.2 2016-09-15 ---------------------- - stable release version Tom, when can we start working on fixing the NFS User Share Issue on media players?
October 4, 20169 yr Author Tom, when can we start working on fixing the NFS User Share Issue on media players? Did you not see this? I have an idea what this might be, please send me an email: [email protected] and I will send an experimental release for you to try.
October 4, 20169 yr Tom, when can we start working on fixing the NFS User Share Issue on media players? Did you not see this? I have an idea what this might be, please send me an email: [email protected] and I will send an experimental release for you to try. i did not, sorry bout that, sending email now
October 4, 20169 yr Just curious if you have had any luck with the AMD-KVM issue? Not yet. We believe that will be resolved in 6.3 when we update QEMU to 2.7.
October 4, 20169 yr hmm, currently running 6.2.1-2016.09.22 but when I check for updates in the plugin section no updates are found?
October 4, 20169 yr hmm, currently running 6.2.1-2016.09.22 but when I check for updates in the plugin section no updates are found? That's the mainline branch, not the stable branch. Update for the mainline branch is probably not ready yet.
October 4, 20169 yr Author hmm, currently running 6.2.1-2016.09.22 but when I check for updates in the plugin section no updates are found? That's the mainline branch, not the stable branch. Update for the mainline branch is probably not ready yet. Yes that's right. Next mainline release will be 6.3.0-rc1. Your server will update to that when it gets released.
October 4, 20169 yr Just curious if you have had any luck with the AMD-KVM issue? Not yet. We believe that will be resolved in 6.3 when we update QEMU to 2.7. Any idea on timeframe? And is the decision to wait until then based on the fact there were too many changes to pinpoint was caused the problems with 6.2?
October 5, 20169 yr Just curious if you have had any luck with the AMD-KVM issue? Not yet. We believe that will be resolved in 6.3 when we update QEMU to 2.7. Any idea on timeframe? And is the decision to wait until then based on the fact there were too many changes to pinpoint was caused the problems with 6.2? Can't speak for timeframe, but this is a patch release. Stable Releases Stable releases are numbered <major>.<minor>.<patch> as in: 6.2.0 6.2.1 6.2.2 6.3.0 6.3.1 etc. Completion of a new feature or improvement set typically increments the <minor> number. Patch releases are reserved exclusively for CVE's and other critical bug fixes. CVE's and critical bug fixes appear in a mainline release for testing first, and then are back ported to the latest stable. At this time, whenever a new stable release is published, all previous stable releases are deemed EOS (End of Support).
October 5, 20169 yr Updated to 6.2.1 with no issues => in fact, it appears that the shutdown process is now stable in the main code ... I removed the PowerDown plugin and tested it a bit, and it shuts down very nicely.
October 5, 20169 yr Was the command line reboot suggestion by dlandon below added as part of the shut down fixes? http://lime-technology.com/forum/index.php?topic=51983.msg499540#msg499540 Also if you do the powerdown command via cli and it hangs will it still invoke the poweroff command via the webgui timeout?
October 5, 20169 yr Author Was the command line reboot suggestion by dlandon below added as part of the shut down fixes? http://lime-technology.com/forum/index.php?topic=51983.msg499540#msg499540 Also if you do the powerdown command via cli and it hangs will it still invoke the poweroff command via the webgui timeout? Not exactly. The 'powerdown' script is now just a wrapper for backward-compatibility. The work is done in /etc/rc.d/rc.local_shutdown. You can take a look in there to see what it's doing.
October 5, 20169 yr Was the command line reboot suggestion by dlandon below added as part of the shut down fixes? http://lime-technology.com/forum/index.php?topic=51983.msg499540#msg499540 Also if you do the powerdown command via cli and it hangs will it still invoke the poweroff command via the webgui timeout? Not exactly. The 'powerdown' script is now just a wrapper for backward-compatibility. The work is done in /etc/rc.d/rc.local_shutdown. You can take a look in there to see what it's doing. The cli and other options for shutting down/rebooting, etc are: - reboot - poweroff - Ctrl-Alt-Del - Quick push of the power button - UPS power failure These commands are deprecated, but still there for compatibility for the time being: - powerdown - powerdown -r If you use either /sbin/powerdown or /usr/local/sbin/powerdown in any scripts, you need to change them to the newer methods: - Change 'powerdown' to '/sbin/poweroff' - Change 'powerdown -r' to '/sbin/reboot'
October 5, 20169 yr That's going to really take sone getting used to powerdown -r is commited to my muscle memory.... Sent from my LG-H815 using Tapatalk
October 5, 20169 yr That's going to really take sone getting used to powerdown -r is commited to my muscle memory.... Sent from my LG-H815 using Tapatalk I understand. We are creatures of habit. The way LT has implemented the shutdown is more consistent with standard Linux commands.
October 5, 20169 yr ... If you use either /sbin/powerdown or /usr/local/sbin/powerdown in any scripts, you need to change them to the newer methods: - Change 'powerdown' to '/sbin/poweroff' - Change 'powerdown -r' to '/sbin/reboot' Does this mean the command for PLink (executed from a Windows box) should be changed from "powerdown" to "poweroff" ?? This is what I use now: S:\Downloads\Putty\Plink.exe -ssh -pw <password> root@<servername> powerdown
October 5, 20169 yr I upgraded after clean install, I had no shares or whatever and now when I add a share doesn't show up in the web interface. However the folder is exists and works. I can view them at dashboard shares list but not on the shares tab.
October 5, 20169 yr I upgraded after clean install, I had no shares or whatever and now when I add a share doesn't show up in the web interface. However the folder is exists and works. I can view them at dashboard shares list but not on the shares tab. The symptoms are consistent with an adblocker blocking the unRAID GUI. If you run an adblocker in your browser then you need to whitelist the unRAID server.
October 5, 20169 yr I upgraded after clean install, I had no shares or whatever and now when I add a share doesn't show up in the web interface. However the folder is exists and works. I can view them at dashboard shares list but not on the shares tab. The symptoms are consistent with an adblocker blocking the unRAID GUI. If you run an adblocker in your browser then you need to whitelist the unRAID server. I feel stupid, you are right, thanks
Archived
This topic is now archived and is closed to further replies.