Leaderboard

Popular Content

Showing content with the highest reputation on 11/23/20 in all areas

  1. I've have been following this and the other thread with very mixed feelings and I feel the community is unjustly hard towards @limetech. Sure some things could have been handled better, yet I keep the feelings that the bigger injustice is not actually committed by him. In order to understand things better and to see things from a different perspective I personally like to make analogies. Sometimes it gives different insights into situations. And I cam up with the following for this one: We have 3 parties here, The parent (@limetech), the uncle (@CHBMB and the like) and the kid (the community). Now the situation is that the kid is asking the parent for this shiny new toy, but for whatever reason the parent is not buying the kid the toy. Maybe it is to expensive, maybe he is waiting for the birthday, whatever.. However, the uncle who hears the kid decided to get the kid this new toy, because he loved the kid and wants to please the kid. Fast forward and the parents sees that the kid really loved the toy but unfortunately the toy has some sharp edges and the parent is afraid the kid might hurt himself hence the parent decided to order a better and safer version of the toy. However, when the parent tells the kid it ordered this new toy the uncle hears the parent and flies into a rage because the parent did not tell the uncle that he/she was going to buy the new toy and the uncle thinks the parents is ungrateful because he/she did not even thank the uncle. In his rage therefore the uncle takes the toy away from the kid even before the new toy arrived (it is after all still in beta). Not only that but takes away the other toys he got the kid as well and says he is never going to give the kid any more toys. All this to punish the parent. Now with this analogy, ask yourself. Is the reaction of @CHBMB (the uncle) proportionate and justified? Does a parent (@limetech) need to inform the uncle of these kind of things? Sure it is nice, but is it really needed? Do you think it is right for the uncle to punish the kid? Should the parent even be grateful that the uncle presents the kid a toy with sharp edges (I know I wouldn't). The only one the uncle should expect thanks from i.m.o is the kid. The community is and was grateful. Yet @CHBMB is the one who decided to punish the community and take away their toy because of his hurt feelings. Yet the only one who gets shit is @limetech. If I where him I would be more than a little pissed and disappointment and I think it shows in his messages. Please read my analogy again and ask yourself who in the story did anything to hurt the kid? The parent or the uncle? And please also think about the fact that we have no way of knowing if @limetech was not going to thanks @CHBMB for the work in an official release note, which this wasn't. Now I do think the parent should have said something to the uncle. And I also am a bit disappointment to learn that even though UnRaid builds heavy on the community there is no special channel in place to facilitate communication with reliable community develops. Considering how well the development of both UnRaid and the community add-ons go together I kind of assumes something was already in place. However it seems this is something that is considered and worked on now. But in everything that happened, this simple miscommunication seems far the lesser evil here. And I do think it might be good that the community asks itself again who really is to blame for taking away it's shining toy with sharp edges and if it is reasonable to have this reaction. But that's just my 2 cents.
    9 points
  2. We do have a special forum board called "The Lab" which is available to Community Dev's and Moderators where we can and do talk about development, though we (Lime Tech, Inc) need to do a better job at posting roadmaps in there (working on it). There is another board called "The Bar" where Moderators can hang out and discuss forum issues. Finally @SpencerJ servers role of "Community Manager", though in this particular case I thought it best to address the Community directly myself.
    4 points
  3. This is a wonderful post, written with insight, sensitivity and purpose. Thank you for taking the time to write it. I read it a few times, I hope others do the same.
    4 points
  4. @kim_sv @vw-kombi see here:- https://github.com/binhex/documentation/blob/master/docker/faq/sonarr.md
    3 points
  5. I'll caveat this post by saying that I've had a few interactions with @limetech over the last 10+ years, and he's always been kind, gracious and understanding. The kind of guy you would enjoy going for a drink with and shooting the shit. That said, @limetech you've now made two missteps in your posts in the last week. It may be a consideration to either a) have a third party review your posts prior to posting (at least the non-technical ones) or b) get a community manager. This isn't a criticism, but rather an obervation. I sincerely believe you when you say that you meant no disrespect with your posts, but something is getting lost in translation. Your expertise is creating this awesome OS. Get someone whose expertise is being the conduit for this awesome community. ~Spritz
    3 points
  6. All of us at Lime Technology are very excited to announce Larry Meaney as a new full-time hire. Larry has joined us as a Senior Developer/Project Lead. Here's a little more about Larry: Please help us give Larry aka @ljm42 a warm welcome!
    2 points
  7. Next release of 6.9 will be on Linux 5.9 kernel, hopefully that will be it before we can go to 'stable' (because Linux 5.8 kernel was recently marked EOL).
    2 points
  8. Before anyone else beats me to it: Soon™
    2 points
  9. Thanks @binhex for the release of v3
    2 points
  10. doing the same for radarr makes me more nervous, i would expect it to be more 'beta' than production ready, and i can imagine there would be a lot more support caused by this which i would not be able to respond to (time constraints), so for now im going to say no.
    2 points
  11. I'm not ephigenie, but I liked the idea, so I'll give my two cents on it, for what it's worth: Maybe something like a broad strokes roadmap. Nothing too concrete, but even a post with headings like: Features being worked on for the next major/minor release (multiple cache pools) Bugs being squashed for the next major/minor release (SSD write amplification) Future possibilities currently under investigation (ZFS) You could make the forum visible to community developers only. Or if you're feeling particularly transparent, forum members with enough posts that they've at least been semi-active, and around for a while. The understanding would be that anything mentioned is subject to change or reprioritisation, and that obviously certain things can't be talked about for market/competitive reasons or whatever. (or just because you don't like spilling all the beans on shiny new things) This would allow you to gauge community interest (at least, the portion of the community active on the forums) around given features which might factor into prioritization. As well, it gives us members a peak at the direction unRAID is heading, and an appreciation for why so-and-so wasn't added to the latest patch, or why such-and-such a bug is still around.
    2 points
  12. This post represents my own personal musings and opinion. This thread (and the broader situation) interests me on a number of levels. We (Royal we) bang on (quite rightly) about our community and how supportive, inclusive, helpful and respectful it is. Values really that any organisation in the world would be lucky for its members to behave consistent with. Saying that, this situation has shown that there is an undercurrent of what I can only call bitterness and to some extent entitlement in some community members. I don’t feel that this is across the board by any means. However, for some, there seems to be a propensity to believe the worst of every (almost like we are waiting to jump on any poorly, Ill-considered or rushed post) word posted by default rather than the positive - which given how together we are supposed to be is very surprising. There could be any number of reasons for this, whether it be the whole keyboard warrior thing, immaturity, mixture of ages of people talking to each other I just don’t know. I think we also have to acknowledge that we are all living in unprecedented times. We are very geographically spread and some are copping it harder than others for sure but we are all in a very in normal place. I have also observed that some (whether that be due to their contribution to this forum or their development work etc.) individuals appear to think that they should be subject to a treatment different to others. I always felt that when doing something in the open source / community space the only reasonable expectation was that there was appreciation from the community for that work and that was enough. It’s volunteer work that plays second fiddle to real life (a fact that many are rightly quick to throw out when the demands of the community get to high). Irrespective of how much those developments have added value to the core product I don’t think those expectations could or should change. Saying that, the community includes the company too and those expectations of appreciation for work done (especially where commercial gain is attained from that work) carries to them too. The thing that surprised me the most though (and again this could be due to the reasons above - or others) is how quick some have been to react negatively (or even just walk) but how slow some have been to react in a more positive way. Perhaps that’s human nature. As I write this I am drawing to a conclusion that we as a community perhaps need to manage our own expectations of what is reasonably expected as a community, developer or company member. This might help (or it might not) help situations like this moving forward.
    2 points
  13. You're completely missing the point. We're glad that you integrated it. We're unhappy that our efforts and calls for help were largely ignored over the years. You never even reached out to the folks who maintained it for years. Then you have the gall to say you did it to discourage "unofficial" builds as if it was a bad thing that they provided it for years. Yeah, I'm out, too. Not a fan of a one way street.
    2 points
  14. @Tom - you and the team have worked hard and we all appreciate it! but the issue is Respect and Communication (which sounds like there was none given). THAT is a punch in the face! Would you want to work that way for someone/something?
    2 points
  15. Yes Tom, that's how I viewed it when we developed the Nvidia stuff originally, it was improving the product. The thread has been running since February 2019, it's a big niche. 99 pages and 2468 posts.
    2 points
  16. This is the support thread for multiple Plugins like: AMD Vendor Reset Plugin Coral TPU Driver Plugin hpsahba Driver Plugin Please always include for which plugin that you need help also the Diagnostics from your server and a screenshots from your container template if your issue is related to a container. If you like my work, please consider making a donation
    1 point
  17. Having a plain webhook notifier would be nice, one that can be very customised (preferably being able to create a json payload). A plain webhook method allows a user to use pretty much their push notification service of choice. This may, or may not be a tangent of my wish to send notifications to discord without using the "slack hack", as expressed on the 2020 poll
    1 point
  18. Those following the 6.9-beta releases have been witness to an unfolding schism, entirely of my own making, between myself and certain key Community Developers. To wit: in the last release, I built in some functionality that supplants a feature provided by, and long supported with a great deal of effort by @CHBMB with assistance from @bass_rock and probably others. Not only did I release this functionality without acknowledging those developers previous contributions, I didn't even give them notification such functionality was forthcoming. To top it off, I worked with another talented developer who assisted with integration of this feature into Unraid OS, but who was not involved in the original functionality spearheaded by @CHBMB. Right, this was pretty egregious and unthinking of me to do this and for that I deeply apologize for the offense. The developers involved may or may not accept my apology, but in either case, I hope they believe me when I say this offense was unintentional on my part. I was excited to finally get a feature built into the core product with what I thought was a fairly eloquent solution. A classic case of leaping before looking. I have always said that the true utility and value of Unraid OS lies with our great Community. We have tried very hard over the years to keep this a friendly and helpful place where users of all technical ability can get help and add value to the product. There are many other places on the Internet where people can argue and fight and get belittled, we've always wanted our Community to be different. To the extent that I myself have betrayed this basic tenant of the Community, again, I apologize and commit to making every effort to ensure our Developers are kept in the loop regarding the future technical direction of Unraid OS. sincerely, Tom Mortensen, aka @limetech
    1 point
  19. Nope, it was just a screenshot of the Dashboard which doesn't have S/N info or any other identifying characteristics. Thankfully I am back up and running - I decided to add the 2nd parity and it's now doing its parity check on 2. All is functional except for a few minor changes I made after the last backup. Thanks again.
    1 point
  20. This is the way it is designed to work, and some people depend on it working that way. No and Only shares are ignored by mover.
    1 point
  21. @altorn_achm I have been refining my setup to include auto updating of mods. I will write a guide and reupload the xml files as soon as i can.
    1 point
  22. My newbitude is showing through here. We're not just rebuilding the drive, we're rebuilding trust across the entire array. -- Chris
    1 point
  23. So for some reason after restarting the docker to remove the CODE, I can't get it to detect changes in the UNRAID folder. It did the initial sync fine, however when i added a folder and some text documents to test it's not syncing those. Any ideas? Disregard Figured it out, was my own stupidity.
    1 point
  24. You have to download the Unraid-Kernel-Helper-Plugin (not the Docker container), then you can click on it (Unraid-Kernel-Helper-Plugin) on the settings page.
    1 point
  25. No problem, try to help where I can. Does the Nvidia drivers also show up?
    1 point
  26. Yes, simply download my prebuilt 6.8.3 with Nvidia driver builtin, extract it and replace all the bz* files from the archive in the root of your USB Boot Device and it should hopfully boot, but as I said, you have to reassign your cache pool. Please report back if something isn't working as expected.
    1 point
  27. Ahh I think I see what you mean. When I tried to revert before even though I copied my config back it didn't restore my array which I never changed after going to beta35. I'm going to give this a shot. Thank you so much for your help!
    1 point
  28. What is not working reverting back? If you want to go back to 6.8.3 go to my linked post above load the stable version with Nvidia (at the bottom), disable autostart (settings - disk settings - apply), shutdown your server, copy the files from the downloaded zip archive to your USB Flash Boot device (overwrite the existing ones) and restart the server. Then you have to reassign your cache drive (since 6.8.3 can't handle multiple cache pools but keep in mind that only one cache pool will work) and start the array, everything should hopefully work again as you know it (if you also need your UUID from your GPU download the Unraid-Kernel-Helper-Plugin - not the Docker container!).
    1 point
  29. Yep, cancel and try without a different disk.
    1 point
  30. slow file transfer was root caused to nic driver for large file transfer offload. Thanks everyone for their input!
    1 point
  31. Hey, from what I can see, you have setup deluge correctly. The reason why your uploads are slow is most likely due to low demand. When you seed your torrents, it is uploading data to other users to use (so they can download the same torrent). So you may only be sending data to 1 person who is also downloading the torrent. Have a search on how torrenting works: https://www.howtogeek.com/141257/htg-explains-how-does-bittorrent-work/#:~:text=torrent file into a BitTorrent client.&text=Once connected%2C a BitTorrent client,BitTorrent clients in the swarm. If you want to test your actual upload speeds, see spaceinvaderone's video here: If you are seeding to many peers, check through your settings/preferences to see if you have any limits on the upload speeds. Also check the bottom right footer on the main deluge screen (that shows the total download and upload speeds).
    1 point
  32. Because that's the way the hardware is designed. If one of the ACS override options don't help you, then you can either permanently attach the device to the VM when you edit it or use the HotPlug USB plugin
    1 point
  33. Same, I upgraded last night and before the upgrade was joined to ADS (Windows Server 2019) no issue. Now for the life of me I can't get it to rejoin. Tried removing the machine from ADS before rejoining as well. My log looks just like Darren's above btw. Edit: I tried running the permissions tool thinking that might help and was still unable to join.
    1 point
  34. I've updated to Version: 6.9.0-beta35 just now and I was using linuxserver.io Plex docker as well with unraid nvidia plugin. I switched to this plugin and hardware transcoding is working without any problems out of the box. I think it is simply important to follow the instructions exactly. @ich777 Thanks for the great work!
    1 point
  35. Wow give the man a break. It requires considerable testing. We will have to be patient and give it a month before champing at the bit at least.
    1 point
  36. It was my older gaming computer. How it all began....... ---------------------------------------------------------------------------------------------- Let me know what you guys think.
    1 point
  37. Just a little feedback on upgrading from Unraid Nvidia beta30 to beta35 with Nvidia drivers plugin. The process was smooth and I see no stability or performance issue after 48h, following these steps : - Disable auto-start on "nvidia aware" containers (Plex and F@H for me) - Stop all containers - Disable Docker engine - Stop all VMs (none of them had a GPU passthrough) - Disable VM Manager - Remove Unraid-Nvidia plugin - Upgrade to 6.9.0-beta35 with Tools>Update OS - Reboot - Install Nvidia Drivers plugin from CA (be patient and wait for the "Done" button) - Check the driver installation (Settings>Nvidia Drivers, should be 455.38, run nvidia-smi under CLI). Verify the GpuID is unchanged, which was the case for me, otherwise the "NVIDIA_VISIBLE_DEVICES" variable should be changed accordingly for the relevant containers - Reboot - Enable VM Manager, restart VMs and check them - Enable Docker engine, start Plex and F@H - Re-enable autostart for Plex and F@H All this is perhaps a bit over-cautious, but at least I can confirm I got the expected result, i.e. an upgraded server with all functionalities up and running under 6.9.0-beta35 !
    1 point
  38. Ever since I started using unraid (2010, v4.7), the community is what has been the leader in adding enhancements/value/features to unraid. Initially unraid didn't do much more than being a NAS, which was exactly what it was designed to do. But the community was the ones who started to build plugins and guides on how to use them to add way more functionally then the core function of just a NAS. That's not to say limetech was lacking really. They did and do build a rock solid NAS and that was the motto for the longest time. But a lot of user, and definitely myself wanted to keep utilizing the hardware more and more, way beyond just a NAS. The community really thrived at that. I've been able to add much more functionality to my system, learn and use more and more programs thanks to unraid/limetech and the community. I've really enjoyed the community here, it has felt small and personable and while its growing it still has the small tight knit feeling. A place where people give great support and never makes anyone feel like they have asked a stupid question. Unraid is where I've learned a lot of things about linux dockers etc. Again thanks to the community. I'm sure I'm just stating the obvious here at this point. Not to say unraid is worthless without the community but it is what helps or maybe even the cause to why it thrives. On a somewhat selfish note, I have very much benefited from the work of all the community devs especially @CHBMB and @bass_rock with their work on the nvidia plugin. For the people that use it, it was a huge breath of fresh air for older systems running plex. And it is definitely not exclusive to older systems. I also used the DVB drivers that was built by them. Unraid/limetech really didn't seem interested, at the time in providing support for the nvidia drivers and @CHBMB and the @linuxserver.io team saw how much the "niche" (I honestly don't think it's that niche) of people really wanted and would really benefit from it. I was ecstatic when it as finally released. I'm not sure where the notion came that the "third party" kernel was unstable as @CHBMB and the @linuxserver.io team work really hard at releasing good dockers/plugins etc. With very good support and documentation. It's such a no brainer when going into CA Apps and seeing something maybe by @linuxserver.io, it's always what I'll install given the choice. I had mentioned this in the request thread for GPU drivers in the kernel to @limetech that having the ability for hardware acceleration in plex via nvidia cards would attract users. I'm sure it did and likely attracted users for other reasons once @CHBMB and @bass_rock got it working. Limetech didn't ever comment in that thread and from what I remember was not at all interested at the time in pursuing it, at least from what I could tell from public information. Yet @CHBMB and @bass_rock worked hard to make it happen and as I mentioned I'm sure that created revenue for limetech and I know made many people happy. I'm glad limetech has decided to build in the feature and support it at the company level. And really this should be a big win for both @limetech and @CHBMB. For limetech because it's a great added feature and for CHBMB to give him a break from having to support that plugin which was clearly a lot of work. Maybe even freeing up his time to work on other great things for the community. While I'm glad he is finally getting a break. I do hope he and any other developers that may have decided to leave come back, as I do really appreciate their work. I also hope that this situation actually ends up being more positive then negative. It looks like limetech as learned more now, then they I'm sure already knew, how valuable their community developers are. And hopefully more communication will help build a stronger better relationship with the community and its developers, because the combination of the limetech team and the community developers has created a ever evolving fastastice product. Thank you to both the limetech team, the community and all the community developers.
    1 point
  39. In principal I agree, however though I am not using it myself I think it unfair not to acknowledge the stability attained by @CHBMB and @bass_rock 's Nvidia plugin. From its forum thread, it appears that there are quite a number of successful users and few to none show-stopping issues. That seems pretty stable to me. Here is hoping that the limetech's latest addition will prove itself as stable in short accord.
    1 point
  40. Hi, I would go for the inatec, good cards, compatible and cheap. The Startech is expensive but it's another card with more chipsets compared to the chaper ones. You can choose any of these, depending on your needs: Inatec KT4004 - 4 usb 3.0 external ports with power connector - Fresco chipset Inatec KT4006 - 2 usb 3.0 external ports + 2 usb 3.0 internal ports (to be connected with an extension cable (not provided) to the front of the case for example) - no power connector - Fresco chipset There's a lso Inatec KTU3FR-5O2I (5 usb 3.0 external ports + 2 usb 3.0 internal ports + power connector): however this card has the Fresco chipset and VLI chipset and I'm not sure that the VLI chipset works out of the box. I have the Inatec KT4006 and it works good in my catalina and big sur, just connect and passthrough. Update: sorry, I read now that you have supermicro, the op reported some issue with supermicro+inatec, so not sure..however he reported issues with the KTU3FR-5O2I, which has the vli chipset too as I wrote. All I can say is that the fl1100 fresco chipset works out of the box and the listed cards have only the fresco chipset.
    1 point
  41. Will update the plugin and add a warning at the top to don't close the windows with the 'X' and wait for the 'Done' button.
    1 point
  42. As a user of Unraid I am very scared about the current trends. Unraid as a base it is a very good server operating system but what makes it special are the community applications. I would be very sad if this breaks apart because of maybe wrong or misunderstandable communication. I hope that everyone will get together again. For us users you would make us all a pleasure. I have 33 docker containers and 8 VM running on my system and I hope that my system will continue to be as usable as before. I have many containers from linuxserver.io. I am grateful for the support from limetech & the whole community and hope it will be continued. sorry for my english i hope you could understand me.
    1 point
  43. @limetech Not wanting to dogpile on to you, but you would do well to go above and beyond in rectifying the situation with any communality developers that have issues. The community plugins and features that supply so much usability and functionality to unraid that are lacking in the base product actually make unraid worth paying for. if you start loosing community support, you will start to loose it all. with that I am sure I and others will not recommend people to purchase and use your software. @CHBMB @aptalca @linuxserver.io Maybe a cool down period is needed, but don't just pack up your things and go home, it's all too common for companies to ignore users and communities, a large part of the community is often invisible to them hidden behind keeping the business running and profits. it makes it easy for customer facing employees to make statements that might be taken as insensitive.
    1 point
  44. I do not use any of these unofficial builds, nor do i know what they are about and what features they provide that are not included in stock unraid. That being said, i still feel that devs that release them have a point. I think the main issue are these statements by @limetech : "Finally, we want to discourage "unofficial" builds of the bz* files." which are corroborated by the account of the 2019 pm exchange: "concern regarding the 'proliferation of non-stock Unraid kernels, in particular people reporting bugs against non-stock builds.'" Yes technically its true that bug reports based on unofficial builds complicate matters. Also its maybe frustrating that people are reluctant to go the extra mile to go back to stock unraid and try to reproduce the error there. Especially since they might be convinced (correctly or not) it has nothing to do with the unoffial build. Granted from an engineers point of view that might be seen as a nuisance. But from a customer driven business point of view its a self destructive perspective. Obviously these builds fill a need that unraid could not, or else they would not exist and there wouldn't be enough people using them to be a "bug hunting" problem in the first place. They expand unraids capabilities, bring new customers to unraid, demonstrate a lively and active community and basically everything i love about unraid. I think @limetech did not mean it in that way, but i can fully see how people who poured a lot of energy and heart into the unraid ecosystem might perceive it that way. I think if you would have said instead: "Finally we incorporated these new features x,y, and z formerly only available in the builds by A, B and C. Thanks again for your great work A,B and C have being doing for a long while now and for showing us in what way we can enhance unraid for our customers. I took a long time, but now its here. It should also make finding bugs more easy, as many people can now use the official builds." then everybody would have been happy. I think its probably a misunderstanding. I can't really imagine you really wanting to discourage the community from making unraid reach out to more user.
    1 point
  45. 1 point
  46. The multifunction option is kinda a workaround in certain cases, like some AMD GPUs need it. In most cases it isn't needed and most setups work without. If you kinda understand the basics and know how to fix small things, Unraid is pretty easy to get to work, but every setup is different and kinda every user has it's own small quirks.
    1 point
  47. Your docker.img file is trashed, and the syslog is being spammed with errors from it, hence the error FCP is throwing at you. Your recourse is to stop the docker service via Settings - docker. Delete the image from there, then re-enable the service, hit the apps tab, previous apps, check off whatever you want and hit install multi.
    1 point