eschultz

Version 6.3.0-rc5 Release Notes

Recommended Posts

unRAID OS version 6.3 is primarily a bug fix and package "catch up" release.  There is one interesting new feature:

 

Please refer to change log below for list of updated components.

 

unRAID Server OS Change Log
===========================

Version 6.3.0-rc5 2016-11-25
----------------------------

Base distro:

- bash: version 4.4.005
- grep: version 2.26 (rev2)
- kernel-firmware: version 20161118git
- libvirt: version 2.4.0
- mozilla-firefox: version 50.0
- ntp: version 4.2.8p9 (CVE-2016-9311, CVE-2016-9310, CVE-2016-7427, CVE-2016-7428, CVE-2016-9312, CVE-2016-7431, CVE-2016-7434, CVE-2016-7429, CVE-2016-7426, CVE-2016-7433)

Linux kernel:

- version 4.8.10 (CVE-2016-7039)

Management:

- add btrfs_check script to facilitate btrfs file system check
- bug fix: firefox correctly connects to emhttp port number
- samba: include OS X vfs_fruit optimizations by default
- shutdown: bug fix: overall shutdown timeout read from wrong cfg file
- shutdown: bug fix: saving shutdown timeout value
- shutdown: add config setting for overall VM shutdown timeout
- update: hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} smartmontools/drivedb.h
- webGui: add filesystem Check for btrfs volumes in Maintenance mode
- webGui: add vm shutdown time-out option
- webGui: generate VM xml with cpu topology as single-threaded when host cpu is AMD
- webGui: special text aside new disks to clear
- webGui: split out Europe/Istanbul as its own timezone

Other:

- make_bootable_linux: use readlink instead of realpath since it is more compatible

Version 6.3.0-rc4 2016-11-11
----------------------------

Base distro:

- curl: version 7.51.0 (CVE-2016-8615, CVE-2016-8616, CVE-2016-8617, CVE-2016-8618, CVE-2016-8619, CVE-2016-8620, CVE-2016-8621, CVE-2016-8622, CVE-2016-8623, CVE-2016-8624, CVE-2016-86$
- docker: version 1.12.3 (CVE-2016-8867)
- glibc-zoneinfo: version 2016i
- grep: version 2.26
- kernel-firmware: version 20161001git
- libusb: version 1.0.21
- libX11: version 1.6.4 (CVE-2016-7942, CVE-2016-7943)
- libXfixes: version 5.0.3 (CVE-2016-7944)
- libXi: version 1.7.8 (CVE-2016-7945, CVE-2016-7946)
- libXrandr: version 1.5.1 (CVE-2016-7947, CVE-2016-7948)
- libXrender: version 0.9.10 (CVE-2016-7949, CVE-2016-7950)
- libXtst: version 1.2.3 (CVE-2016-7951, CVE-2016-7952)
- libXv: version 1.0.11 (CVE-2016-5407)
- lvm2: version 2.02.166
- mozilla-firefox: version 49.0.2
- mpfr: version 3.1.5
- nano: version 2.7.1
- php: version 7.0.13
- samba: version 4.5.1

Linux kernel:

- version 4.8.7 (CVE-2016-7042, CVE-2016-8630, CVE-2016-8633)
- md/unraid version: 2.7.1
  - make the 'check' command "correct"/"nocorrect" argument case insensitive
  - mark superblock 'clean' upon initialization

Management:

- emhttp: add API command cmdStopMover and API status variable shareMoverActive (yes/no)
- emhttp: ensure disk shares have proper permissions set even if not being exported
- emhttp: fix detecton of unclean shutdown to trigger automatic parity check upon Start if necessary
- emhttp: fix mac address not set in avahi afp share advertisement (regression introduced in -rc2)
- emhttp: unmount docker/libvirt loopback if docker/libvirt fail to start properly
- mover: add start/stop/status subcommands (experimental)
- mover: dereference files on user shares to get st_dev/st_ino instead of from shfs stat structure
- shfs: eliminate 'use_ino' option dependency (fixes NFS issue on buggy clients)
- update: hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} smartmontools/drivedb.h
- webGui: combine PCI Devices and IOMMU Groups on Sysdev page; Sort IOMMU and USB Devices properly
- webGui: correct button positions on confirmation dialogs
- webGui: correct handling of unclean shutdown detection
- webGui: fixed device passthrough for Docker
- webGui: fixed Docker/VMs tab stay visible when array is stopped
- webGui: fixed some help text typos
- webGui: update to font-awesome 4.7.0

Version 6.3.0-rc3 2016-10-22
----------------------------

Linux kernel:

- version 4.8.4 (CVE-2016-5195)

Management:

- shutdown: additional logging in event of cmdStop timeout

Version 6.3.0-rc2 2016-10-19
----------------------------

Base distro:

- docker: version 1.12.2
- containerd: version 0.2.4
- runc: version 1.0.0_rc2
- libseccomp: version 2.3.1
- libvirt-php: 0.5.2 (+ latest from git)
- php: version 7.0.12
- usbredir: version 0.7.1
- spice: version 0.12.8
- spice-protocol: version 0.12.12
- imlib2: version 1.4.9
- gd: version 2.2.3
- rsyslog: version 8.22.0
- libfastjson: version 0.99.4
- reverted OVMF firmware back to the version in 6.2 due to user reported issues

Linux kernel:

- version 4.8.2
- r750: version 1.2.10-16_10_13

Management:

- bug fix: Samba listening on the wrong interface in a VLAN-enable config
- emhttp: added starting/stopping docker/libvirt events
- emhttp: removed 'reboot', 'shutdown', 'changeNetwork' API calls; eliminated emhttp-managed network vars
- md/unraid: kernel 4.8 API changes; support FUA and SYNC write operation flags
- shutdown: save diagnostics in event of cmdStop timeout
- vm manager: add 'virtio-win-0.1.126-2' and 'virtio-win-0.1.126-1' to VirtIO-ISOs list
- webGui: Added "Join" notification agent
- webGui: Add support for "Notify My Android" notifications
- webGui: Fixed: Windows unable to extract diagnostics zip file
- webGui: Increased password length to 128 characters
- webGui: Interactive Reboot and Shutdown directly invokes '/sbin/reboot' and '/sbin/poweroff'

Version 6.3.0-rc1 2016-10-05
----------------------------

Base distro (primary packages):

- btrfs-progs: version v4.7.2
- netatalk: version 3.1.10
- openssl: version 1.0.2j
- php: version 5.6.26
- qemu: version 2.7.0
- samba: version 4.5.0

Base distro (secondary packages):

- apcupsd: version 3.14.14
- bash: version 4.4.0
- curl: version 7.50.3
- diffutils: version 3.5
- e2fsprogs: version 1.43.3
- etc: version 14.2
- file: version 5.28
- fuse: version 2.9.7
- gawk: version 4.1.4
- gdbm: version 1.12
- glib2: version 2.46.2
- glibc: version 2.24
- glibc: version zoneinfo
- glibc-solibs: version 2.24
- gnutls: version 3.4.15
- jemalloc: version 4.2.1
- kmod: version 23
- libtasn1: version 4.9
- libxml2: version 2.9.4
- lvm2: version 2.02.161
- nano: version 2.7.0
- network-scripts: version 14.2
- nfs-utils: version 1.3.4
- openssl-solibs version: 1.0.2j
- pkgtools-14.2-noarch: version 13
- reiserfsprogs: version 3.6.25
- util-linux: version 2.28.2

Base distro (desktop GUI packages):

- freetype: version 2.6.5
- harfbuzz: version 1.3.0
- libXfont: version 1.5.2
- mesa: version 12.0.2
- mozilla-firefox: version 49.0.1
- xkeyboard-config: version 2.18
- xorg-server: version 1.18.4

Linux kernel:

- version 4.7.6
- aacraid: version 1.2.1-52011
- intel 10Gbit ethernet: revert to in-tree drivers
- r750: version 1.2.9-16_09_27

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
- 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.
- webGui: bug fix: Cannot manually specify virtIO iso in VM settings
- webGui: other changes: refer to github commit log

Share this post


Link to post
Share on other sites

Updated from RC4 and

 

webGui: generate VM xml with cpu topology as single-threaded when host cpu is AMD

 

Confirmed as working on my system

Share this post


Link to post
Share on other sites

I'm unable to edit files (move, delete, rename etc) in SMB shares from within VMs - only happened since RC5 I think.

 

 

I was also having slow file transfers like other users in RC4 - haven't had a chance to test (as can't move files!)

 

 

Update: Ignore - Ransomware plugin had triggered a false positive and had locked down SMB

highlander-diagnostics-20161126-1345.zip

Share this post


Link to post
Share on other sites

As I reported with rc4, with array autostart enable, after an unclean shutdown unRAID starts a non correcting check, same with rc5, is this the intended behavior now? 

Share this post


Link to post
Share on other sites

As I reported with rc4, with array autostart enable, after an unclean shutdown unRAID starts a non correcting check, same with rc5, is this the intended behavior now?

That's what the Community wanted.

Share this post


Link to post
Share on other sites

Upgraded smoothly, and preparing to remove the VFS Fruit settings from my Samba extras configuration, since it should be redundant now. Also thanks to my new host reboot and array restart procedures, my Windows 10 VM now has several days' more uptime than the host machine.

 

That would be another useful thing, but I think it's already in a feature request topic? Doing dompmsuspend <domain> disk, which does a suspend-to-disk, or else shutdown if the guest isn't configured for it. Acceptable so long as the virtual hardware configuration doesn't change (noticeably) between shutdown and restart. And possibly faster, since it won't trigger Windows Update if it's actually hibernating.

Share this post


Link to post
Share on other sites

As I reported with rc4, with array autostart enable, after an unclean shutdown unRAID starts a non correcting check, same with rc5, is this the intended behavior now?

That's what the Community wanted.

i think it the right decision!    If you want a Correcting check it is easy enough to cancel the automatic check and start a correcting one.    However the converse is not always true as an automatic check may make corrections that you did not want to happen and by then it would be too late.

Share this post


Link to post
Share on other sites

Are there any instructions on exactly how to do an upgrade from a previous 6.3 rc install?

 

I have v6.3.0-rc3 installed but can not remember exactly what steps I need to do to get to rc5.

 

I have the files downloaded and any help would be appreciated

Share this post


Link to post
Share on other sites

Are there any instructions on exactly how to do an upgrade from a previous 6.3 rc install?

 

I have v6.3.0-rc3 installed but can not remember exactly what steps I need to do to get to rc5.

 

I have the files downloaded and any help would be appreciated

Plugins - check for updates - upgrade unRaid OS listed at the bottom - reboot

 

Share this post


Link to post
Share on other sites

I try that but it says there are no updates available.

 

Can just replace the bzroot, bzroot-gui  and bzimage files on your flash drive with those from the RC5 release.  Dunno why you can't do it via the webui though....  ???

Share this post


Link to post
Share on other sites

I try that but it says there are no updates available.

Probably something wrong with your DNS / Default Gateway settings in Network Settings.  Can you install *any* plugin?  Do any apps have the ability to communicate with the outside world?

 

http://lime-technology.com/forum/index.php?topic=48508.msg465303#msg465303

Share this post


Link to post
Share on other sites

I try that but it says there are no updates available.

Probably something wrong with your DNS / Default Gateway settings in Network Settings.  Can you install *any* plugin?  Do any apps have the ability to communicate with the outside world?

 

http://lime-technology.com/forum/index.php?topic=48508.msg465303#msg465303

 

A quick check for plugin updates should provide the answer to these questions. 

Share this post


Link to post
Share on other sites

I try that but it says there are no updates available.

Probably something wrong with your DNS / Default Gateway settings in Network Settings.  Can you install *any* plugin?  Do any apps have the ability to communicate with the outside world?

 

http://lime-technology.com/forum/index.php?topic=48508.msg465303#msg465303

 

A quick check for plugin updates should provide the answer to these questions.

Nope.  Any errors in checking are not echoed back to the display.  The better test is from the console:

ping -c3 github.com

Share this post


Link to post
Share on other sites

Hi, I noticed that some of my files aren't showing up via SMB share in RC5. Upgraded from RC4. I can see that the files are there when looking directly in the Web UI and in console. But they don't all show up via SMB. I've tried moving the files around and they can show up elsewhere, but putting them back in one of the affected folder and they disappear again. I've tried renaming some of the files with no luck as long they are in these affected folders. Some of the files have spaces or french accents, but a lot of them don't have any.

 

I've tried going back to 6.2.4 and all of the files were back visible. Updated again to RC5 and still the same problem.

Also, I've tried accessing via Windows 10 and an Android box.

 

Anyone seen anything like this?

 

Share this post


Link to post
Share on other sites

Hi, I noticed that some of my files aren't showing up via SMB share in RC5. Upgraded from RC4. I can see that the files are there when looking directly in the Web UI and in console. But they don't all show up via SMB. I've tried moving the files around and they can show up elsewhere, but putting them back in one of the affected folder and they disappear again. I've tried renaming some of the files with no luck as long they are in these affected folders. Some of the files have spaces or french accents, but a lot of them don't have any.

 

I've tried going back to 6.2.4 and all of the files were back visible. Updated again to RC5 and still the same problem.

Also, I've tried accessing via Windows 10 and an Android box.

 

Anyone seen anything like this?

A screenshot showing what you're describing would be helpful

 

Sent from my SM-T560NU using Tapatalk

 

 

Share this post


Link to post
Share on other sites

Hi, think I found something. But I'm not exactly sure why this happened... I noticed that when I renamed the file to correct that wierd symbol, multiple files other came back after that don't have that symbol. This was working in 6.2.4. But the RC5 give this wierd behavior. I'm not 100% sure if this was happening in RC4 or not. Didn't pay attention.

 

Original Name when I had put the file : Pierre.Hébert.Premier.Spectacle.2014.mkv

Using ls -al now : Pierre.H\351bert.Premier.Spectacle.2014.mkv

File accessible using this wierd symbol : Pierre.H?bert.Premier.Spectacle.2014.mkv

 

Is reproduced every time I make a new file with that symbol via the console. Realized that making a new file wasn't always doing it. Don't know what happened there...

 

Hope this explain it a little better.

Thanks!

 

EDIT : the symbol doesn't appear correctly when pasted here. Not sure how to find what it is.

 

EDIT 2 : I've put back RC4 and the files that have the \351 or the wierd symbol aren't showing up but the other files aren't affected now. I can see everything else.

 

EDIT 3 :

Should make more tests and then write. Looks like files never showed up with that naming. Even with 6.2.4. Only now, some other files are not showing when this is mixed with RC5.

Probably my fault somewhere when I migrated from virtualized Unraid 5.x under vmware to when I passed to 6.0/6.1Beta or when I moved to run Unraid directly on the hardware.

I guess renaming files correctly will be my "fix".

 

Want anything before I do that?

screen.png.d3a5ded5f12911a1355ebb8a3dbb3688.png

Share this post


Link to post
Share on other sites

SMB (or at least Windows) won't be able to deal with certain characters in folder/file names. Whenever I have encountered this with downloads, it usually showed up in Windows as a folder or file that had a timestamp, but no actual filename displayed. Using the timestamp I was able to figure out which folders/files were at fault and after renaming them they appeared in Windows.

 

Another problem often encountered is the fact that SMB is not case-sensitive, so if you have 2 shares with the same name except for upper/lower case (perhaps created accidentally) only one of those shares will appear in Windows. People will complain that no files are showing in their share because the share being shown by Windows was an empty share that happened to have the same name (except for case) as the share they expected to see.

Share this post


Link to post
Share on other sites

Hi, yea I understand that, but was mostly wondering why the output list was different when switching Unraid version. In the end, correcting the names will fix all of it.

 

Thanks!

Share this post


Link to post
Share on other sites

Looks like either your Samba client or your terminal client is using CP1251 or latin1 instead of UTF-8, so your Unicode is broken. Character 233 is correct, but only for a latin1 code page, not for the correct UTF-8 code page.

 

It's a pity that even after all these years, PuTTY doesn't default to UTF-8 encoding.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.