Leaderboard

Popular Content

Showing content with the highest reputation on 02/10/19 in all areas

  1. More bug fixes. More refinements to webGUI, especially check out latest Community Apps plugin! Other highlights: Parity sync/Data rebuild/Check pause/resume capability. Main components in place. Pause/resume not preserved across system restarts yet however. Enhanced syslog capability. Check out Settings/Nework Services/Syslog Server. Special thanks once again to @bonienl and @Mex. Version 6.7.0-rc3 2019-02-09 Base distro: jq: version 1.6 oniguruma: version 5.9.6_p1 php: version 7.2.14 Linux kernel: version: 4.19.20 md/unraid: version 2.9.6 (support sync pause/resume) patch: PCI: Quirk Silicon Motion SM2262/SM2263 NVMe controller reset: device 0x126f/0x2263 Management: emhttp: use mkfs.btrfs defaults for metadata and SSD support emhttp: properly dismiss "Restarting services" message firmware: added BCM20702A0-0a5c-21e8.hcd added BCM20702A1-0a5c-21e8.hcd vfio-pci script: bug fixes webgui: telegram notification agent bug fixes webgui: VM page: allow long VM names webgui: Dashboard: create more space for Dokcer/VM names (3 columns) webgui: Dashboard: include links to settings webgui: Dashboard: fix color consistency webgui: Syslinux config: replace checkbox with radio button webgui: Docker page: single column for CPU/Memory load webgui: Docker: usage memory usage in advanced view webgui: Dashboard: fixed wrong display of memory size webgui: Dashboard: fix incorrect memory type webgui: Plugin manager: align icon size with rest of the GUI webgui: Plugin manager: enlarge readmore height webgui: Plugin manager: add .png option to Icon tag webgui: Plugin manager: table style update webgui: Added syslog server functionality webgui: syslog icon update webgui: Main: make disk identification mono-spaced font webgui: Added parity pause/resume button webgui: Permit configuration of parity device(s) spinup group.
    3 points
  2. Having just looked at CA for the first time in a while (my server is running fine and I don't fiddle with it much), here's what I said to Squid about all the new CA icons: I took a look at SpaceInvaderOne's video review of 6.7rc1 and I'll repeat my thoughts. The icon shapes are nice, but they're nothing but a sea of white. Again, I get that this is the latest trend in design, but it is, in my opinion a terrible one. There is considerably more cognitive load in mentally parsing the shapes when there is no color to help out. This is especially tough on those of us whose eyesight isn't quite as good as it used to be. There is a reason why modern IDEs all do syntax highlighting. This is an absolute God-send in comparison to the dark ages of working on a monochrome green or amber monitor! Just try disabling syntax highlighting in your modern IDE and see how hard that makes it - there's no good reason to go back. Again, I get that you're just following the "modern" trend, and I have tremendous appreciation for the incredible amount of work that goes into keeping the system updated with all the latest security patches and all the new features you're bringing to the table, but this is one trend I wouldn't mind missing out on. I'm sure that there will be a number of security patches in the 6.7 release, and I'd be remiss in skipping it just because of the UI design, but, based on what I've seen, I'd be tempted. And, yes, I really hate that my Android phone shows all my notification icons in white against a black background. When they allowed color there, I could tell at a glance if I had an orange text notification icon - now I have to analyze each one to see if it's the "new text message" shaped white square, among the sea of other white, essentially square, icons. </rant>
    3 points
  3. Fix common problems extended test will show it.
    2 points
  4. It will show you the first one, first on cache if there is one, then disk by disk in order.
    2 points
  5. When I woke up to ~50 emails from replies to this topic, I knew exactly what had happened, people complaining about the version again. While I remain mostly silent with the exception of troubleshooting in these threads, I wanted to drop in and say thanks again before I turn off the "notify me of replies" button this time The LS.IO team makes the vast majority of containers myself, close friends, and surely countless others who are on unRAID use on a daily basis, day in and day out. I don't understand the insane need for the latest version of UniFi all the damn time. You'd think these people would just get a cloud controller and call it a day. I'm happy to have one server here, running containers to control everything I need, UniFi included, even if it is three days out of date. :gasp: Again, thanks @CHBMB to you and the rest of the LSIO team for continuing to put up with the few entitled users here, you make unRAID and the docker community a better place.
    2 points
  6. It’s time to back off and thank them for what they do for us!!!! This is starting to get ridiculous if don’t like the way things are right now roll your own…. CHBMB I just wanted to say thanks for doing your best at keeping this up to date. Your efforts are greatly applicated.
    2 points
  7. I agree with you. I said essentially the same in my rant in the -rc2 section.
    1 point
  8. I'll try to resist 'peer' pressure, if it comes to that 🤣
    1 point
  9. I don't post much but I have to agree its harder to discern what icon your looking at, example would be unbalance or speedtest it just draws you to it when navigating both by its color and shape/image
    1 point
  10. lol. Once 6.7 started down the pipe I also complained about that. Personally, I didn't see how a modern UI is nothing but a retro look to monochrome / lowres monitors. That being said, I'm also the first to admit that I have no idea what a UI should actually look like. Personally, since my primary server is running 6.7 and the backup is running 6.6, I find the 6.6 one looks absolutely terrible compared to the 6.7. (And controlR / cachedirs looks completely out of place) They're only blue because you're not running 6.7 After you upgrade, they'll be white like everything else. Realistically though, the proper place for these kind of complaints is in the 6.7 thread or the feature requests thread. As you've said, I'm simply following the herd / conforming to the design of the UI as a whole.
    1 point
  11. You will have two files. To my knowledge, Unraid will use the first file found (on disk1 i guess) when you have two of the same on several disks.
    1 point
  12. 1 point
  13. Last we were told is 4.20 is aim with possible 5.0 depending on when it is finalized.
    1 point
  14. Right, I'm going to raise those element's brightness a bit.
    1 point
  15. Sorry, I realise now you actually had posted the relevant info originally. I missed it. So what is the issue? You can't browse from Plex (Docker container) - Host (Unraid) - SMb Share (Different Machine) Probably a limitation of the SMB layer I would imagine. Not something I've ever tried, but I'd be surprised if nobody else has. The --privileged flag gives all capabilities to the container, and it also lifts all the limitations enforced by the device cgroup controller. In other words, the container can then do almost everything that the host can do.
    1 point
  16. In Unraid 6.7 we do not suppress PHP warnings anymore. Please follow the advice of @johnnie.black and delete/recreate your docker image. You will need to re-install your containers, if you have CA installed, you can use its restore function to quickly get back all your containers.
    1 point
  17. https://forums.unraid.net/topic/57181-real-docker-faq/?do=findComment&amp;comment=564309
    1 point
  18. You're literally missing the point. It just says we maintain images. Nothing about versions. Even if we maintain a working image that contains a version 5 years old, it satisfies the above criteria as long as it still works. Let me make one thing clear. Lsio is a group of volunteers who got invited to become team members based on their contributions or commitment (with the exception of the original founders). We are not elected public officials. We owe nothing to you. We do not serve at your pleasure. I serve at my pleasure. I do what I want. With that said, we are nice people and we try to give back to the community. Do not confuse our good will with any false sense of obligation. As an FYI, the constant badgering of unify users on multiple forums, discord, Reddit, GitHub and private messages every time there is a new version pisses me off so much that I have 0 interest in touching the unifi repo for any reason even though I myself am a user of that image.
    1 point
  19. Look at the forum settings, make sure signatures are switched on and you'll see a link in my sig to Docker Run Command. That's what we need to see.
    1 point
  20. Would be nice to see this at the bottom like it is on the desktop. As it stands now, you have to scroll back to the top, click the hamburger, and some other stuff. Its a new year and im trying to limit my mindless scrolling, and going back to the top is an easy way to cut down on that. how about it???
    1 point
  21. "We make and maintain container images for the community." Where does that say we promise updates immediately? If you're running critical network infrastructure that demands 0 day patching, then you should be looking at maintaining your own software or contracting out to someone who will do it for you. Or get involved and help maintain it, rather than rely on other people volunteering their free time to do it for you.
    1 point
  22. Ya I fully understand that and have seen it before PLEASE don’t stop because of a few that have no patience. Thanks again…..👍
    1 point
  23. Yes, and that's what I'm referring to. It's not stuck on 5.9.x but you all need to start bearing in mind that we don't live to purely exist every repository as soon as software is updated. EVERYTHING we do is in our limited spare time, we all have families, jobs and other commitments. For some reason Unifi always generates a hullaballoo everytime they update and we don't immediately drop everything to update a container. If your wifi is working, what's the rush? Of course if anyone wants to volunteer their free time to help out and maintain stuff then by all means hop into our Discord and volunteer your services.
    1 point
  24. Perhaps 24 is more flexible? 6 x 4 = 24 8 x 3 = 24 12 x 2 = 24
    1 point
  25. Did anyone notice a drastic slowdown starting with RC2 when moving files? Sometimes i cant even access radarr, because it hangs. My Windows 10 VM says SSD Usage 100% and reaction time 1200seconds or something liek that..^^
    1 point
  26. There's a link in the plugin to the Nvidia site, select your driver there and it will tell you what cards are supported. Transcoding ability does vary between cards though, so you will need to do some research. Sent from my Mi A1 using Tapatalk
    1 point
  27. I've partially finished updating the logging. This may not cut down on log sizes yet, but now that I've done this first part I can implement a log rotation so logging is only kept for X amount of days.
    1 point
  28. It sounds like you should be using the one with MariaDB. Do you already have a separate database set up?
    1 point
  29. 1 point
  30. Correct, although iirc you only replace bzimage for your needs. So you may get lucky if you continue to do the same.
    1 point
  31. Long time user of unraid but just registered today to say thanks for this incredible plugin!! And new update looks amazing!
    1 point
  32. didn't see it in the post, so let me just recommend getting hardware acceleration using Intel QSV going, decreased the transcoding time by factors of 10+ for me.
    1 point
  33. Hi Markus! SFTP is creating the users in the container from the users.conf file on the first run, but it does not appear to handle when users are added to the file and the docker is restarted. Is it possible to have the container add additional users that may be added to the users.conf file after the first run? It would also be pretty sweet if the startup script could also update the user passwords using the users.conf file on startup, making it possible to manage users without using the containers shell.
    1 point
  34. Check out this awesome introduction video produced by @SpaceInvaderOne:
    1 point
  35. Attached. It looked like it stalled during downloading the docker, so i may just need to redownload it. Edit: I delete the config folder and started the container again. So far its importing as expected.
    1 point