Unraid OS version 6.9.0 available


332 posts in this topic Last Reply

Recommended Posts

6.9.0-rc2 -> 6.9.0, smooth, no issues.

 

One tiny data point: After the upgrade, I received three notice messages for 3 of my drives:

"Notice [TOWER] - Disk 3 returned to normal utilization level"

I never saw a warning state while in previous versions. Have the default utilization thresholds changed?

 

Great job, Limetech folks!!

Link to post
  • Replies 331
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Refer to Summary of New Features for an overview of changes since version 6.8.   To upgrade: First create a backup of your USB flash boot device: Main/Flash/Flash Backup If yo

Successfully upgraded 3 (encrypted) systems from 6.8.3 to 6.9.0.   One of the 6.8.3 systems was running nvidia-plugin, upgrade procedure:   0. Stop docker containers from auto-star

I'll wait for 6.9.1.   There's always some unforeseen bugs that crop up on hardware and I've learned there's no reason to rush these things.      Thanks for all the hard work

Posted Images

5 hours ago, Arragon said:

After updating to 6.9.0 all my user shares are gone. /mnt looks like this


d---------  1 root   root    0 Jan  1  1970 user/

and I can't change permission on that


# chmod 1777 /mnt/user
chmod: changing permissions of '/mnt/user': No such file or directory

 

You should create a new post within General Support and include  your diagnostics

Link to post

Update from 6.8.3 went smooth as always. Temp sensors on TRX40 are working now. 😘

Switching from old pci-vfio in syslinux config to the new method also went without any issues.

 

But a small thing I noticed. Syslog isn't starting with the normal boot process entries. The first entries for me are from some plugin checks/updates

 

grafik.thumb.png.137561cc1e4e361031fb238ce15ca767.png

 

Is this normal behaviour? Tried it with Firefox (main Browser) and Brave (never used for my server before). Same result. Is there a max line limit now for showing the logs and I can't find the settings?

Link to post

After the update to 6.9 Final, the HDD's (sata) no longer go into standby after 30 minutes, no spin down.

I have not changed any settings or installed new plugins.

Edited by xruchai
Link to post

I'm excited to upgrade, great work guys!  Just a quick question (and I read the release notes), but is their any major changes to networking functionality?  Specifically communication between bridges and/or a method to set a default bridge for docker containers (similar to what exists for VM's)

 

Thanks again for all the hard work everyone!!


~Spritz

Link to post
10 minutes ago, bastl said:

Update from 6.8.3 went smooth as always. Temp sensors on TRX40 are working now. 😘

Switching from old pci-vfio in syslinux config to the new method also went without any issues.

 

But a small thing I noticed. Syslog isn't starting with the normal boot process entries. The first entries for me are from some plugin checks/updates

 

grafik.thumb.png.137561cc1e4e361031fb238ce15ca767.png

 

Is this normal behaviour? Tried it with Firefox (main Browser) and Brave (never used for my server before). Same result. Is there a max line limit now for showing the logs and I can't find the settings?

I believe this is due to the size of the syslog buffer provided to the WebUI and it was mentioned in one of the beta or RC threads. The full syslog should still be available on the filesystem itself.

 

EDIT: Bug report already opened for it: 

 

Edited by weirdcrap
Link to post
3 minutes ago, weirdcrap said:

I believe this is due to the size of the syslog buffer provided to the WebUI and it was mentioned in one of the beta or RC threads. The full syslog should still be available on the filesystem itself.

Thx for the info. Is there any settings to show again the full syslog inside the WebUI?

 

 

Edit:

I was to quick. Noticed your edit to late. Thanks for the link

Edited by bastl
Link to post
2 minutes ago, bastl said:

Thx for the info. Is there any settings to show again the full syslog inside the WebUI?

Not that I'm aware of at this time. I assume it would be rather trivial to increase the buffer size but I'm not sure where in UnRAID this is handled without digging through code.

 

If you follow that bug report @John_Mopened I bet LimeTech will come up with a workaround pretty quick for those who want it.

Link to post
6 minutes ago, bastl said:

Thx for the info. Is there any settings to show again the full syslog inside the WebUI?

 

 

Edit:

I was to quick. Noticed your edit to late. Thanks for the link

sed -i 's/1000/3000/' /usr/local/emhttp/plugins/dynamix/include/Syslog.php

 

run this in terminal to fix.

Link to post
4 minutes ago, SimonF said:

sed -i 's/1000/3000/' /usr/local/emhttp/plugins/dynamix/include/Syslog.php

 

run this in terminal to fix.

Thanks. Does this survive a server reboot?

 

Link to post
Just now, bastl said:

Thanks. Does this survive a server reboot?

 

I imagine not as those files are unpacked fresh from the flash each boot. you would need to add it to your GO file.

Edited by weirdcrap
Link to post

@limetech@SpencerJ

 

Can this be appended to the first post so people know if they revert they need to add the cache back in as I think its buried in the release notes and people are not seeing it..

 

Note: A pre-6.9.0 cache disk/pool is now simply a pool named "cache".  When you upgrade a server which has a cache disk/pool defined, a backup of config/disk.cfg will be saved to config/disk.cfg.bak, and then cache device assignment settings are moved out of config/disk.cfg and into a new file, config/pools/cache.cfg.  If later you revert back to a pre-6.9.0 Unraid OS release you will lose your cache device assignments and you will have to manually re-assign devices to cache.  As long as you reassign the correct devices, data should remain intact.

 

Also if they start the array can they stop and add if they missed this step or have auto start *yes?

Link to post

Updated from 6.9.0 rc2 to 6.9.0 stable and everything went smoothy as expected.

 

Thanks for all the hard work by unRAID team, @ich777 for his amazing plugins and support, and for @linuxserver.io developers for making almost any software you can imagine in a container and maintaining them.

Link to post
4 hours ago, pervel said:

Is it necessary to upgrade if you're on 6.9.0-rc2? Has anything changed?

Yes.  The wiki doc shows the consolidated changes (changes since 6.8.3) but here are changes from -rc2 to stable:

 

Version 6.9.0 2021-02-27 (vs -rc2)

Base distro:

  • bind: [removed]
  • btrfs-progs: version 5.10
  • ca-certificates: version 20201219
  • curl: version 7.74.0 (CVE-2020-8286 CVE-2020-8285 CVE-2020-8284)
  • dnsmasq: version 2.84 (CVE-2020-25681 CVE-2020-25682 CVE-2020-25683 CVE-2020-25684 CVE-2020-25685 CVE-2020-25686 CVE-2020-25687)
  • intel-microcode: version 20210216
  • kernel-firmware: version 20210211_f7915a0
  • openssl: version 1.1.1i
  • openssl-solibs: version 1.1.1i
  • p11-kit: version 0.23.22 (CVE-2020-29361 CVE-2020-29361 CVE-2020-29361)
  • php: version 7.4.15
  • samba: version 4.12.11
  • sudo: version: 1.9.3p2 (CVE-2021-23239 CVE-2021-23240)
  • wireguard-tools: version 1.0.20210223

Linux kernel:

  • version 5.10.19

Management:

  • bug fix: rename /etc/krb.conf to /etc/krb5.conf
  • emhttpd: bug fix: initial device temperatures not being displayed
  • emhttpd: bug fix: No Smartdata for non standard controller type
  • plugin: support sha256 file validation
  • smart-one.cfg keeps SMART info per-ID instead of per-slot; disk warning/critical config moved to disk/pool cfg
  • wireguard support: rc.wireguard: add iptables rules
  • webgui: Add notification agent for Discord
  • webgui: Fix: Dashboard / Docker scrolling on iPad devices
  • webgui: dockerMan: Selectable start upon install
  • webgui: fix: login prompt when switching between servers
  • webgui: sanitize input on tail_log
  • webgui: SysDevs - warn if leave page without saving
  • webgui: Diagnostics: Remove SHA256 Hashes
  • webgui: Display settings: colors should be 3 or 6 character hex digits
  • webgui: Fix: properly set samesite cookie (fix login issue with Safari)
  • webgui: Switch Diagnostics to web socket
  • Like 1
  • Thanks 1
Link to post

I just wanted to say that this is the best feature-set of a major release I've seen in a long time. You guys managed to pack in a lot of community requested items and we love to see it. Great work!

  • Like 1
  • Thanks 1
Link to post
2 hours ago, doron said:

6.9.0-rc2 -> 6.9.0, smooth, no issues.

 

One tiny data point: After the upgrade, I received three notice messages for 3 of my drives:

"Notice [TOWER] - Disk 3 returned to normal utilization level"

I never saw a warning state while in previous versions. Have the default utilization thresholds changed?

 

Great job, Limetech folks!!

Yes, see here.

Link to post
7 hours ago, hawihoney said:

 

I do have two system/appdata folders. One on an unassigned device and one on an array device. The system share is set to "Use cache=No". E.g.:

 

/mnt/disk17/system/

/mnt/disks/NVMe1/system/

 

VMs are running on array, Dockers are split between both. Docker/VM settings are set to:

 

/mnt/disk17/system/docker.img

/mnt/disk17/system/libvirt.img

 

Should I expect problems?

 

 

I would say it's a possibility... One of my prod systems is using a completely non-standard zfs setup, with appdata living on a pair of P3500 NVMe drive, and everything else living on a 24 drive zfs pool, with the mount point for appdata being taken care of in the go file on boot - as I've not had enough time to ensure that I can stick around to fix it if things go south, I haven't touched it yet.

 

Definitely back up your flash drive before updating, and if things aren't working afterwards, compare the domain and network config files post-upgrade for unexpected changes.

Link to post
1 hour ago, weirdcrap said:

With the GPU changes (https://wiki.unraid.net/Unraid_OS_6.9.0#GPU_Driver_Integration) the old method of enabling Intel QuickSync via the go file is no longer recommended then?

 


# Enable Intel QuickSync HW Transcoding
modprobe i915 
chmod -R 777 /dev/dri

 

Correct, you'll instead un-blacklist the driver by creating a file to override the driver blacklist:

 

touch /boot/config/modprobe.d/i915.conf

Link to post
23 minutes ago, SimonF said:

@limetech@SpencerJ

 

Can this be appended to the first post so people know if they revert they need to add the cache back in as I think its buried in the release notes and people are not seeing it..

 

Note: A pre-6.9.0 cache disk/pool is now simply a pool named "cache".  When you upgrade a server which has a cache disk/pool defined, a backup of config/disk.cfg will be saved to config/disk.cfg.bak, and then cache device assignment settings are moved out of config/disk.cfg and into a new file, config/pools/cache.cfg.  If later you revert back to a pre-6.9.0 Unraid OS release you will lose your cache device assignments and you will have to manually re-assign devices to cache.  As long as you reassign the correct devices, data should remain intact.

 

Also if they start the array can they stop and add if they missed this step or have auto start *yes?

 

Good suggestion.  I added a note about Reverting to the OP.

Link to post
8 minutes ago, limetech said:

 

Good suggestion.  I added a note about Reverting to the OP.

 

I think it'd also be helpful to note specific 'gotchas' within the original announcement that were addressed within the previous beta releases announcements - many haven't touched 6.9 yet and are moving straight from 6.8.3, so information on things like the the blacklisting of video drivers aren't readily at hand to them.

 

i.e. "For those with manual edits to their /boot/config/go file, please take note of <modprobe stuff>"

Edited by BVD
Link to post
5 hours ago, mgrx said:

I've just updated, and i get a noVNC error on every vm i try to access using the integrated vnc client:

 

 

 

Same issue on my end as well. - Clearing browser cache corrected this.

2021-03-02_10-11-31.png

Edited by archedraft
Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.