Unraid OS version 6.9.0 available


Recommended Posts

1 hour ago, mcrommert said:

Well like the last rc - you still can't set the alarm temp for cache (at least) drives

Please post a bug report or to existing report - this should be fixed.  Note that in the transition to 6.9.0 all the non-default SMART settings (such as controller type) along with temperature warning/critical thresholds, as well as storage volume free space thresholds must be manually set up again.

Link to comment
4 minutes ago, limetech said:

 

We're trying to up our documentation game!  If you, or anyone else, want to contribute to wiki docs, please PM @Spencer or @jonp who will give you edit privilege. 👍

 

 

 

@limetech FYI that's not right right Spencer (unless I'm nuts of course lol) - Anyone else looking to request, the above should be @SpencerJ 👍

  • Haha 1
Link to comment
3 minutes ago, limetech said:

 

Yes we'll get on this.

As always.  You guys are fast on keeping us on the latest and greatest.

 

Just surprised you didn't wait until the 1 year announcement of 6.9 beta to give us the final version ;)

 

  • Haha 5
Link to comment

Upgrade went smooth! Great job Limetech team! Now in the process of transitioning unassigned devices to pools.

 

Question -- I know there was a previous issue with SSDs and excessive writes with btrfs, so I switched all my SSDs to xfs a while back. I see that any new pool defaults to btrfs. Has the excessive writes issue been fixed? Is there any benefit to running btrfs on single SSD pools or should I stick with xfs? THANKS!

  • Like 1
Link to comment
32 minutes ago, bergePanzer581 said:

Awesome! Great work guys! does the GPU driver blacklisting mean we can blacklist a gpu from UNRAID for easy pass-through? I guess headless pass-through is an (un)official thing now?

Correct.  The now-included ast, i914, amdgpu, and radeon drivers are already blacklisted by default.  You can un-blacklist them to provide proper console video if you want.

  • Like 1
Link to comment

Upgrade was seamless from 6.9.0-rc2

 

Noticed this is coming up at end of boot process, not sure if unraid issue, or a plugin issue (maybe @ich777)

/bin/bash: line 33 [: ==: unary operator expected

 

Also this issue still persists, will create new issue in stable reference this issue

 

  • Like 1
Link to comment
4 minutes ago, Boomháuer said:

Awesome, just upgraded from 6.8.3 to 6.9.0 and now I have no Docker Containers or VMs...

Please post a bug report and please include diagnostics (Tools/Diagnostics).  If you post here it very well could get lost...

Link to comment
5 minutes ago, Boomháuer said:

Awesome, just upgraded from 6.8.3 to 6.9.0 and now I have no Docker Containers or VMs...

 

Can you open up a thread with the logs attached before you restore your backup so it can be looked at when you get a moment? It sounds like your config might've pointed the appdata folder to another location (other than standard), and that config information was wiped. If that's the case, should be a simple fix of editing where libvert and appdata are stored. ZFS plugin maybe?

Link to comment
1 minute ago, BVD said:

 

Can you open up a thread with the logs attached before you restore your backup so it can be looked at when you get a moment? It sounds like your config might've pointed the appdata folder to another location (other than standard), and that config information was wiped. If that's the case, should be a simple fix of editing where libvert and appdata are stored. ZFS plugin maybe?

As far as I know I was using the standard appdata folder, unfortunately I already tried to revert back to 6.8.3 but I will post logs in a bug report.

 

Thanks.

Link to comment
5 minutes ago, kaiguy said:

Upgrade went smooth! Great job Limetech team! Now in the process of transitioning unassigned devices to pools.

 

Question -- I know there was a previous issue with SSDs and excessive writes with btrfs, so I switched all my SSDs to xfs a while back. I see that any new pool defaults to btrfs. Has the excessive writes issue been fixed? Is there any benefit to running btrfs on single SSD pools or should I stick with xfs? THANKS!

There were a number of "fixes", including using 1MiB partition alignment.  But I'd say if xfs is working for you and you're not planning on adding another device to add redundancy to your pool, then stick with xfs.

  • Thanks 1
Link to comment

Just to add some kudos for the development team - this is a MASSIVE update and a testament to the tremendous work by the development, testing and of course the community teams that have helped test this through-out the betas and the release candidates! Well done!

  • Thanks 2
Link to comment

Upgraded both servers to 6.9.0.  No issues that I have noticed so far.  Upgrade went smoothly and everything I have tested so far is working correctly.

 

Now I just have to figure out how 6.9.0 may impact iGPU and SSH related lines in my 'go' file and do things the "correct" way.

  • Thanks 1
Link to comment
2 hours ago, Boomháuer said:

Awesome, just upgraded from 6.8.3 to 6.9.0 and now I have no Docker Containers or VMs...

 

EDIT: Just went back to 6.8.3 and they are still missing... super not happy now.

Hey Boomhauer, try stopping your array and remounting the cache drive then restarting array. See if docker starts up after that.

Link to comment
4 hours ago, tjb_altf4 said:

Noticed this is coming up at end of boot process, not sure if unraid issue, or a plugin issue (maybe @ich777)

I hear about this the first time I think?

Where did you notice the '/bin/bash: line 33 [: ==: unary operator expected' what Plugins have you installed?

What process is stuck at 100%?

Link to comment

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.