Unraid OS version 6.11.2 available

Kilrah · November 6, 2022

The checkbox is for USB only. I have one VM that runs from a passed through USB drive and didn't need any change though.

From NVMe it should run without change since you'll already have boot order right if your VM works.

SimonF · November 6, 2022

36 minutes ago, craigr said:

Thank you!

So if you were to check your NVMe drive in form view, what line(s) would be added to your XML? I really don't want to have to parse through all my XML customizations when they get wiped out, and then potentially fiddle with the OVMF BIOS as well

The should be nothing different to your current setup. If you specify a boot order for the NVME drive the the boot order='value' will be added to the pci device example below of me adding 3.

  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Windows 10/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Windows10.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.221-1.iso'/>
      <target dev='hdb' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </controller>
    <filesystem type='mount' accessmode='passthrough'>
      <driver type='virtiofs' queue='1024'/>
      <binary path='/usr/libexec/virtiofsd' xattr='on'>
        <cache mode='always'/>
        <sandbox mode='chroot'/>
        <lock posix='on' flock='on'/>
      </binary>
      <source dir='/mnt/user/isos'/>
      <target dir='isos'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </filesystem>
    <interface type='bridge'>
      <mac address='52:54:00:d1:db:d1'/>
      <source bridge='br0'/>
      <model type='virtio-net'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='5910' autoport='no' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <audio id='1' type='none'/>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
      </source>
      <boot order='3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </hostdev>

Edited November 6, 2022 by SimonF

Danny08 · November 6, 2022

Last update to 6.11.1 somehow crashed my cli/non-gui boot. Without GUI it wouldnt boot.

This update fixed it and my server boots normally. Everythings working fine. Thank you, good work.

chis34 · November 6, 2022

Updated without issues. Thanks.

_cjd_ · November 6, 2022

Updated from 6.11.1 with a couple bumps along the road

boot seemed to hang with the last statement being: Starting Samba - I'm not sure this is the actual process that is stuck
after ~5min it finally came up to login with two error lines:
- error: failed to connect to hypervisor
- error: Operation not supported: Cannot use direct socket mode if no URI is set
Once into the UI, it took some shenanigans to be able to start the array
- Upon entering the array password, the "Start array" button remained disabled
- Removing focus from the array password field did not help - tried changing from passphrase to key and back, no luck also
- ticking "show password" DID eventually enable the "Start array" button (and clicking started the array successfully)

Once the array was running, everything else started up normally; 1 VM (HomeAssistant) and a handful of docker images. Nothing jumped out at me in system log (other than some errors about network unreachable trying to log...)

unr41dus3r · November 6, 2022

As reportet in UD Thread, with 6.11.2 XFS/BTRFS formatting of my 4TB drive is not working

Did an downgrade to 6.11.1 and format works again

craigr · November 6, 2022

9 hours ago, Kilrah said:

The checkbox is for USB only. I have one VM that runs from a passed through USB drive and didn't need any change though.

From NVMe it should run without change since you'll already have boot order right if your VM works.

8 hours ago, SimonF said:

The should be nothing different to your current setup. If you specify a boot order for the NVME drive the the boot order='value' will be added to the pci device example below of me adding 3.

  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Windows 10/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Windows10.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.221-1.iso'/>
      <target dev='hdb' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </controller>
    <filesystem type='mount' accessmode='passthrough'>
      <driver type='virtiofs' queue='1024'/>
      <binary path='/usr/libexec/virtiofsd' xattr='on'>
        <cache mode='always'/>
        <sandbox mode='chroot'/>
        <lock posix='on' flock='on'/>
      </binary>
      <source dir='/mnt/user/isos'/>
      <target dir='isos'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </filesystem>
    <interface type='bridge'>
      <mac address='52:54:00:d1:db:d1'/>
      <source bridge='br0'/>
      <model type='virtio-net'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='5910' autoport='no' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <audio id='1' type='none'/>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
      </source>
      <boot order='3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </hostdev>

I had to screw with it a little bit, but it wasn't bad. I upgraded unRAID successfully and everything is working well (VM's and Dockers). Remember, I did not have any "boot order" defined in my xml before (it was in the OVMF BIOS setup I think). If I tried to use boot order before, my VM would not start. I had to work around this way:

  <os>
    <type arch='x86_64' machine='pc-i440fx-6.2'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/2c4db39b-fc53-1762-d1ba-9c768e033e45_VARS-pure-efi-tpm.fd</nvram>
    <boot dev='hd'/>
  </os>

This VM was built on Windows 10 and spaces_win_clover.img to load the NVMe bare-metal. Upgrading from Windows 10 to 11 and then removing the clover image caused unique issues for me I suspect.

Anyway, I upgraded unRAID, put a check for my NVMe in the new Windows template, defined its boot order as "1", saved the template, compared it to my old xml, modified my old xml to remove the <boot dev='hd'/> lines and add <boot order='1'/>. Everything started up on the first try.

No issues to report so far. The unRAID update is working well.

Thanks all!

craigr

Edited November 6, 2022 by craigr

FlyingTexan · November 7, 2022

On 11/4/2022 at 11:02 PM, limetech said:

The 6.11.2 release is focused on bug fixes and minor improvements. Please note there are important security mitigations in Samba, all users are encouraged to update.

As always, prior to updating, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup".

Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report.

Version 6.11.2 2022-11-04

This release is focused on bug fixes and minor improvements. Please note there are important security mitigations in Samba, all uses are encouraged to update.

VM Manager

If you boot a VM from a passed physical USB device there is a new setting called Enable USB boot which must be set to Yes. This is due to feature change in the latest OVMF component.

Changes:

Add boot order for USB and USB Boot option. Using 'boot order' field VM can boot from a passed-through NVMe controller/device.

Add virtiofs/9p Unraid share mapping.

CD Hotplug bug fix.

Fix Hotplug within Templates.

Fix changing from passthru to custom CPU.

Test for guest agent to suppress error message in libvirt log, and show text for guest not running or guest agent is not installed.

Fix unable to change HyperV settings.

Add 'start with console' option.

OVMF for QEMU: version edk2-stable202208

Wireguard

Changes:

Fixed problem setting up tunnels if using default network.cfg settings.

Fix typo setting up routes.

Plugin manager

Changes:

If plugin files cannot be read from CDN URL, fall back to non-CDN URL.

Enforce plugin files must end in '.plg'.

Fix post hook failing when plugin download fails.

Adjust the wget parameters to keep it from indefinitely hanging.

Scheduler

For scheduled Parity Checks, change default mode to Non-correcting. In case there are disk issues during a parity check it would be safer to have the default be non-correct. If sync errors are detected then the user can analyze the log and act accordingly.

Misc. webGUI

Changes:

DashStats: The inbound networkstats is out of place when numeric value is xxx.x.

Docker: Add/clarify Help to Docker Custom Network settings.

Docker: Fix display aberration on orphan images

SMART attributes: clarify message: "Can not read attributes" to "Attributes not available"

ShareEdit/ShareList: show pool not defined when share pool is not a defined pool

Linux kernel

version 5.19.17

patch: additional NVMe BOGUS_NID quirks for non-compliant devices reported by users

sound support:

CONFIG_SOUND: Sound card support

CONFIG_SND: Advanced Linux Sound Architecture

CONFIG_SND_OSSEMUL: Enable OSS Emulation

CONFIG_SND_PCM_OSS: OSS PCM (digital audio) API

CONFIG_SND_HRTIMER: HR-timer backend support

CONFIG_SND_SUPPORT_OLD_API: Support old ALSA API

CONFIG_SND_PROC_FS: Sound Proc FS Support

CONFIG_IPV6: The IPv6 protocol (change from module to built-in)

Base Distro

Package updates including CVE mitigations:

bash: version 5.2.002

bind: version 9.18.8 (CVE-2022-38178 CVE-2022-38178 CVE-2022-3080 CVE-2022-2795)

btrfs-progs: version 6.0

curl: version 7.86.0

dbus: version 1.14.4

freeglut: version 3.4.0

git: version 2.38.1 (CVE-2022-39253 CVE-2022-39260)

glibc-zoneinfo: version 2022e

harfbuzz: version 5.3.1

icu4c: version 72.1

iproute2: version 6.0.0

kernel-firmware: version 20221017_48407ff

less: version 608

libXmu: version 1.1.4

libXrender: version 0.9.11

libedit: version 20221009_3.1

libffi: version 3.4.4

libgpg-error: version 1.46

libpciaccess: version 0.17

libunistring: version 1.1

libxkbfile: version 1.1.1

libxshmfence: version 1.3.1

lsof: version 4.96.4

nginx: version 1.22.1

openssh: version 9.1p1

php: version 7.4.32

pixman: version 0.42.0

rsync: version 3.2.7

samba: version 4.17.2 (CVE-2021-20251 CVE-2022-3437 CVE-2022-3592)

sudo: version 1.9.12

tree: version 2.0.4

xkeyboard-config: version 2.37

xterm: version 375

zlib: version 1.2.13 (CVE-2022-37434)

Why not use latest Linux kernel?

Dazog · November 7, 2022

7 minutes ago, FlyingTexan said:

Why not use latest Linux kernel?

6.1 is due in Dec and is LTS, would make sense to stay on 5.19 then jump to 6.1 since 6.0 will go EOL shortly after 6.1 is out.

PhilipJFry · November 7, 2022

Hi @limetech
Upgrade went ok.

But SMB very unhappy now. Shares no longer visible on the network.

Nov  7 16:51:36 Futurama  emhttpd: read SMART /dev/sde
Nov  7 16:54:43 Futurama  dhcpcd[1229]: br0: failed to renew DHCP, rebinding
Nov  7 16:54:43 Futurama  dhcpcd[1229]: br0: leased 192.168.7.227 for 14400 seconds
Nov  7 16:58:35 Futurama  smbd[29181]: [2022/11/07 16:58:35.887620,  0] ../../source3/smbd/open.c:958(fd_openat)
Nov  7 16:58:35 Futurama  smbd[29181]:   Too many open files, unable to open more!  smbd's max open files = 16424
Nov  7 16:58:36 Futurama  smbd[29181]: [2022/11/07 16:58:36.034052,  0] ../../source3/smbd/open.c:958(fd_openat)
Nov  7 16:58:36 Futurama  smbd[29181]:   Too many open files, unable to open more!  smbd's max open files = 16424
Nov  7 16:58:36 Futurama  smbd[29181]: [2022/11/07 16:58:36.050145,  0] ../../source3/smbd/files.c:1199(synthetic_pathref)
Nov  7 16:58:36 Futurama  smbd[29181]:   synthetic_pathref: opening [events/albums/frame/_frame-singapore/2018-10-20181004_122419.jpg] failed
Nov  7 16:58:36 Futurama  smbd[29181]: [2022/11/07 16:58:36.626251,  0] ../../source3/smbd/files.c:1199(synthetic_pathref)
Nov  7 16:58:36 Futurama  smbd[29181]:   synthetic_pathref: opening [events/albums/frame] failed

Other relevant info 🙂

root@Futurama:~# cat /proc/sys/fs/file-max
3231614
root@Futurama:~# cat /proc/sys/fs/file-nr
20256   0       3231614
root@Futurama:~# sysctl fs.file-max
fs.file-max = 3231614
root@Futurama:~# ulimit -n
40960
root@Futurama:~# ulimit –Sn
bash: ulimit: –Sn: invalid number
root@Futurama:~# ulimit -Hn
40960

Edited November 7, 2022 by PhilipJFry

dlandon · November 7, 2022

I've responded in your other post. Please keep the discussion there.

PeteAron · November 7, 2022

fyi. i updated my primary server from 6.8.3 to 6.11.2 using the webtool without issue.

ChatNoir · November 7, 2022

Updated yesterday evening without a hitch.

GeorgeJetson20 · November 8, 2022

Upgraded from 6.11.1 to 6.11.2 - A little nervous after reading some of the issues but went without a hitch. Checked my VM's and Docker and SMB's and no issues so far. I still have another server on 6.9.2 but i'm afraid to update that yet. That can't go down if there are any issues.

chronkus · November 8, 2022

Updated from 6.11.1 to 6.11.2 - Boot hangs on "Starting Samba". Booting into safe mode and removing the My Servers plugin (dynamix.unraid.net.plg) resolves it. Tried again with a clean plugin install but the issue persists.

Edited November 8, 2022 by chronkus

ljm42 · November 8, 2022

12 hours ago, chronkus said:

Updated from 6.11.1 to 6.11.2 - Boot hangs on "Starting Samba". Booting into safe mode and removing the My Servers plugin (dynamix.unraid.net.plg) resolves it. Tried again with a clean plugin install but the issue persists.

~~Interesting. Would you please provide your diagnostics.zip (from Tools -> Diagnostics) after booting normally without the My Servers plugin? I want to look for settings to try and reproduce this.~~

~~And to clarify, what happens if you have a working system and then install the plugin? Are there immediate issues or is it fine until a reboot?~~

~~Thanks~~

Edit - moved this conversation here https://forums.unraid.net/topic/130696-my-servers-plugin-causes-boot-hang-after-updating-to-6112/

bbrodka · November 8, 2022

6.11.2 has trouble formatting newly installed drives

see thread

JorgeB · November 8, 2022

2 minutes ago, bbrodka said:

6.11.2 has trouble formatting newly installed drives

see thread

It's a known issue and already fixed, v6.11.3 should be available very soon.

Adam3490 · November 8, 2022

8 hours ago, JorgeB said:

It's a known issue and already fixed, v6.11.3 should be available very soon.

Thank you very much!

Unraid OS version 6.11.2 available

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

limetech

SpencerJ

JorgeB

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Version 6.11.2 2022-11-04

VM Manager

Wireguard

Plugin manager

Scheduler

Misc. webGUI

Linux kernel

Base Distro

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation