Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/22/20 in all areas

  1. 16 points
    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.
  2. 15 points
    I come here to see what's new in development and find that there is a big uproar. Hate to say it, but I've been here a long time and community developers come and go and that's just the way it is. This unRAID product opens the door to personalizations, both private and shared. Community developers do leave because they feel that unRAID isn't going in the direction they want it to go or that the unRAID developers aren't listening to them even though there is no obligation to do so. Some leave in a bigger fuss than others. The unRAID developers do the best they can at trying to create a product that will do what the users want. They also do their best to support the product and the community development. The product is strong and the community support is strong and new people willing to put in time supporting it will continue to appear. Maybe some hint of what was coming might have eased tensions, but I just can't get behind users taking their ball and going home because unRAID development included something they used to personally support. That evolution has happened many times over the years, both incrementally and in large steps. That's the nature of this unRAID appliance type OS as it gets developed. There is no place for lingering bad feelings and continuing resentful posts. Hopefully, the people upset can realize that the unRAID developers are simply trying to create a better product, that they let you update for free, without any intent to purposely stomp on community developers.
  3. 12 points
    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.
  4. 9 points
    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).
  5. 9 points
    Before anyone else beats me to it: Soon™
  6. 7 points
    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
  7. 5 points
    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.
  8. 5 points
    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
  9. 5 points
    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.
  10. 5 points
    Issue appears to be that if you have any VM running that used VNC, then starting it would mess up the displays on the dashboard. Either way, this issue is fixed next rev
  11. 4 points
    I just saw the release notes for the last version of Unasigned Devices: Might be that ?
  12. 4 points
    Built zfs-2.0.0-rc7 for unRAID-6.8.3 & 6.9.0-beta35 Great to see that unRAID is finally adding native ZFS so this might be one of the last builds from me And yes, i´m already using the new way of side-loading kernel moduels in this plugin
  13. 4 points
    Hätte ich nicht so viel gequatscht, wäre es auch schneller gegangen, aber ich wollte so viele Informationen wie möglich vermitteln und die 10 Minuten habe ich gerade so unterboten ^^
  14. 4 points
    I see questions on Reddit and here on the forums asking about VM performance for Dual(or multi) socket motherboards. So I figured I’d write up a basic tuning guide for NUMA environments. In this guide I will discuss three things, CPU tuning, memory tuning and IO tuning. The three intertwine quite a bit so, while I will try to write them separate, they really should be considered as one complex tuning. Also, if there is one rule I recommend you follow it is this: don’t cross NUMA nodes for performance sensitive VMs unless you have no choice. So for CPU tuning, it is fairly simple to determine, from the command line, what CPUs are connected to which node. Issuing the following command: numactl -H Will give you a readout of which CPUs are connected to which nodes and should look like this: (Yes they are hyperthreaded 10-cores, they are from 2011 and your first warning should be that they are only $25USD a pair on eBay: xeon e7-2870, LGA1567) This shows us that CPUs 0-9 and their hyperthreads 20-29 are on node 0, it also shows us the memory layouts for the system, which will be useful later. With this layout pinning a VM to cores 0-7 and 20-27 would give the VM 8 cores and 8 threads all from one CPU. If you were to pin cores 7-14 and 27-34 your VM would still have 8 cores and 8 threads but now you have a problem for your VM, without tuning the XML, it has no idea that the CPU it was given is really on two CPUs. One other thing that you can do to help with latency is to isolate an entire CPU in the unRAID settings, (Settings>CPU Pinning). That would basically reserve the CPU for that VM and help reduce unnecessary cache misses by the VM. For memory tuning, you will need to add some XML to the VM to force allocation of memory from the correct node. That XML will look something like: <numatune> <memory mode='strict' nodeset='0' /> </numatune> For this snippet of XML mode=”strict” means that if there isn’t enough memory for the VM to allocate it all to this node then it will fail to start, you can change this to “preferred” if you would like it to start anyway with some of its memory allocated on another NUMA node. Lastly, IO tuning is a bit different from the last two. Before we were choosing CPUs and memory to assign to the VM based on their node, but for IO tuning the device you want to pass-through, (be it PCI or USB) the node is fixed and you may not have the same kind of resource(a graphics card) on the other node. This means that ultimately the IO devices you want to pass-through will, in most cases, actually determine which node your VM should prefer to be assigned to. To determine which node a PCI device is connected to you will first need that devices bus address, which should look like this: 0000:0e:00.0. To find the devices address in the unRAID webGUI go to Tools>System Devices then serach for your devices in the PCI Devices and IOMMU Groups box. Then open a terminal and issue the following commands: cd /sys/bus/pci/devices/[PCI bus address] cat numa_node The output should look like this: For my example here you can see that my device is assigned to NUMA node 0. I will point out that if you are passing multiple devices, (GPU, USB controller, NVMe drive) that they all might not be on the same node, in that case i would prioritize which node you ultimately assign your VM to based on the use of that VM. For gaming i would prioritize the GPU being on the same node personally but YMMV. Other thing that you can do to help with latency is to isolate an entire CPU for the a VM if it is for something like Gaming. That would basically reserve the CPU for that VM and help reduce unnecessary cache misses by the VM It can be easy to visualize NUMA nodes as their own computers. Each node may have its own CPU, RAM and even IO devices. The nodes are interconnected through high-speed interconnects but if one node wants memory or IO from a device on another node, it has to ask the other node for it, rather than address it directly. This request causes latency and costs performance. In the CPU section of this guide we issued the command “numactl -H” and this command also shows us the distance from one node to another, abstractly, with the nodes laid out in a grid showing distance from one node to another. The farther the distance, the longer the turnaround time for cross-node requests and the higher the latency. Advanced tuning: It is possible, if you have need of it, to craft the XML for a VM in such a way as to make the VM NUMA aware so that the VM is able to properly use two or more socketed CPUs. This can be done by changing both the <cputune> and <vcpu> tags. This is outside the scope of a basic tuning guide and I will just include a link to https://libvirt.org/formatdomain.html which included the entire specification for libvirt Domain XML, which the unraid VMs are written in.
  15. 4 points
    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.
  16. 3 points
    Wie kann ich eine Testlizenz erwerben, wie lange ist sie gültig und welchen Funktionsumfang bietet sie? Testlizenzen werden direkt in Unraid OS erworben (gehe dazu auf Extras > Registrierung) Die Testlizenz ist 30-Tage gültig und sie kann bis zu 2x um 15 Tage verlängert werden Testlizenzen bieten dir zeitlich begrenzten Zugriff auf Unraid OS in vollem Funktionsumfang und ohne Beschränkung auf angeschlossene Speichergeräte. Ist für Unraid eine aktive Internetverbindung erforderlich? Für dein Lizenztyp Basic/Plus/Basic: Nein Für Testlizenzen ist eine aktive Internetverbindung beim Serverstart erforderlich um die Probelizenz zu überprüfen. Welche Einschränkungen gibt es zwischen den Lizenztypen Basic/Plus/Pro? Basic: Bis zu 6 angeschlossene Speichergeräte Plus: Bis zu 12 angeschlossene Speichergeräte Pro: Keine Limitierung an angeschlossenen Speichergeräten Es gibt keine weiteren Einschränkungen der Software unabhängig vom Lizenztyp. Wieviele Speichergeräte kann ich im Array bzw. Cache verwenden? Unraid OS Pro unterstützt bis zu 30 Speichergeräte im Paritätsgeschütztem Array (28 Datenträger und 2 Paritätsdatenträger) und bis zu 24 Datenträger im Cache-Pool. Zusätzliche Speichergeräte können weiterhin direkt mit anderen Unraid-Funktionen wie VM's oder dem Plugin "Unassigned Devices" genutzt werden. Geräte die keine Datenträger sind wie GPU's zählen nicht zum Limit der angeschlossenen Speichergeräten. Das USB Bootgerät zählt nicht zu den angeschlossenen Speichergeräten. Wie lauten die Mindesthardwareanforderungen von Unraid OS? Ein 64-Bit-fähiger Prozessor mit 1GHz oder besser Mindestens 2GB RAM Linux-Hardwaretreiber für Speicher-, Ethernet, und USB-Controller Zwei Festplatten - um den Schutz deiner Dateien mit einer Paritätsfestplatte zu gewährleisten Je nach Anwendungstyp und installierten Apps und VM's können die Hardwareanforderungen dementsprechend höher sein. Sind Updates von Unraid OS Kostenpflichtig? Alle Lizenzschlüssel Basic/Plus/Pro enthalten kostenlose Updates auf neue Versionen von Unraid OS. Ist die Lizenz Hardwaregebunden? Die Lizenz ist an die GUID (Eindeutige ID) vom USB Startgerät gebunden somit kann bei einem Hardwaredefekt das USB Startgerät einfach an anderer Hardware angeschlossen werden und Unraid OS gestartet werden. Was passiert wenn mein USB Startgerät defekt ist? Sollte dein USB-Stick defekt sein, kannst du deinen Lizenzschlüssel einmal pro Jahr auf einen neuen USB-Stick übertragen.
  17. 3 points
    Hey guys. We had a Corona virus scare over here (been super sick), so we've been dealing with that. I was hoping to have this out by tonight, but I am still working on it. I have the code written and the JSON is independently completed, but I have yet to integrate it into the UUD. And the the largest task of all is documentation and release notes (and that takes a LONG time). I've been going back and forth debating whether or not to release this independently as the Ultimate Plex Dashboard (UPD), or just integrate it into the UUD as version 1.5. I've decided to incorporate it into UUD, but for those of you who want a dedicated Plex Dashboard, I can release a standalone version of this as well, if there is enough demand. I'll post updates next week on a potential release date. I hope you all have a fantastic Thanksgiving!
  18. 3 points
    Unraid Kernel Helper/Builder With this container you can build your own customized Unraid Kernel. Prebuilt images for direct download are on the bottom of this post. By default it will create the Kernel/Firmware/Modules/Rootfilesystem with nVidia & DVB drivers (currently DigitalDevices, LibreElec, XBOX One USB Adapter and TBS OpenSource drivers selectable) optionally you can also enable ZFS, iSCSI Target, Intel iGPU and Mellanox Firmware Tools (Mellanox only for 6.9.0 and up) support. nVidia Driver installation: If you build the images with the nVidia drivers please make sure that no other process is using the graphics card otherwise the installation will fail and no nVidia drivers will be installed. ZFS installation: Make sure that you uninstall every Plugin that enables ZFS for you otherwise it is possible that the built images are not working. You also can set the ZFS version from 'latest' to 'master' to build from the latest branch from Github if you are using the 6.9.0 repo of the container. iSCSI Target: Please note that this feature is at the time command line only! The Unraid-Kernel-Helper-Plugin has now a basic GUI for creation/deletion of IQNs,FileIO/Block Volumes, LUNs, ACL's. ATTENTION: Always mount a block volume with the path: '/dev/disk/by-id/...' (otherwise you risk data loss)! For instructions on how to create a target read the manuals: Manual Block Volume.txt Manual FileIO Volume.txt ATTENTION: Please read the discription of the variables carefully! If you started the container don't interrupt the build process, the container will automatically shut down if everything is finished. I recommend to open a console window and type in 'docker attach Unraid-Kernel-Helper' (without quotes and replace 'Unraid-Kernel-Helper' with your Container name) to view the log output. (You can also open a log window from the Docker page but this can be verry laggy if you select much build options). The build itself can take very long depending on your hardware but should be done in ~30minutes (some tasks can take very long depending on your hardware, please be patient). Plugin now available (will show all informations about the images/drivers/modules that it can get): https://raw.githubusercontent.com/ich777/unraid-kernel-helper-plugin/master/plugins/Unraid-Kernel-Helper.plg Or simply download it through the CA App This is how the build of the Images is working (simplyfied): The build process begins as soon as the docker starts (you will see the docker image is stopped when the process is finished) Please be sure to set the build options that you need. Use the logs or better open up a Console window and type: 'docker attach Unraid-Kernel-Helper' (without quotes) to also see the log (can be verry laggy in the browser depending on how many components you choose). The whole process status is outlined by watching the logs (the button on the right of the docker). The image is built into /mnt/cache/appdata/kernel/output-VERSION by default. You need to copy the output files to /boot on your USB key manually and you also need to delete it or move it for any subsequent builds. There is a backup copied to /mnt/cache/appdata/kernel/backup-version. Copy that to another drive external to your Unraid Server, that way you can easily copy it straight onto the Unraid USB if something goes wrong. THIS CONTAINER WILL NOT CHANGE ANYTHING TO YOUR EXISTING INSTALLATION OR ON YOUR USB KEY/DRIVE, YOU HAVE TO MANUALLY PUT THE CREATED FILES IN THE OUTPUT FOLDER TO YOUR USB KEY/DRIVE AND REBOOT YOUR SERVER. PLEASE BACKUP YOUR EXISTING USB DRIVE FILES TO YOUR LOCAL COMPUTER IN CASE SOMETHING GOES WRONG! I AM NOT RESPONSIBLE IF YOU BREAK YOUR SERVER OR SOMETHING OTHER WITH THIS CONTAINER, THIS CONTAINER IS THERE TO HELP YOU EASILY BUILD A NEW IMAGE AND UNDERSTAND HOW THIS IS WORKING. UPDATE NOTICE: If a new Update of Unraid is released you have to change the repository in the template to the corresponding build number (I will create the appropriate container as soon as possible) eg: 'ich777/unraid-kernel-helper:6.8.3'. Forum Notice: When something isn't working with or on your server and you make a forum post always include that you use a Kernel built by this container! Note that LimeTech supports no custom Kernels and you should ask in this thread if you are using this specific Kernel when something is not working. CUSTOM_MODE: This is only for Advanced users! In this mode the container will stop right at the beginning and will copy over the build script and the dependencies to build the kernel modules for DVB and joydev in the main directory (I highly recommend using this mode for changing things in the build script like adding patches or other modules to build, connect to the console of the container with: 'docker exec -ti NAMEOFYOURCONTAINER /bin/bash' and then go to the /usr/src directory, also the build script is executable). Note: You can use the nVidia & DVB Plugin from linuxserver.io to check if your driver is installed correctly (keep in mind that some things will display wrong and or not showing up like the driver version in the nVidia Plugin - but you will see the installed grapics cards and also in the DVB plugin it will show that no kernel driver is installed but you will see your installed cards - this is simply becaus i don't know how their plugins work). Thanks to @Leoyzen, klueska from nVidia and linuxserver.io for getting the motivation to look into this how this all works... For safety reasons I recommend you to shutdown all other containers and VM's during the build process especially when building with the nVidia drivers! After you finished building the images i recommend you to delete the container! If you want to build it again please redownload it from the CA App so that the template is always the newest version! Beta Build (the following is a tutorial for v6.9.0): Upgrade to your preferred stock beta version first, reboot and then start building (to avoid problems)! Download/Redownload the template from the CA App and change the following things: Change the repository from 'ich777/unraid-kernel-helper:6.8.3' to 'ich777/unraid-kernel-helper:6.9.0' Select the build options that you prefer Click on 'Show more settings...' Set Beta Build to 'true' (now you can also put in for example: 'beta25' without quotes to automaticaly download Unraid v6.9.0-beta25 and the other steps are not required anymore) Start the container and it will create the folders '/stock/beta' inside the main folder Place the files bzimage bzroot bzmodules bzfirmware in the folder from step 5 (after the start of the container you have 2 minutes to copy over the files, if you don't copy over the files within this 2 mintues simply restart the container and the build will start if it finds all files) (You can get the files bzimage bzroot bzmodules bzfirmware also from the Beta zip file from Limetch or better you first upgrade to that Beta version and then copying over the files from your /boot directory to the directory created in step 5 to avoid problems) !!! Please also note that if you build anything Beta keep an eye on the logs, especially when it comes to building the Kernel (everything before the message '---Starting to build Kernel vYOURKERNELVERSION in 10 seconds, this can take some time, please wait!---' is very important) !!! Here you can download the prebuilt images: Unraid Custom nVidia builtin v6.8.3: Download (nVidia driver: 450.66) Unraid Custom nVidia & DVB builtin v6.8.3: Download (nVidia driver: 450.66 | LE driver: 1.4.0) Unraid Custom nVidia & ZFS builtin v6.8.3: Download (nVidia driver: 450.66 | ZFS version: 0.8.4) Unraid Custom DVB builtin v6.8.3: Download (LE driver: 1.4.0) Unraid Custom ZFS builtin v6.8.3: Download (ZFS version: 0.8.4) Unraid Custom iSCSI builtin v6.8.3: Download (targetcli version: 2.1.53) Manual Block Volume.txt Manual FileIO Volume.txt Unraid Custom nVidia builtin v6.9.0 beta25: Download (nVidia beta driver: 450.66) Unraid Custom nVidia & DVB builtin v6.9.0 beta25: Download (nVidia beta driver: 450.66 | LE driver: 1.4.0) Unraid Custom nVidia & ZFS builtin v6.9.0 beta25: Download (nVidia beta driver: 450.66 | ZFS Build from 'master' branch on Github on 2020.08.19) Unraid Custom ZFS builtin v6.9.0 beta25: Download (ZFS Build from 'master' branch on Github on 2020.07.12) Unraid Custom iSCSI builtin v6.9.0 beta25: Download (targetcli version: 2.1.53) Manual Block Volume.txt Manual FileIO Volume.txt Unraid Custom nVidia builtin v6.9.0 beta29: Download (nVidia beta driver: 455.23.04) Unraid Custom nVidia & DVB builtin v6.9.0 beta29: Download (nVidia beta driver: 455.23.04 | LE driver: 1.4.0) Unraid Custom nVidia & ZFS builtin v6.9.0 beta29: Download (nVidia beta driver: 455.23.04 | ZFS v2.0.0-rc2) Unraid Custom ZFS builtin v6.9.0 beta29: Download (ZFS v2.0.0-rc2) Unraid Custom iSCSI builtin v6.9.0 beta29: Download (targetcli version: 2.1.53) Manual Block Volume.txt Manual FileIO Volume.txt Unraid Custom nVidia builtin v6.9.0 beta30 Download (nVidia driver: 455.28) Unraid Custom nVidia & DVB builtin v6.9.0 beta30: Download (nVidia driver: 455.28 | LE driver: 1.4.0) Unraid Custom nVidia & ZFS builtin v6.9.0 beta30: Download (nVidia driver: 455.28 | ZFS 0.8.5) Unraid Custom ZFS builtin v6.9.0 beta30: Download (ZFS 0.8.5) Unraid Custom iSCSI builtin v6.9.0 beta30: Download (targetcli version: 2.1.53) Manual Block Volume.txt Manual FileIO Volume.txt Notice for Custom pre-built images for Unraid version 6.9.0beta35 and up: Since Unraid changed the game completely with the release of version 6.9.0beta35 and up, so that you can install the Nvidia, DVB and many more other addons to Unraid that I even can't imagine at the time of writing, I will not make or post pre-built images here for the new versions. However I will update the container in general so that you can build your own custom images if you want a 'all in one' solution. (You have to be at least on Unraid 6.9.0beta35 to see the Plugins in the CA App for Nvidia, DVB,...) If you like my work, please consider making a donation
  19. 3 points
    @kim_sv @vw-kombi see here:- https://github.com/binhex/documentation/blob/master/docker/faq/sonarr.md
  20. 2 points
    Nvidia-Driver (only Unraid 6.9.0beta35 and up) This Plugin is only necessary if you are planning to make use of your Nvidia graphics card inside Docker Containers. If you only want to use your Nvidia graphics card for a VM then don't install this Plugin! Discussions about modifications and/or patches that violates the EULA of the driver are not supported by me or anyone here, this could also lead to a take down of the plugin itself! Please remember that this also violates the forum rules and will be removed! Installation of the Nvidia Drivers (this is only necessary for the first installation of the plugin) : Go to the Community Applications App and search for 'Nvidia-Drivers' and click on the Download button (you have to be at least on Unraid 6.9.0beta35 to see the Plugin in the CA App) : Or download it directly from here: https://raw.githubusercontent.com/ich777/unraid-nvidia-driver/master/nvidia-driver.plg After that wait for the plugin to successfully install (don't close the window with the , wait for the 'DONE' button to appear, the installation can take some time depending on your internet connection, the plugin downloads the Nvidia-Driver-Package ~150MB and installs it afterwards to your Unraid server) : Click on 'DONE' and continue with Step 4 (don't close this window for now) : Check if everything is installed correctly and recognized to do this go to the plugin itself if everything shows up PLUGINS -> Nvidia-Driver (if you don't see a driver version at 'Nvidia Driver Version' or another error please scroll down to the Troubleshooting section) : If everything shows up correctly click on the red alert notification from Step 3 (not on the 'X'), this will bring you to the Docker settings. At the Docker page change 'Enable Docker' from 'Yes' to 'No' and hit 'Apply' (you can now close the message from Step 2) : Then again change 'Enable Docker' from 'No' to 'Yes' and hit again 'Apply' (that step is only necessary for the first plugin installation, you can skip that step if you are going to reboot the server - the background to this is that when the Nvidia-Driver-Package is installed also a file is installed that interacts directly with the Docker Daemon itself and the Docker Daemon needs to be reloaded in order to load that file) : After that, you should now be able to utilize your Nvidia graphics card in your Docker containers how to do that see Post 2 in this thread. IMPORTANT: If you don't plan or want to use acceleration within Docker containers through your Nvidia graphics card then don't install this plugin! Please be sure to never use one card for a VM and also in docker containers (your server will hard lock if it's used in a VM and then something want's to use it in a Container). You can use one card for more than one Container at the same time - depending on the capabilities of your card. Troubleshooting: (This section will be updated as soon as more someone reports an issue and will grow over time) NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.: This means that the installed driver can't find a supported Nvidia graphics card in your server (it may also be that there is a problem with your hardware - riser cables,...). Check if you accidentally bound all your cards to VFIO, you need at least one card that is supported by the installed driver (you can find a list of all drivers here, click on the corresponding driver at 'Linux x86_64/AMD64/EM64T' and click on the next page on 'Supported products' there you will find all cards that are supported by the driver. If you bound accidentally all cards to VFIO unbind the card you want to use for the Docker container(s) and reboot the server (TOOLS -> System devices -> unselect the card -> BIND SELECTED TO VFIO AT BOOT -> restart your server). docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused "process_linux.go:432: running prestart hook 0 caused \"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: device error: GPU-9cfdd18c-2b41-b158-f67b-720279bc77fd: unknown device\\n\""": unknown.: Please check the 'NVIDIA_VISIBLE_DEVICES' inside your Docker template it may be that you accitentally have what looks like a space at the end or in front of your UUID like: ' GPU-9cfdd18c-2b41-b158-f67b-720279bc77fd' (it's hard to see that in this example but it's there) Reporting Problems: Please be sure if you have a problem to always include a screenshot from the Plugin page, a screenshot of the output of the command 'nvidia-smi' (simply open up a Unraid terminal with the button on the top right of Unraid and type in 'nvidia-smi' without quotes) and the error from the startup of the Container/App if there is any.
  21. 2 points
    Fehler gefunden. Die SSDs waren in der falschen Reihenfolge. Funktioniert jetzt alles
  22. 2 points
  23. 2 points
    Attached OVMF files from edk2 stable release 202011, released today. Work good for me. edk2-202011.zip
  24. 2 points
    Dalek Banner Size: 1920x90 Dynamix color theme: Black Unraid Version: 6.9.0 This is the preview
  25. 2 points
    @S3ppo please try deactivating the subtitles
  26. 2 points
    The settings you mention on apply to where Unraid attempts to place new files - it does not affect the placement of existing files. there are a number of choices for manually moving files: use the linux command line if you are familiar with Linux commands use the ‘mc’ command from the Linux command line for an easier to use interface install and use a docker container such a Krusader if you want a graphical interface enable disk shares under Settings->Global Share settings and use your preferred file manager on Windows/MacOS to do it over the network. This can be more convenient but will be slower than doing internally within the Unraid server. one thing to be aware of whatever option you use is to make sure all operations are either disk-to-disk or share-to-share. You should never mix disk and shares in the same command (I.e. disk-to-share or share-to-disk) as this can lead to data loss.
  27. 2 points
    I am confused - Unraid will not automatically move files between array disks - this is a manual operation. Have I misunderstood what you actually did? Maybe posting your system’s diagnostics zip file (obtained via Tools -> Diagnostics might help with. working out. What. Is actually happening.
  28. 2 points
    It was done to unify the interface between how the dashboard and the docker tab works
  29. 2 points
    I completely agree with this sentiment. So we might have a solution for this, but I need to chat with the team about it. More info soon!
  30. 2 points
    Hallo zusammen, ich habe seit ein paar Tagen nun unraid am laufen und ich muss sagen ich bin sehr sehr begeistert. Deshalb möchte ich auch meine Erfahrungen hier teilen und vielleicht dem Einen oder Anderen Frischling wie mir damit helfen. Da mein Drucker (Sharp MX-C301W) kein Airprint zur Verfügung stellt hatte ich bisher in Proxmox eine VM am laufen welche Airprint über Cups bereistellt. Das wollte ich nun natürlich auch in unraid, bevorzugt über docker. Folgende Vorgehensweise brachte den Erfolg: In unraid unter Apps, Settings: "Enable additional search results from dockerHub" = yes. Dann nach airprint suchen und oben "Click Here To Get Results Fom DockerHub" auswählen. Docker image von firilith/airprint auswählen und "Click to install". Folgendes einstellen: Custom:br0 10.55.5.5 (eigene statische IP eures Netzwerk) dann add path (vorher anlegen): Container Path:/config <-> Host Path:/mnt/user/appdata/airprint/ Container Path:/services <-> Host Path:/mnt/user/appdata/airprint/services/ und add variable: Key:CUPSADMIN Value:admin Key:CUPSPASSWORD Value:password und Apply http://10.55.5.5:631/ im Browser eurer Wahl öffnen und unter Verwaltung "Neue Drucker suchen". Netzwerkdrucker muss eingeschaltet sein. Drucker auswählen und "Freigabe" aktivieren, dann weiter. Hersteller und Modell/Treiber auswählen (oder PPD Datei, durchsuchen..) und hinzufügen. Das wars, nun kann über Airprint aus z.B. dem iPad gedruckt werden. VG TD
  31. 2 points
    @Darren Cook If you need assistance with downgrading to 6.8.3 feel free to contact me or follow the post that @Zorlofe linked. Here you can get the files for the stock Unraid 6.8.3 with Nvidia driver (pre built images at the first post at the bottom):
  32. 2 points
  33. 2 points
    I have a windows vm running blue iris for Security camera duties. No video card. i also use this as a whole house audio server with multiple legacy m-audio delta multi-channel sound cards. No Linux drivers, but works fine on windows or Mac OS. No video card required. this also runs windows-only tv tuner software for whole house DVR, no video card required. i also have this connected to an old alarm system for which I wrote some drivers. The vm manages the connectivity and interfaces with a node red docker where all the logic is implemented. No video card required on desktop os for this job either. there are loads of use cases for desktop vms with no gpu. Of course, a lot can be handled in other ways on Linux, for example, but for those not comfortable in the black arts of bash and the command line, a headless windows or Mac vm can be a great tool.
  34. 2 points
    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!
  35. 2 points
    Thanks @binhex for the release of v3
  36. 2 points
    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.
  37. 2 points
    @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.
  38. 2 points
    Found it and it verified the driver is working. You da man!!
  39. 2 points
    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.
  40. 2 points
    I am using linuxserver.io Plex docker with unraid nvidia plugin and switched to this plugin and hardware transcoding is fine and no other issues. Sent from my iPhone using Tapatalk
  41. 2 points
    It was my older gaming computer. How it all began....... ---------------------------------------------------------------------------------------------- Let me know what you guys think.
  42. 2 points
    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.
  43. 2 points
    @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.
  44. 2 points
    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.
  45. 2 points
    @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?
  46. 2 points
    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.
  47. 2 points
    Hello all, I've been running Unraid on my QNAP TS-853A for about a month now. I intend to use Unraid full-time on this box with this as the primary file server in my home. Before switching to Unraid, I Googled if it was possible to run Unraid on a QNAP and the consensus was: "Probably, just try it." As long as you can access the BIOS and change the boot order, you should be able to boot into Unraid. Some people report not all of their drive bays working depending on which SATA controller was being used (that forum thread is from 2016, so an update may have added compatibility for those controllers). All 8 drive bays are working on my TS-853A. The rest of the hardware is working just fine. The LCD screen on the front of the QNAP constantly says "SYSTEM BOOTING >>>>>>>", but I can overlook that. One day I may try to see if I can modify that. I just want to document that it's possible -- and easy -- to run Unraid on a QNAP. My only experience with QNAP boxes is with my own, so your mileage may vary. This is my first Unraid installation, but everything was incredibly straight-forward. I had no complications getting things set up. As others have stated in the past, these NAS boxes come with 500 MB-ish of DOM flash storage. I didn't try to install Unraid on the DOM because I didn't know if it had a UID. It would be nice to use, but I don't see 500 MB being suitable in the long term. I actually removed the DOM because my BIOS would ignore my boot order and prioritize the DOM over my Unraid flash drive. I'll report back if I ever get around to booting Unraid from the DOM. The Celeron N3160 and 8 GB of DDR3 prevent me from going wild with dockers and VMs, but I had that expectation going in; my primary purpose for this box is a file server for my business. But it's running a Minecraft server for my nephews, Bitwarden, and a few other services that I use for work/play. I let my 2015 Nvidia Shield act as my Plex server pulling content from my Unraid SMB shares. Plus, boot times went from 10+ minutes to just a couple. Unraid has breathed new life into my QNAP. This was a hand-me-down of sorts, but I've always been a Synology guy. This QNAP was a clear upgrade from the hardware of the Synology, but the QNAP software experience was subjectively much worse. So far, it's been more than suitable for full-time use. If anyone else uses a QNAP for Unraid, I've attached the case model design I've made. ts-853a.svg
  48. 2 points
    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
  49. 1 point
    You can try this: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including the new disk you want to rebuild, replacement disk should be same size or larger than the old one -Check both "parity is already valid" and "maintenance mode" and start the array -Stop array -Unassign the disk you want to rebuild -Start array (in normal mode now), ideally the emulated disk will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk -If the emulated disk mounts and contents look correct stop the array -Re-assign the disk to rebuild and start array to begin.
  50. 1 point