Jump to content

jumperalex

Members
  • Content Count

    1990
  • Joined

  • Last visited

Community Reputation

6 Neutral

1 Follower

About jumperalex

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

1230 profile views
  1. [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.
  2. 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.
  3. 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]
  4. "posted" as in to the LIO servers or Ubiquiti's? They are already at Ubiquiti and I'm using latest.
  5. soooo what needs to be done to get on the 5.11.39 version?
  6. 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. It was easy enough to the missing \\tower\movies share. While typing this post I got my first alert 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.
  7. uggg when and why did this happen How hard / is it possible to copy my config over to the new LIO docker? Really not looking to redo all my clients 😮
  8. 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)
  9. Fixed it for me too. Anyone know the issue and if it is something for linuxserver to fix or further upstream?
  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. sadly no. I really haven't thought about this issue since DarkHorse's post.
  12. 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!
  13. 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.
  14. 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.