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

• IGD Device Assignment to VMs
  

 

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

 

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

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

Thanks for the update.

 

RC4 still has this issue: https://lime-technology.com/forum/index.php?topic=52857.0 . This does not happen in 6.2.

unjosh-diagnostics-20161111-1513.zip

Upgraded without issues. One possible exception (though not wrt unraid itself):

 

- Rebooted the array without doing a stop of the array first (unsure if that reboot triggers a stop by itself, did not look like it)

- After reboot fix common problems showed an error wrt an unclean shutdown

 

However no parity check started automatically.

Upgraded without issues. One possible exception (though not wrt unraid itself):

 

- Rebooted the array without doing a stop of the array first (unsure if that reboot triggers a stop by itself, did not look like it)

- After reboot fix common problems showed an error wrt an unclean shutdown

 

However no parity check started automatically.

 

Reboot or Shutdown in v6.3 performs a clean operation, i.e. array is stopped in the proper way.

 

I guess Squid needs to have a look at his plugin

 

Time is wrong in is this version (+1 hr).

VM's report it ok (or Plex docker)

Dunno about previous versions as it did not pop-up in front of me.

My backup server running on 6.2.3 is reporting it ok with same region & ntp settings.

I am on UTC+2 (Athens, Bucharest..).

 

cheers,

Dan

 

Sent from my SM-G920F using Tapatalk

 

Upgraded without issues. One possible exception (though not wrt unraid itself):

 

- Rebooted the array without doing a stop of the array first (unsure if that reboot triggers a stop by itself, did not look like it)

- After reboot fix common problems showed an error wrt an unclean shutdown

 

However no parity check started automatically.

 

Reboot or Shutdown in v6.3 performs a clean operation, i.e. array is stopped in the proper way.

 

I guess Squid needs to have a look at his plugin

 

Notifications really look nice in this version !

 

 

Verzonden vanaf mijn iPhone met Tapatalk

Upgraded and the docker/vm tabs were at the top of the screen on boot up even with the array offline - still having the same issue where it shows "Starting Services" then the page stops trying but the server does load up properly

 

Not sure if my server diagnostics will help these since its a gui thing - let me know

 

Jamie

- mover: add start/stop/status subcommands (experimental)

 

How do I try these?

 

mover status

 

when it was running but there was no output.

Upgraded without issues. One possible exception (though not wrt unraid itself):

 

- Rebooted the array without doing a stop of the array first (unsure if that reboot triggers a stop by itself, did not look like it)

- After reboot fix common problems showed an error wrt an unclean shutdown

 

However no parity check started automatically.

 

Reboot or Shutdown in v6.3 performs a clean operation, i.e. array is stopped in the proper way.

 

I guess Squid needs to have a look at his plugin

Works perfectly fine on my systems under normal circumstances.  There *may* be an edge case scenario where if the array is offline and FCP runs a scheduled scan and it was the only scan ever run since the last reboot and a subsequent reboot then happens.  Would have to find time when I'm bored to run through that logic again but that's a relatively low priority at the moment for me. 

I seem to be having an issue with the passing through of a usb3 controller, the first time after reboot I ran an libreElec vm with IGD passthrough and the usb controller everything worked perfectly, then after a reboot my mouse plugged into the passed through usb controller would not work. I get this message in my log "Cannot reset device 0000:00:14.0, no available reset mechanism." this is the address of my usb controller. If I start up my windows 10 vm with usb controller passed through with vnc graphics, the intel controller shows up in windows but does not show any devices plugged into this controller.

Time is wrong in is this version (+1 hr).

VM's report it ok (or Plex docker)

Dunno about previous versions as it did not pop-up in front of me.

My backup server running on 6.2.3 is reporting it ok with same region & ntp settings.

I am on UTC+2 (Athens, Bucharest..).

 

I found the cause of your problem:

 

As of September 2016, the Europe/Istanbul time zone is permanently on Summer Time / DST, so it now has a permanent offset of UTC+3.

 

You'll have to wait until LT acknowledges this and includes separate time zones for Athens, Bucharest, and Istanbul. (Yes, all three normally have their own zoneinfo files. Of course, it looks "safe" to assume Athens = Bucharest, for the sake of reducing configuration options.)

I've split off the posts about shutdown of a Windows 10 VM to the following:

 

  Shutting down Win 10 VM that insists on updating Windows

Time is wrong in is this version (+1 hr).

VM's report it ok (or Plex docker)

Dunno about previous versions as it did not pop-up in front of me.

My backup server running on 6.2.3 is reporting it ok with same region & ntp settings.

I am on UTC+2 (Athens, Bucharest..).

 

I found the cause of your problem:

 

As of September 2016, the Europe/Istanbul time zone is permanently on Summer Time / DST, so it now has a permanent offset of UTC+3.

 

You'll have to wait until LT acknowledges this and includes separate time zones for Athens, Bucharest, and Istanbul. (Yes, all three normally have their own zoneinfo files. Of course, it looks "safe" to assume Athens = Bucharest, for the sake of reducing configuration options.)

Beirut utc+2 works instead.

 

Sent from my SM-G920F using Tapatalk

 

 

Anyone with AMD hardware test this to see is the VM issues have been resolved?

 

Sent from my SM-N910V using Tapatalk

 

 

Anyone with AMD hardware test this to see is the VM issues have been resolved?

 

Sent from my SM-N910V using Tapatalk

 

No change, running an AMD A8-7600 Radeon R7 on an A88XM-Plus MB with RC4

 

XML is manually modified to the below which seems to suppress the errors

 

  <cpu mode='host-passthrough'>

    <topology sockets='1' cores='1' threads='2'/>

  </cpu>

 

but log still shows

 

2016-11-12T23:22:16.086993Z qemu-system-x86_64: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.

Time is wrong in is this version (+1 hr).

VM's report it ok (or Plex docker)

Dunno about previous versions as it did not pop-up in front of me.

My backup server running on 6.2.3 is reporting it ok with same region & ntp settings.

I am on UTC+2 (Athens, Bucharest..).

 

I found the cause of your problem:

 

As of September 2016, the Europe/Istanbul time zone is permanently on Summer Time / DST, so it now has a permanent offset of UTC+3.

 

You'll have to wait until LT acknowledges this and includes separate time zones for Athens, Bucharest, and Istanbul. (Yes, all three normally have their own zoneinfo files. Of course, it looks "safe" to assume Athens = Bucharest, for the sake of reducing configuration options.)

Beirut utc+2 works instead.

 

Sent from my SM-G920F using Tapatalk

 

Coincidentally, the same time zone, and the same DST, even though it's Asia and not EU. Good find, though it still needs to be fixed.

 

For instance, how were 768 zoneinfo files reduced to just 94?

 

Anyone with AMD hardware test this to see is the VM issues have been resolved?

 

Sent from my SM-N910V using Tapatalk

  <cpu mode='host-passthrough'>

    <topology sockets='1' cores='1' threads='2'/>

  </cpu>

 

but log still shows

 

2016-11-12T23:22:16.086993Z qemu-system-x86_64: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.

Why not:

<cpu mode='host-passthrough'>
  <topology sockets='1' cores='2' threads='1'/>
</cpu>

Anyone with AMD hardware test this to see is the VM issues have been resolved?

 

Sent from my SM-N910V using Tapatalk

 

No change, running an AMD A8-7600 Radeon R7 on an A88XM-Plus MB with RC4

 

XML is manually modified to the below which seems to suppress the errors

 

  <cpu mode='host-passthrough'>

    <topology sockets='1' cores='1' threads='2'/>

  </cpu>

 

but log still shows

 

2016-11-12T23:22:16.086993Z qemu-system-x86_64: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.

Figures, maybe someone will look at it for us now.  Sucks not being able to upgrade past 6.1.9. 

 

Maybe LT should consider releasing a security patch update without messing with QEMU from 6.1.9. 

 

Sent from my SM-N910V using Tapatalk

 

 

Is there a reason why:

 

mozilla-firefox

 

is in this repo? Is LT providing us with a GUI now?  Is this a package dependency?

Is there a reason why:

 

mozilla-firefox

 

is in this repo? Is LT providing us with a GUI now?  Is this a package dependency?

Since 6.1  A boot option to start with a local GUI.  Generally only used if your main way of interfacing with the webUI is through a VM on unRaid

Anyone with AMD hardware test this to see is the VM issues have been resolved?

 

Sent from my SM-N910V using Tapatalk

 

No change, running an AMD A8-7600 Radeon R7 on an A88XM-Plus MB with RC4

 

XML is manually modified to the below which seems to suppress the errors

 

  <cpu mode='host-passthrough'>

    <topology sockets='1' cores='1' threads='2'/>

  </cpu>

 

but log still shows

 

2016-11-12T23:22:16.086993Z qemu-system-x86_64: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.

Figures, maybe someone will look at it for us now.  Sucks not being able to upgrade past 6.1.9. 

 

Maybe LT should consider releasing a security patch update without messing with QEMU from 6.1.9. 

 

Sent from my SM-N910V using Tapatalk

have you tried setting the Threads='1' as suggested?  That fixed the error message for me on my AM`d system.

Anyone with AMD hardware test this to see is the VM issues have been resolved?

 

Sent from my SM-N910V using Tapatalk

 

No change, running an AMD A8-7600 Radeon R7 on an A88XM-Plus MB with RC4

 

XML is manually modified to the below which seems to suppress the errors

 

  <cpu mode='host-passthrough'>

    <topology sockets='1' cores='1' threads='2'/>

  </cpu>

 

but log still shows

 

2016-11-12T23:22:16.086993Z qemu-system-x86_64: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.

Figures, maybe someone will look at it for us now.  Sucks not being able to upgrade past 6.1.9. 

 

Maybe LT should consider releasing a security patch update without messing with QEMU from 6.1.9. 

 

Sent from my SM-N910V using Tapatalk

have you tried setting the Threads='1' as suggested?  That fixed the error message for me on my AM`d system.

 

I don't have my AMD boards running at the moment, so can't check. So is this only an error message or does it affect starting the VM or performance hit? If it's serious enough, maybe a defect report should be added.

LT should be able to set threads to 1 when AMD CPUs are detected.

Anyone with AMD hardware test this to see is the VM issues have been resolved?

 

Sent from my SM-N910V using Tapatalk

 

No change, running an AMD A8-7600 Radeon R7 on an A88XM-Plus MB with RC4

 

XML is manually modified to the below which seems to suppress the errors

 

  <cpu mode='host-passthrough'>

    <topology sockets='1' cores='1' threads='2'/>

  </cpu>

 

but log still shows

 

2016-11-12T23:22:16.086993Z qemu-system-x86_64: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.

Figures, maybe someone will look at it for us now.  Sucks not being able to upgrade past 6.1.9. 

 

Maybe LT should consider releasing a security patch update without messing with QEMU from 6.1.9. 

 

Sent from my SM-N910V using Tapatalk

have you tried setting the Threads='1' as suggested?  That fixed the error message for me on my AM`d system.

 

I don't have my AMD boards running at the moment, so can't check. So is this only an error message or does it affect starting the VM or performance hit? If it's serious enough, maybe a defect report should be added.

LT should be able to set threads to 1 when AMD CPUs are detected.

There is a defect report.. see AMD CPU KVM bug in the defect forum.

 

Sent from my SM-N910V using Tapatalk

 

 

And it does appear to affect the performance on my machine.  I don't have raw data to prove this and it is merely opinion based on my observations.  I followed the instructions in the defect report thread and it did resolve the errors but on my machince, all VMs were broken in one way or another, including Ubuntu server and OpenELEC

 

Sent from my SM-N910V using Tapatalk

 

 

LT should be able to set threads to 1 when AMD CPUs are detected.

 

This code already exists in the current RC, but it doesn't actively scan existing VMs that were created PRIOR to that fix being put in place.  As such, you need to click "Edit" and then "Update" on each of your existing VMs before starting them in the new version.  This will remove any custom XML you've applied, but it will also fix the topology section of the XML to properly use cores, not threads.

 

If anyone has an AMD system, please test this for us and reply back here with confirmation.

LT should be able to set threads to 1 when AMD CPUs are detected.

 

This code already exists in the current RC, but it doesn't actively scan existing VMs that were created PRIOR to that fix being put in place.  As such, you need to click "Edit" and then "Update" on each of your existing VMs before starting them in the new version.  This will remove any custom XML you've applied, but it will also fix the topology section of the XML to properly use cores, not threads.

 

If anyone has an AMD system, please test this for us and reply back here with confirmation.

 

That's good to know. Didn't see anything about it in the release notes