Jump to content
limetech

Unraid OS version 6.6.0 available

269 posts in this topic Last Reply

Recommended Posts

6 minutes ago, ijuarez said:

docker image is 100GB (why not) 

Because it can mask problems you have with misconfigured dockers growing uncontrollably.

Share this post


Link to post
Just now, trurl said:

Because it can mask problems you have with misconfigured dockers growing uncontrollably.

fair enough, 20GB a good enough?

Share this post


Link to post
1 hour ago, jamesyt666 said:


I just downgraded, Enabled ACS overrride and restarted and now all my devices are split apart again. It seems a bit odd that the new version does not work the same way...

 

Well this may take a while to analyze.  ACS override is accomplished using a "patch" to the kernel which, we've been told, will never be accepted upstream.  We've had to fix the patch a couple times now with certain kernel releases.  The reason it will not be accepted upstream is because it's a theoretical security hole.  The guys running the cloud servers would have a big security risk with this patch in place.  The real solution is to use hardware that properly defines IOMMU groups.

Share this post


Link to post

upgraded last night from 6.5.3. fix common problems notified me of an unclean shutdown but there was no automatic started parity check. Acknowledged and re-booted. same thing. Manually started a "no correct" parity check, completed this morning without errors. shutdown diagnostics from flash drive log folder attached.

tower-diagnostics-20180920-2057.zip

Share this post


Link to post
upgraded last night from 6.5.3. fix common problems notified me of an unclean shutdown but there was no automatic started parity check. Acknowledged and re-booted. same thing. Manually started a "no correct" parity check, completed this morning without errors. shutdown diagnostics from flash drive log folder attached.
tower-diagnostics-20180920-2057.zip
FCP and unRaid determine unclean shutdowns slightly different. While both may be "unclean", if no parity check started, then none is needed

Sent from my LG-D852 using Tapatalk

Share this post


Link to post
27 minutes ago, Squid said:

FCP and unRaid determine unclean shutdowns slightly different. While both may be "unclean", if no parity check started, then none is needed

Sent from my LG-D852 using Tapatalk
 

Thanks Squid, any idea what "unclean shutdown" it is detecting??

Share this post


Link to post
4 minutes ago, wirenut said:

Thanks Squid, any idea what "unclean shutdown" it is detecting??

I delete a particular file on the flash drive during shutdown.  If the file still exists on the next boot, I assume its an unclean shutdown.

Share this post


Link to post
1 hour ago, Squid said:

I delete a particular file on the flash drive during shutdown.  If the file still exists on the next boot, I assume its an unclean shutdown.

OK. So for my piece of mind and understanding, nothing serious to worry about??

Share this post


Link to post
2 minutes ago, Transmobius said:

Replaced a drive and the "Unused" column isn't displaying correctly in Main.  See attached image, specifically Disk 10

Screenshot from 2018-09-21 13-10-36.jpg

What do you think it should be showing?    It seems to be showing a drive that is basically empty.   If you replaced the drive did you at any point select the ‘Format’ option - if so that would explain the disk being empty.

Share this post


Link to post

I updated to 6.6.0 yesterday.  No issues thus far.  Visually, I like the continuity with recent Web upgrade.  One thing that is very helpful is how the buttons are red/orange outlines with white backgrounds, but change to the gradated red/orange upon hover.  Slick!  Oh, and native cpu pinning is super helpful!  Basically, thanks!

Edited by DoItMyselfToo

Share this post


Link to post
11 minutes ago, itimpi said:

What do you think it should be showing?    It seems to be showing a drive that is basically empty.   If you replaced the drive did you at any point select the ‘Format’ option - if so that would explain the disk being empty. 

The drive is empty, freshly formatted.  The "Used" should say "0 GB" and not "8.80 GB".  Sorry for the typo, in OP I said "Unused".

 

Also, not positive that this is specific to the new v6.6.0, I replaced the drive and then upgraded the OS.  Did not notice the odd "Used" on the prior version - but it may have read that way too.

Edited by Transmobius
added upgrade info sequence

Share this post


Link to post

The "used" space includes space taken by the file system (XFS). An "empty" 8 TB disk uses already 8 ~ 9 GB of file system space, which is what you see.

 

Share this post


Link to post
Just now, bonienl said:

The "used" space includes space taken by the file system (XFS). An "empty" 8 TB disk uses already 8 ~ 9 GB of file system space, which is what you see.

 

And the 51.3 GB used on the 8 GB drive pictured above?

Share this post


Link to post
3 minutes ago, Transmobius said:

And the 51.3 GB used on the 8 GB drive pictured above?

Files are copied to the disk.

Share this post


Link to post
3 minutes ago, Transmobius said:

51.3GB copied to an 8GB?

Your disk is not 8 GB but 8 TB (1000 times bigger)

Share this post


Link to post
5 hours ago, ijuarez said:

fair enough, 20GB a good enough?

 

I'm sitting under 3GB used for the past few years, so 20GB seems way too large to me.

Share this post


Link to post
56 minutes ago, Transmobius said:

The drive is empty, freshly formatted.  The "Used" should say "0 GB" and not "8.80 GB". 

 

Incorrect. Filesystem has overhead.

Share this post


Link to post
32 minutes ago, BRiT said:

 

Incorrect. Filesystem has overhead.

Yep. Sorry absolute brain fart. Next time I'll sleep before doing any system updates and upgrades.

Share this post


Link to post
1 hour ago, BRiT said:

 

I'm sitting under 3GB used for the past few years, so 20GB seems way too large to me.

Similar to me. My Dashboard show 14% of 20GB (=2.8GB). But I only run 5 dockers.

Share this post


Link to post
On 9/20/2018 at 10:48 PM, bonienl said:

Do you mean "br0" or did you define your own custom network "bridge.0" ?

The newer version of Docker included in Unraid 6.6 has changes in the networking part. We adopted so networks generated by Unraid continue to work as before, but there is no guarantee for custom networks made by the user.

Custom: br0
Needed for Unifi, & PiHole.

 

It also seemed to kill Splunk, which is just a Bridge connection.

 

So how does one create a new External IP for a docker with 6.6?

Edited by BCinBC
Splunk broke too

Share this post


Link to post

Just upgraded my main rig from 6.5.3 to 6.6.0, and have not encountered any problems.

 

I'm running an AMD Threadripper 1950X on an ASRock X399 Taichi motherboard.  I have Plex docker, and a couple of VMs (Linux and Windows) running, and Windows has a GPU pass-through.  I didn't seriously eyeball the IOMMU groups, but what I had before still seems to be working fine.  I was/am using the ACS Override, though.

Share this post


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.