jumperalex

Members
  • Posts

    2000
  • Joined

  • Last visited

Posts posted by jumperalex

  1. Honestly I can't recommend anything other than a ubiquity unifi security gateway or edgerouter (pick the model right for you, I have a Lite), plus the AP of your choice (I have a nanoHD) Or a Dream Machine if you want an all in one solution.

    Sent from my SM-P205 using Tapatalk

  2. That is sad and I understand your reasoning. And nothing I say below should be read as a call to change your current plan.

     

    That said, I disagree that LT has made it self tuning. Default settings for even the one main tunable, md_num_stripes, makes a difference for my 7 disk array. Setting it to 5120 improved my parity by 10% from default. Not sure if this is the best speed:memory option, but i also guess I don't need a full script to test out a few options. But for sure default is slower than tweaked. FWIW, I'm getting same speed in 6.8 tweaked as 6.7 tweaked which was the same speed as 6.6 tweaked

     

    nr_requests I'm not so sure but I did increase mine from default to 256. This is where maybe a script might help to see if there is an interaction. Though my research of what nr_requests does leads me to believe there probably isn't any covariance.

     

    In any case, thank you for all your time and effort. Even if it ends up being the stuff of legend, your contribution to the community really is greatly appreciated.

     

    Thank You Pauven!

  3. Yeah that's where I looked and the only two files that I see are screen.conf and settings.conf

     

    settings only has this

     

    #
    # MakeMKV settings file, written by MakeMKV v1.14.5 linux(x64-release)
    #
    
    app_DataDir = "/config/data"
    app_DestinationDir = "/output"
    app_DestinationType = "3"
    app_ExpertMode = "1"
    app_Java = ""
    app_UpdateEnable = "0"
    app_ccextractor = "/usr/bin/ccextractor"
    sdf_Stop = ""
    

     

  4. Hmmm I just removed to include deleting the image; reloaded; and still say expired key. When I paste the current key found on the author's beta page it accepts it, but requires a restart so the key doesn't survive.

  5. [looks around confused] did I say something I didn't mean to? I wasn't asking anyone to change the way the container runs. I was asking where the latest "stable" release was as described by Unifi. Then saarg explained to me where this container sources (read: the repo) and I acknowledged I then understood why the container wasn't grabbing the latest (read: unifi hadn't posted to the repo yet).

     

    As for my reply to your post about it not being wise pushing stable to a production environment ... I'm right that it's the user's choice and their responsibility to choose what tag to use because this container pulls from the repo and what's in the repo is what it gets; at least according to saarg. So "the second it comes out" on the repos is when LSIO will be pushing it unless they make a decision to change their source.

     

    I mean seriously man, I wasn't trying to stir the pot or poke anyone in the eye.

  6. 21 hours ago, jonathanm said:

    Which may or may not mean it's a good idea to push that version to a production environment. "Stable" unifi software has caused major headaches in the past, I'd much rather wait until it's been running on someone else's system for a while before I trust my multiple sites to it. If wifi goes down, it's a big deal. I'd rather not deal with angry users.

    Fair. But that's us users decision to make. I think they have a tag for that ... LTS?

     

    But yeah, can't deny what you're saying in general.

  7. 2 hours ago, saarg said:

    Short answer is: Unifi is cluster f... when it comes to releases.

    5.10.26 is the latest stable in their deb repo and all others are stable candidates and whatever they call it.

    This is the url we hit to get the latest version: http://dl-origin.ubnt.com/unifi/debian/dists/stable/ubiquiti/binary-amd64/Packages

    5.11.39 has been deemed stable according to this https://community.ui.com/releases/UniFi-Network-Controller-5-11-39/6ab8ef1a-376f-41e6-85b2-ceec098b8462

     

    Sadly, as you're surely aware, they still haven't pushed to the repos. [sigh]

  8. Anyone played around with it?

     

    https://lifehacker.com/why-you-should-use-windows-defenders-ransomware-prevent-1837311176

     

    I know this isn't explicitly UNRAID related but we spend a fair bit of time talking about protecting our servers and thought this might be worth a discussion.


    After I turned the feature on I went to add more locations and noticed BOOM my linked \\tower shares showed up by default. To be sure, these are the locations that are part of my mapped Windows Libraries such as Music, Videos, etc. Notice something missing? No of course you woulnd't ;-) ... my Movies share isn't there because it isn't part of a Windows Library.

    image.thumb.png.7986fb4cd966a42683205c62f38e7e4b.png

    It was easy enough to the missing \\tower\movies share.

    image.png.35603858dcd3fd7259158ee411919e27.png

    While typing this post I got my first alert

    image.png.a0f0f6083b81bb8373a7150ef7b99d8a.png

    PickerHost.exe seems harmless enough from searching. Though I have no idea what it is doing in My Data Sources. A little research showed PickerHost.exe to be harmless and part of windows so I used the Action|Allow on Device option.

     

    In any case, I thought some of you might be interested and I'm surprised at least a quick search didn't find any discussion. But please feel free to post the link(s) if there has been.

     

    I'm still not ready to make my SMB shares read/write since I so rarely even need to write to them externally. When I do I just change their status for a moment and then revert back. Afterall, my PC isn't the only computer / device on the network but I'll be adding this to the other windows machine soon enough and defense in depth is always the right answer.

     

  9. FWIW, I have a marvell controller (HighPoint Rocket 620 2-port) and upgrade went fine.

     

    IOMMU group 18:	[1b4b:9120] 05:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9120 SATA 6Gb/s Controller (rev 12)
    	[1b4b:91a4] 05:00.1 IDE interface: Marvell Technology Group Ltd. 88SE912x IDE Controller (rev 12)

     

  10. See sig for context ...

     

    For unraid memory speed has no real impact. What matters is PCIe bandwidth and even a touch of OC there isn't going to be worth it especially if it has any impact on reliability. Afterall, that's why you're going ECC isn't it?

     

    8GB is fine unless you're going REALLY crazy with running dockers and VMs. I ran with 8GB on a single stick for a long time with no problems at all; but I was also only streaming two plex streams at most and usually direct not transcoded. I only upgraded to 16GB because DDR3 is getting pricey so I thought I'd buy for the future before it got too expensive.

     

    I have the ROG STRIX B450 for my desktop. Love it. ECC compatible but I didn't choose to go that route for a desktop. I'd have no concerns using it for unraid; in fact I choose it both for current use and as a hand-me-down future-proof for unraid knowing I'd want ECC DDR4.

     

    As for which ram to choose [shrug] I've had good luck so far with Kingston (again ... see sig). Looking at your link I wouldn't just go for the cheapest. This is for the long haul man. Go out drinking one less night :)

  11. 2 minutes ago, aptalca said:

    Most of our images don't update apps inside the container so not updating the image for a month is ok. But for apps that update inside the container like this plexpass version, you should make sure you are always on the latest image, otherwise it may break (like it did this time but could have been a lot worse)

    haha fair play. I've never had any other "worse" problems. But yeah now I know. I wonder if that might be something worth adding as a caution actually in the docker overview box? "Note: This Docker image is more dependent on an up-to-date image than you might be used to. Any application problems may be solved by a docker update" or something like that ... Just saying.

     

    And saying Thank You!

  12. 1 hour ago, aptalca said:

    Judging by that log, you need to update your plex image/container

    I update every month on schedule. Forcing a docker update now ... yup, there are updates ... done ... and there I can now see it grabbing the new plexpass version in the log using the same url that I said I found on plex.tv myself.

     

    That is rather annoying 😛 But now I know.

     

    Thanks.

  13. On 1/24/2019 at 7:45 AM, aptalca said:

    No, what I mean is, the docker image is only able to pull either the stable (public) releases or plexpass versions.

     

    Go to the Plex website, hit download and you'll see a toggle switch for plexpass. With it on and off, you'll see two versions listed. Those are the latest versions this image supports. Not ones that are posted on the forums.

    Resurrecting this a bit ... so based on what you said I do indeed see that version 1.15.0.659 is available as a plexpass verison for me. But my log says it still isn't available.

    Atempting to upgrade to: 1.15.0.659-xxx
    https://downloads.plex.tv/plex-media-server/1.15.0.659-xxx/plexmediaserver_1.15.0.659-xxx_amd64.deb:
    2019-02-16 10:09:37 ERROR 404: Not Found.
    
    
    
    ########################################################
    # Upgrade attempt failed, this could be because either #
    # plex update site is down, local network issues, or #
    # you were trying to get a version that simply doesn't #
    # exist, check over the VERSION variable thoroughly & #
    # correct it or try again later. #
    ########################################################

    I've been running for quite some time and updates have occurred in the past. I'm on 1.14.1.5488 right now. I recall a while back seeing an update issue but I ignored it at the time and it "went away" some time later when I next looked. I chalked it up to resolved connection issues, but now I'm thinking it "went away" because the plexpass version moved to stable and the download succeeded.

     

    I do see mention on the git readme about "IMPORTANT NOTE:- YOU CANNOT UPDATE TO A PLEXPASS ONLY (BETA) VERSION IF YOU ARE NOT LOGGED IN WITH A PLEXPASS ACCOUNT" which makes me ask, logged in where? inside my plex docker instance? yup, done that. In a parameter of the docker set-up? I don't see where to do that. On my desktop I can download the 1.15 verison, and did as a test. But the link for THAT is "https://downloads.plex.tv/plex-media-server-new/1.15.0.659-xxx/debian/plexmediaserver_1.15.0.659-xxx_amd64.deb which is different than where the dockers seems to be attempting to pull from. While logged into the plex.tv website the docker link doesn't work from my browser either. But maybe the deb version is what I should be testing against?

     

    Any help is appreciated and by all means tell me what other info I might need to provide.