Jump to content

Titan84

Members
  • Posts

    79
  • Joined

  • Last visited

Report Comments posted by Titan84

  1. 5 minutes ago, bonienl said:

    The plugin is still useful for shares which have not set a minimum free space value. AKA the user has never set anything explicitely for the current shares.

     

    New shares which get an automatic value assigned in 6.12 are not touched by the plugin.

     

    Thanks for clarifying @bonienl

    Last question 🙂 the plugin has the ability to set a schedule to re-check the shares every so often to verify that the free space is still accurate. Does 6.12 do something similar?

  2. 43 minutes ago, bonienl said:

    This version also does automatic calculation of the minimum free space setting for any new share.

    Existing shares can be easily updated by forcing a change in the settings (e.g. enter a space in the min. free space field) and apply.

     

    The user can still set a designated value and overruling the automatic calculation.

    Values can be entered as absolute numbers with an optional suffix or as a percentage value.

     

    Does this mean that we no longer need the Dynamix Share Floor plugin?

  3. I tried deleting the Docker.img file and re-creating it but that didnt help.

    I then downgraded back to 6.11.5 but i still had the issue only when the Docker service was enabled. I then changed the IP assignment from Static to Auto on Unraid and then on the Unifi controller side i set the server to have the same static IP address and this seems to have fixed the issue.

    I never had this issue before upgrading to 6.12.0-RC3 so im not sure if something strange happened on the network side of things during the upgrade.

     

    I do have another Unraid server on the same network and setup the same, still on 6.11.5 and never been updated to 6.12.0-RC3 and this has never had any issues.

     

    Anyway, solution seems to be changing static to Auto for the IP.

     

    I will try this again when RC4 comes out.

  4. Upgraded my i9-12900K system to this version yesterday and so far no issues to report and all is running smoothly.

    As CS01-HS reported i also noticed the following in the logs...

     

    kernel: Attempt to set a LOCK_MAND lock via flock(2). This support has been removed and the request ignored.

     

    I see someone else has uploaded their diags already but if you need another set please let me know. If this post gets any bigger ill create a separate bug report.

     

  5. 5 hours ago, itimpi said:

    I would expect any 6.11 release to have significant new functionality.    If it was only a kernel upgrade I would expect it to be a point release within the 6.10 series.

    Fair enough, a pointed release would be fine using the 6.10.x lable.

     

    3 hours ago, flyize said:

    I believe that @limetech has already stated that 6.11 will be based on 5.17.

    They said that it will be based on the latest Kernel version at the time of releasing 6.11 so id say either 5.18.x or 5.19.

     

    3 hours ago, flyize said:

    Otherwise, you can try running 5.18 by using @thor2002ro's custom kernel. However, I can tell you that 5.18 doesn't currently fix it.

    Yeah, I saw your instructions on how to do it so its an option. Iv seen mixed results though with some people saying that it's working so I dont really know tbh. 

  6. Since the new Kernel 5.18.x will likely solve this issue, what are the chances that @limetech could release say a version 6.11-RC1 for us that has the latest Kernel. In this RC1 version literally the only changes from 6.10.2 would be the new Kernal and nothing else.

    I'm aware that the team have a lot going on right now with the NIC issue and I'm not sure what's all involved with combining unraid with the new Kernel so this might be totally out of the question but I thought id ask ;-)

    I'm in the same boat as a lot of other people with a 12900K but don't want to use a custom Kernel mod if I can help it as I don't want to mess things up 🙂

  7. @limetech Just wondering, would it make sense if you could please update the default setting to 30 seconds in your next Unraid release and then if users wanted a higher value then they can increase the value. In my case i wasn't aware of the default polling interval being so high and i would guess that many others dont know about this either. I have just gone ahead and changed this to 30 sec now.

  8. 55 minutes ago, ich777 said:

    It is maybe possible that 5.18 has became stable and that 6.11 will have Kernel 5.18+

    Watching the 5.18 RC releases, if it continues as smooth as it has been they say we are looking at a release on the 22nd May so hopefully it can make it into 6.11 RC series. Im guessing (looking at past Unraid releases) that 6.11 RC1 isn't going to be released in May so perhaps there is still a chance 🙂

  9. 21 hours ago, limetech said:

    From your link does not look like kernel issue.  If you are following this, please alert us if they come up with a solution that requires us to change something.  Best way to alert would be to create a separate Bug Report and then update if the situation changes.  thx

    @limetech The Plex devs have come back this morning and said that the fix to the Alder Lake iGPU for Plex transcodes will be part of the 5.18 Kernal release.

    With the 5.18 kernal being released end of May, im hoping that you might be able to include 5.18 as part of your 6.11 RC1 release ;-)

     

    https://forums.plex.tv/t/plex-media-server-on-ubuntu-21-10-with-intel-12th-gen-alder-lake/768123/12

     

    • Like 2
×
×
  • Create New...