Leaderboard
Popular Content
Showing content with the highest reputation since 02/19/24 in all areas
-
As some have figured out, there are new license key types coming soon™ for Unraid OS. We are still working on minor details but here is what we have planned. We are going to introduce two new keys: Starter - supports up to 4 devices. This will be offered at a lower price than today's Basic key. Unleashed - supports unlimited number of devices. This will be offered at about the same price as today's Plus key. These two new keys provide for free Unraid OS updates for one year following activation. After a year you have the option of extending the key for another year of updates for a fraction of the cost of the original key. If you choose not to extend, you can still run any version of Unraid OS released prior to your renewal date, back to version 6.12.8. Simultaneous with introducing these two key types, we will no longer offer Basic and Plus keys; but, Pro keys (with unlimited devices and Unraid OS updates for life) will still be offered. We might change the name of the key from Pro to Lifetime - that is one of the "minor details" we are still working on. Nothing changes for existing Basic/Plus/Pro keys: you still get Unraid OS updates for life and you will still have the option to upgrade Basic to Plus/Pro or Plus to Pro. For more on these changes, please see our blog post and for a wide-ranging discussion about the origin of Unraid, present state of the company and future plans, please see our Uncast Show episode: Please use this topic for any comments or questions.39 points
-
The current 28-device limitation applies to the unRAID array. You can have any number of btrfs/zfs pools with other devices. An upcoming version will let you have multiple unRAID arrays though we don't plan on increasing the width of a single unRAID array. With your Pro key you'll get this update for free 🙂20 points
-
18 points
-
You clearly didn't make the effort of even reading the post you're replying to.17 points
-
I had to chime in, this hit a nerve. I agree with 1812, they want everything for free. Even downloading movies. They will spend the money for hardware but software they want for free or next to nothing. Take a look at the users that rant the most. They are fairly new members. I doubt they have experienced a hard disk failure. This is where Unraid shines. If they complain about pricing, I doubt they use parity drive(s). I say let them leave and go to an alternative. I chose Unraid 14 years ago. Back then the biggest concern was LT’s risk management since Tom was a one man show. I wanted a system to be expandable, I wanted to use my various sized hard disks. I wanted the disk to spin down and I liked the idea that you could still access a disk by itself. It had to be an unconventional server, Unraid fit the bill. I went with the pro license at that time since it was the only one that covered my hard disk count. I just checked my email invoice from “Tom” and it was on sale for $109 ($10 discount) at that time. I spent more for a UPS. Soon I was maxed out and bought two 1TB drives, then larger drives and survived through the 2TB limit! I have experienced the introduction of Joe L.’s creations; cache_dirs, unMENU and preclear. We endured a number of LT re-locations. Unraid has come along way. Thanks Tom! Sorry, I haven’t been active on this forum lately, I been busy doing other things and frankly, Unraid just works. I have recovered through a number of hard disk failures, parity swaps, array up sizing and array down sizing. All painlessly. BTW, I still have the original flash drive. I didn’t cheap out on that. I’ve recommended and help setup Unraid using the Pro license to lots of people and not one complained about the cost. When my kids finally move out, we will happily pay for the “Lifetime” license no matter what the cost.12 points
-
A small point: it's not a subscription fee in this sense: with a subscription if you don't renew then the service ends. By contrast if you do not extend your Starter or Unleashed key your server still runs as before and you still have complete access to your data, etc.12 points
-
This plugin does a quick patch to the docker system on 6.12.8 only to prevent any empty host paths or container paths which may be present in an already installed template (or on a new installation) from triggering an error (and creating an orphan image) when updating the application. This is NOT fixing any bug in Unraid at all. Previously, the docker run command (eg: on 6.12.6) would not return an error if there was no container path specified. The docker system in 6.12.8+ does return an error (which is the proper operation). This quick patch simply has the docker system not add in to the docker run command any paths which has either the container or host side of it blank. If you did update an application and then had it orphan due to an empty path, then simply installing this plugin and then going to Apps, Previous Apps and reinstalling will get you back and running without changing the template to how it should be set up11 points
-
It's any publicly published version of Unraid OS, including "major" version updates, eg, from v6 to v7. We're also not going to play any games like coming up with "NewUnraid OS" where all of a sudden your key won't work or we start charging an extra fee to keep using.11 points
-
11 points
-
I appreciate the response regarding the licensing situation. The other concern that I would like some explanation for is the privacy issue related to the new update mechanism. I was finally able to coax some debug logs out of my browser, and I discovered that there's a lot of information being sent with every click of the "Update OS" button: apiVersion caseModel connectPluginVersion description expireTime flashProduct flashVendor guid inIframe keyfile lanIp name osVersion osVersionBranch registered regGuid regExp regTy regUpdatesExpired site state wanFQDN Some of these make sense as part of a license check (guid, keyfile, flash information). Some, though, seem to be quite extraneous: caseModel (does Limetech really need what kind of case my server is in?), LAN IP, hostname, description... none of these are needed to validate a license. The privacy policy (https://unraid.net/policies) says nothing about collecting this kind of information: What is the primary purpose for collecting all of this information? Is the information used for other purposes? If so, what? Is this information stored? If so: Is it stored in identifiable form? How long is it retained?10 points
-
1. The "core" of Unraid (the main array) isn't open source, and there aren't any "equals" to it in the OSS world (there are things that are similar, but nothing that has the whole feature set to my knowledge). 2. Even if "similar" is good enough, configuring an OSS-based system is still more complicated to deploy/configure/monitor/maintain. 3. Donations "just because people like the product as it is" sounds nice, but in practice very few people actually do that. (Simple example, because I know the numbers: I created and maintain the Tailscale plugin for Unraid. There are around 6,000 active installs right now. Of those 6,000 installs, I've had 3 people send anything via the donation button - 0.05%. I'm not complaining, just pointing out how things work in reality.)9 points
-
I think this is fine, just don't announce you're being acquired by Broadcom next week!!9 points
-
I'm not getting involved with the guesswork about a possible future licensing model. Should the financial need for a subscription model arise, I'll be happy to consider it for the system I've grown to love. But it really hurts me to see that Unraid as a brand is taking what seems like a lot of unnecessary PR damage right now. Unraid has always been very community reliant and driven and I'd say that was one the most liked points besides the OS. All of the hate and doomsday scenarios being spun online right now could've been avoided by better communication. I really hope a lesson is learnt from this and we'll see more up-front communication, rather than picking up the pieces later.9 points
-
Build’s Name: My Customised SFF Home Server Build Full Spec: PartPicker Link Usage Profile: Unraid Server for Containers, VM's and Storage Server Time to upgrade my home server again, decided to down size from my current Fractal Design XL to something smaller and more power efficient. Decided to go with the Fractal Node 304 case, I’m moving from 12x 8tb disks with dual parity to 6x 20tb disks with single parity so will fit. Using a smaller case will mean taking up a lot less space in my small home office! Here's a finished picture, with a rather long build thread below: ________________________________________________________________________ So then, started of by ordering the case. I managed to swap the white HDD caddys for black ones with a colleague, looks much better. Then swapped out the Fractal fans for black Noctua A9 and A14 Chromax fans. These look slightly better and much quieter. Reused one of the LSI 9207-8i HBA from the old server. The brackets are powder coated black and have a Fractal R3 40mm fan on the heat sink. The fans are mounted using black nylon nuts and bolts, reusing the same holes as the heat sink to keep things neat and tidy. Updated the firmware while I was at it. Installed a Corsair RM650 (2021) PSU and realised the motherboard ATX cables were pretty long. Time consuming, but re-pinned and braided the connectors to make the optimal length. The USB cables from the front IO to the motherboard were also pretty long, so found some shorter ones on Ali Express. Soldered these onto the original PCB and braided the cable. Also shortened and braided a few other cables, like the on/off, restart buttons and hdd activity cables. I also removed the front panel audio cables as not needed for a server. Not a massive problem, but noticed that the power cable orientation meant the cable at the PSU end pointed up and needed to loop round, which looked messy. So found a left angle IEC (that’s a thing) cable, braided and re-terminated at the case end. Now it points down and runs along the bottom of the case, much tidier. Next up was the mother boards silver IO shield, didn’t look brilliant on the black case. I couldn’t find a black one, thought about 3d printing one, but ended up just powder coating the original. Came out really well and looks much better. Installed everything on the motherboard and made a custom length, braided cable for the CPU fan. Did the same for the two front fans and exhaust fan. The case takes 6x 3.5 HDD’s, these would be filled with my 20tb disks, so needed somewhere to install the 2x 2.5 HDD’s I use for cache drives. Easy option would be to mount on the outside of the HDD caddys, but where’s the fun in that! I decided to make my own bracket to mount them both on the side of the case. Fabricated these out of aluminium sheet and powder coated black. Drilled two holes in the bottom of the case, then used some black, low profile bolts to secure the bracket. These are hidden by the plastic feet mounting covers that run round the bottom edge of the case, so can’t be seen. Inside view of the bottom of the case, where the brackets secured. I used black nylock nuts and black washers to keep looking original. Drilled two more holes a the top of the case and secured the bracket using rivnuts and some more low profile bolts, with black washers. These were needed to make sure the case top fitted without snagging. Made some custom length SATA power cables for the HDD’s to keep things tidy. Then connected the HBA’s SATA data cables. I forgot to take a picture with the cables tied together, but looks tidy. Swapped the remaining PCI cable to a black one and all done! All sealed up, shame no one will ever see the hard work that went into the build! A fun project though, so worth it for me! ________________________________________________________________________ Well done for making it to the end of this post! I'm please with how the builds turned out. My old server use to average 190W power draw, this uses 110W. To be honest, I was hoping for a little lower, need to do some troubleshooting when I have some time. I think the HBA is stopping the system from getting to lower C states, so may swap out for a ASM1064 based card in the future and check things out with powertop.8 points
-
(chuckling at the irony of some of these people who illegally download movies they didn't pay for, complaining that software they already own that isn't changing, but new purchases will incur potential recurring fees to support further development of the platform they love, use, and, again, already own and will continue to receive the benefits of using at no additional cost.) Seriously folks, it's a standard, common sense practice for mature software to have recurring fees to sustain continued development. If it didn't, once you hit a market saturation point for your product, you essentially can only cover maintenance but no other development (or get in the business of harvesting your existing user base's personal information to sell to third parties.) Some of you complaining would be shocked to learn that there are many of us that pay hundreds every year for updates to other software companies we use and need. From audio and video editing, to network licensing. I do. I just did 2 weeks ago! But I evaluate if the new features in that next version are worth it, or skip a generation. Now, with all that said, I will honestly admit that the little cheapskate in me doesn't like any increase on anything ever! Even if I can rationally justify it. And that's because nobody really wants to gleefully pay more for anything. I hear you. I feel you. I started out like some folks cobbling together hardware and sketchy drives to make my first server. Many of you are probably still in this stage. But 8 years later, and after numerous sever interactions, I run 4 licenses now on solid hardware with solid drives [knock on wood.] If their newly announced model was implemented when I first looked around 8 years ago, it would have given me the same pause to consider it versus alternatives. I would have still tried all the other free operating systems like I did. But I think in the end, I would have still picked Unraid for its ease of use, ability to run on a wide range of hardware, and community support. I think that it's ridiculously generous that Unraid has stated that they will grandfather previously sold licenses to have continued updates. Some of my licenses are 7 or 8 years old, and I'm still getting new features, new patches, and more. There is no other software that I own that has done that beyond a few years. This is why I have recommended this os, and will continue to do so. I'll just tell people to suck it up and buy the lifetime upfront, as it'll pay for itself over time, and give the dev's the ability to do more sooner. --- as a postscript, don't reply to me with nonsensical arguments or how it "costs a month's worth of food" replies. I'll just ignore them. This software is a luxury, not a necessity. If you are having to make the decision between eating versus storing more data than the average pc can do, then the solution is simple; go use a completely free os and stop making irrelevant arguments.8 points
-
3.7.24 Update: Caveat Emptor: Multiple users have run into GUID conflicts with these devices. I will attempt again to contact Eluteng and ask about this to see if this was a recent manufacturing change or a one-off "bag batch". Another option/alternative to USBs that we've been internally testing and vetting are mSATA adapters/drives: This USB mSATA adapter (~$10) appears to provide unique GUIDs for Unraid: https://www.amazon.com/gp/product/B07VP2WH73/ This 32GB mSATA drive works with the above adapter (~$15): https://www.amazon.com/gp/product/B07543SDVX/ To avoid having the adapter hang off the back of the machine, these can allow you to mount it inside your case (depending on your system): https://www.amazon.com/gp/product/B000IV6S9S/ https://www.amazon.com/gp/product/B07BRVBQVW/ Important notes/caveats: The mSATA drive does not come pre-partitioned, so you have to create one yourself. Windows sees it as a hard disk, not a removable drive, so the USB Creator might not write to it and you may need to use the manual method. The USB Creator worked fine from a Mac for me. While we're not officially officially recommending these just yet, multiple members of the Unraid team are running OS instances off of this exact set up. We hope to have a full blog/video on this alternative soon. You can use them for Unraid VMs too, just be sure to configure "USB 3.0 (qemu XHCI)" in the VM template (even if the host only has USB 2 hardware!). As always, if you are running the same make/model of drive for both the host and the guest you will need the "USB Manager" plugin to pass the drive to the VM. Major props to @AgentXXL over in our Discord server for doing much of the early testing on this.8 points
-
This has nothing to do with anything. As a matter of point, the installation URL for CA to run on 6.11.x is publicly posted in the CA thread (and is also a recommended post), and all of the downloaded data files remain fully compatible with that version. No further updates to CA running on 6.11.5 which is pretty much the same as no further updates to 6.11.5 will happen since 6.12.0 was released. There came a time when a major overhaul of CA dictated the either I spend forever debugging all of the necessary compatibility for an OS version which had already been supplanted. I chose to drop compatibility going forward, but make damn sure that all 6.11 users weren't out of luck. Similar thing happened when I've previously dropped compatibility for everything pre 6.1, everything pre 6.5, everything pre 6.9 on various releases of CA. If I had to maintain compatibility today with 6.0.0 then trust me CA would not be anything like what you're seeing on 6.11.x I don't drop compatibility for no reason. It only gets dropped when the gain isn't worth the pain8 points
-
Thanks for the update. Pretty much what I expected from LT, support for existing community. You all haven't let me down yet.8 points
-
After seeing your request to JonathanM, I created my own design which I am happy to share. It does not have any markings or trademarks, but it does have around 350 diamond-shaped ventilation holes for cooling. I've uploaded the .stl files to Thingiverse along with some images, notes, and settings. You can download the files and read more design here: https://www.thingiverse.com/thing:6520361 I hope that folks find it useful.7 points
-
Because a lot of us have been bitten by the 'boil the frog' type of transitions.7 points
-
7 points
-
7 points
-
Yep, sure was hidden. Right there in the files accessible to anyone running Unraid. I'm shocked it was found.7 points
-
Not all quacks are ducks... but the recent docker vulnerability kinda forced our hand to get 6.12.8 released ASAP.7 points
-
Great to see a more sustainable model coming out and a long life ahead for unraid. New terms are more than fair to the existing community and better than could reasonably excepted. Kudos, thank you for a great product and being an even better custodian. 🏆🏆7 points
-
If you make this a subscription service you've lost a customer.7 points
-
Wilkommen im Kurs: DataCollector nimmt sich wieder zu ernst und meint etwas helfen zu können. 😅 Und mal wieder ein Thema, das in der letzten Zeit ab und zu auftauchte. Bevor nun jede gute Seele das immer wieder von vorne schreibt, dachte ich mir, daß ich das mal zusammenkritzele. Stand: 12.03.2024 und betrifft die vermutlich alle unraidversionen. Aber in Wirklichkeit kenne ich nur unraid ab 6.9.x bis aktuell 6.12.x und da trifft es zu. Da man die unraid GUI Oberfläche auch durch andere Sprachpakete anpassen und man auch die Farben manuell verändern kann, beziehe ich mich hier auf die default englischsprachige GUI Oberfläche (egal ob gebootete GUI direkt am PC oder WebGUI). Definition: Dies hier hängt zusammen mit klassischen Festplatten mit in sich drehenden Plattern und beweglichen Köpfen, da dies dort am wichtigsten ist und die größte Stromersparnis im idle Zustand bewirken kann. SSDs lassen sich auch damit steuern, aber es hängt stark von der Firmware der SSD ab, ob diese das auch wirklich mitmachen oder einfach ignorieren. Übliche SSDs sind aber von Natur aus (fast) alle auf Stromsparen in idle getrimmt, weshalb sich das dort kaum auf den Strombedarf auswirkt (und eben deshalb vielleicht ignoriert wird?). Ausnahme sind überwiegend Enterprise-SSDs. Die haben gelegentlich nicht die selben Stromsparmechanismen und halten des öfteren einen PC sowieso unnötig 'wacher' als erforderlich. Zuerst: Man kann in unraid einstellen, wann (sich langweilende) Festplatten die Platter stoppen. Dies nennt sich 'spin down' und ist wohl die sparsamste Betriebsart einer Festplatte, wenn man mal von 'PC Abschalten' absieht. 🔌 Natürlich dauern dann erneute Zugriffe auf die Festplatte einige Sekunden, weil eben die Platter wieder die richtige Rotationsgeschwindigkeit erreichen müssen, damit die Festplattenköpfe ihre korrekte Flughöhe einnehmen und dann loslegen können. Pauschal wird pro Festplatte von rund 30 Sekunden Aufwachzeit geschrieben, wobei das in Wirklichkeit von Modell zu Modell leicht abweichen kann. Zu finden ist diese Einstelloption einmal zentral für alle Datenträger unter: Settings / Disk Settings / "Default spin down delay" Man kann aber auch für einzelne Datenträger dies individuell anders einstellen indem man beispielsweise unter: Main / Disk<Nr> / "Spin down delay" für diese gezielte Festplatte <Nr> extra konfiguriert. Wenn man es will kann man Datenträger auch manuell sofort anstoßen sich schlafen zu legen oder aufzuwachen indem man auf den kleinen Kreis links des Datenträgers klickt. Ist der Kreis grau schläft die Festplatte. Ist der Kreis grün dreht die Festplatte. So, num zum eigentlichen Thema: Warum schläft meine Festplatte nicht? SAS: Ein Punkt ist mir recht früh aufgefallen: Sollte man SAS Festplatten verwenden gibt es so einige Kontroller-Festplattenkombinationen, die das einfach ignorieren. Es gibt ein extra Plugin (SAS Spindown), welches dann doch einige SAS Festplatten dazu überreden kann, aber auch das wirkt nicht bei allen SAS Geräten. SATA: Hier kenne ich keine Einschränkungen, weshalb ich sage, daß sich direkt angeschlossene SATA Festplatten eigentlich immer in den "spin down" bringen lassen. Warum klappt das also nicht? In allen Beiträgen, die ich bisher las, lag es daran, daß auf den Festplatten noch Reste von oft angesprochenen Shares (Verzeichnissen) vorhanden sind und Zugriffe darauf eben die Festplatte entweder sofort wieder aufweckten oder gar dem Befehl zum "Spin down" so schnell wiedrsprachen, daß die Festplatte einfach weiter läuft. Nun ist man aber vielleicht der festen Überzeugung, daß man doch alles getan habe um die Shares auf einem Pool/Cache/SSD auszulagern und dennoch die Festplatten weiter drehen. Tja, es hat sich eigentlich immer gezeigt, daß da etwas übersehen wurde. Sofern ein Array mit Parity betroffen ist, kann das Verhalten der Paritydisk(s) Aufschluß über die Art der Zugriffe bieten. Wenn die Parity schläft, aber eine oder mehrere Datenfestplatten nicht einschlafen sind es lesende Zugriffe. Wenn die Parity auch aufwacht/wach bleibt sind es schreibende Zugriffe. Zu beachten: unraid hat 4 wichtige shares, ich nenne sie systemshares: appdata - hier finden sich Teile von Docker domains - hier befinden sich Virtuelle Disks von VM isos - hier werden ISO Dateien abgelegt (selten im Zugriff) system - hier finden sich auch Teile von Docker und libvirt Hier greift unraid drauf zu, wenn die Docker und VM Dienste benutzt werden. Um zu prüfen ob die wirklich alle richtig lokalisiert sind sollte man in der GUI unter shares / 'compute all' anklicken. Nach kurzer Recherche sieht man dann auf welchen Datenträgern sich diese Shares verteilen. (Links ist der Datenträger unter dem jeweiligen Share zu sehen und rechts, wieviel Platz das Share dort belegt.) Wenn die Festplatten schlafen sollen, ist es sehr zu empfehlen alle diese 4 Systemshares auf einen Pool/Cache/SSD zu verlagern. Selbst ein absolut leeres Share auf einer Festplatte kann dafür sorgen, dass das "Fuse" Dateisystem dennoch ab und zu dort nachsieht, ob da nicht doch zwischenzeitlich was drin ist und deshalb springt die Festplatte immer wieder an. Nachdem man dafür gesorgt hat, die Systemshares von den Disks weg auf den Pool/Cache/SSD zu verlagern, sollten die Festplatten sich dann auch wirklich schlafen legen können, selbst wenn Docker und VM laufen. Nebenbemerkung: Natürlich ist es dann ungeschickt, wenn man dennoch in einer VM oder Docker einen direkten Pfad angibt der dann beispielsweise downloads doch auf die Festplatte schreibt. Denn dann halten nicht die systemshares die Festplatte drehend, sondern das was man da manuell eingestellt hat und gerade durch die VM/Docker angesprochen wird. Falls man sich nicht mehr dran erinnert, was da schreiben könnte kann man beispielsweise mit dem Plugin "File Activity" sich eine Liste der Zugriffe auflisten lassen. Anhand der dort gelisteten und betroffenen Dateien sind dann Rückschlüsse möglich. USB: Warnung: Igitt! USB Festplatten/SSD sind im unraid Array nicht wirklich empfohlen und immer wieder ein Quell der Probleme (vielleicht nicht zu Anfang aber dann doch des öfteren später). Es gibt Berichte, bei denen USB Datenträger seit Jahren problemlos im Array funktionieren, aber seid gewarnt: wenn etwas schief geht, habt Ihr es gewusst und Euch gezielt dafür entschieden. In diversen Fällen ist dann Hilfe kaum möglich. Zum Thema: bei USB Festplatten hängt es stark von der Firmware in der USB-SATA Wandlerplatine ab, ob sie die daran verbaute Festplatte von einem PC dahingehend steuern läßt oder nicht. Bei vielen moderneren externen Gehäusen klappt es, auch externe Markenfestplatten machen das meist mit, aber wenn nicht: Pech gehabt. Mißverständnis S.M.A.R.T.: Gerne ist ungefär sowas zu lesen: "Meine Festplatte wird durch Abfrage der SMART-Attribute aufgeweckt, das habe ich im Syslog auch gesehen". Seid versichert, das ist nicht so. Es ist genau anders herum. Wenn eine Festplatte aufwacht, versucht unraid zu aller erst diese SMART-Attribute abzufragen. Und genau deshalb sieht es im Syslog so aus, als wenn diese SMART Operation für den "Spin up" verantwortlich sei. Irgendetwas anderes hat die Festplatte aufgeweckt und dann hat unraid sofort gelesen. Wenn man nicht weiß was es war: auch hier könnte das Plugin "File Activity" helfen die Dateien herauszufinden und daraus zurück zu schließen, wer oder was der Verursacher ist. So, mehr fällt mir jetzt nicht ein. Have a nice day with unraid!6 points
-
On this very special episode of the Uncast Show, we are joined by the Founder and CEO of Lime Technology, Tom Mortensen @limetech, and Co-CEO Tiffany Jones @tiffanyj to talk about the origins of Unraid OS, the evolution of the product over the past 18+ years, and some upcoming changes to the company to better align the product and user's desires in Unraid 7 and beyond. Tom and Tiffany share their personal career journeys and take us down memory lane as Unraid incorporated VMs and Docker containerization, GPU passthrough (a decision that dramatically shifted the course of the company with Linus Tech Tips), made key hires to expand the team, and talk about some key projects and initiatives that got the company where it is today. The conversation shifts gears to the future and goes into the upcoming changes to Unraid's pricing model for new licenses and why this change is crucial and necessary for sustaining the company and improving the product for all in the years to come. Please refer to our blog for full details on the upcoming pricing change. Wrapping up the episode, we'll get a first look at Unraid 7 and explore some exciting future OS features and projects such as making the unRAID array optional, integrating and maintaining plugins into the OS, VM Snapshots and cloning, the "Hardware Database," the "My Friends Network," a new Unraid website, a public, open-source Unraid API and much, much more. We truly hope you enjoy this episode.6 points
-
6 points
-
After re-reading the post, I think this comes down to how the announcement was worded - calling it a 'subscription' I don't think is quite right, as that term infers 'rental' in most people's minds. If instead they called it something like 'license support', that'd be more apt to have folks read it and have it reflect more of the ground reality I think...? @limetech I was talking to a couple friends of mine here at work (enterprise data mgmt), where we've just recently been undergoing much the same change in revenue models (one time vs recurring), and when they read the announcement I linked their way (because only a fraction of a percent will watch the full podcast), the first responses I got back were all some form of "the enshittification of all things tech continues, not shocked"... However after I explained a bit further (having listened to the podcast), they were much more amenable to the idea, and their only real issue was with the announcement itself for the most part. Some thoughts I'd had here: While I know that having time-based and calendar-locked recurring revenue makes things FAR simpler for all things fiscal (forecasting revenue, planning hiring, etc), I feel that the current sentiment towards such models is making this go down harder than is actually necessary. The way unraid handles releases is honestly a bit problematic for handling this any other way though, unfortunately (imo). There are often improvements/enhancements included with even point releases (which increases the potential for introducing new bugs), so there is no 'maintenance only' type of release. For example, 6.12's big feature was ZFS integration; but over the course of the last 8 point releases, we now have a new drivers page, new UI buttons to show/hide individual or all items at once, enhancements to package handling, etc. Some recommendations towards the above: I'd propose LimeTech create a software support lifecycle policy - e.g. each major release of UnRAID shall receive continued support (e.g. bug fixes and security updates) for X term (I've been seeing 18 months as fairly typical, but 12 isn't unheard of). This gives an actual cadence that customers can then plan against, as opposed to paying for a 'period of upgradability', a term during which they've no idea what releases may or may not come Charge by major release instead of based on time period - This way, there's no 'unknown' in the customer's mind as to what they're receiving for what they've paid; they know exactly how long they are going to get security updates for and for exactly how much. Only bug fixes allowed in point releases - Most mature software orgs I've worked with in the enterprise have a version schema something like "7.3.7-p3", where anything with the "-p#" is known solely to have included bug fixes found within that build (so for this example, 7.3.7 has had 3 bug-fix / security-patch releases). Since UnRAID doesn't follow such a schema, we'd instead have something like "6.13.2", where 6 is the major release (such as the big ZFS release), 13 is the minor/enhancement release (would include all the small enhancements normally in point releases currently), and 2 is the number of bug-fix/security-patch updates that it's received Possible LTS enabled by the above (oft req'd feature) - If moved to this new schema, Limetech could choose to finally implement the (seemingly heavily requested) option of an LTS UnRAID build (which would have to be an LTS kernel for it to make business sense to Limetech of course). Since you're charging based on the release, not the time window, you can opt to charge more for the LTS release in order towards offsetting the additional costs. Heck, you could even choose to do the time based revenue model initially proposed for these LTS releases, and since *no improvements* are included in point releases, this helps to mitigate some of the development overhead one might typically associate with such a strategy. I know that these proposals are a fairly high bar, and may even appear a bit daunting at first read... But much of the additional work that'd be required can be augmented by build automation tools. Argo or Flux CD could be built up to automate creating and validating these LTS point releases, for example, making maintaining two kernels far less painful than it otherwise could be. After the initial build-out's completed (and it'd take a little time there at least), it's associated costs effectively amount to a percentage of one DevOps guy's time thanks to the fact that much of the amazing features in UnRAID are plugin based (additionally helped further in that they're community supported). I've got about a thousand ideas for all of this, but that's mostly as it's the world I live in at work each day, and while I know this wasn't short (...lol...), I hope at least some of it is some-kind-of helpful! Sincerely wishing all the Limetech folks the best as you're going through this transition 👍6 points
-
I was now able to activate ASPM for Realtek Network Devices again with 6.12.8 by activating ASPM manually. This commands I used: sudo setpci -s 00:1c.0 0x50.B=0x42 sudo setpci -s 01:00.0 0x80.B=0x42 For at least 2 of my server it worked and the addresses between them are equal but you need to find out the right addresses for your boards by yourself. This article may help you (forget the script there, use the explanations how to find the correct adesses): Click Me If the systems are still stable we will see. I had not enough time to test it in detail. At least I´m in C8 again and don't stuck in C3. PS: I still expect a clean solution from Limetch with a new Unraid Release.6 points
-
Please watch this - The best explanation is here in this really nice video interview With Tom the Founder & his Daughter who is co-ceo. Basically extra money is needed to help bring on new team members & help further development. They want to continue serving the community and not seek venture capital etc. They talk about how they would like to use more community developers for little projects. And how moving to this new business model will work both ways as people have the choice to pay or not and so this means they have to bring features that people will pay for. So exciting. After watching the video, hearing the history & realising it is a family run business - I am feeling better about the future of unraid.6 points
-
If anything, it makes it seem more likely that Unraid will be able to continue.6 points
-
This was a function being developed for the next release but was decided best to be a plugin to start with to allow better interations for changes. Currently this is a beta release. the is an existing plugin called virtwold this expands on it to include dockers and LXC. I am in the process to complete changes to make it work fully under 6.12 but currently the search function and help text don't work or don't exist. Two pages are created, first is the settings. Within the settings you can specify which servers are enabled. The interface name needs to be a physical NIC. By default shutdown actions are disabled. The second page is in tools. It allows you to specify the actions allowed. To be able to start dockers you need to have a user defined mac address as one is not assigned until the docker starts and changes. Values for the enabled field are5 points
-
There has never been a promise that prices would remain fixed forever. The prices for nearly everything has gone up. We are not immune to that. But, you do have a chance to buy now and be immune from these prices changes.5 points
-
Update: We've added additional info around the upcoming changes via some FAQs taken from the community: https://unraid.net/blog/pricing-change5 points
-
5 points
-
An alle hier im Thread: Es gibt noch nicht viel von Offizieller Seite, es gibt nur eine Bestätigung das eben das Lizenzmodell umgestellt wird und das es dann: Updates auf Zeit gibt <- BTW das ist kein Abo wenn man seine alte Version nutzen kann selbst wenn man nicht mehr bezahlt einziges manko ist eben das man dann keine Updates mehr erhält, aber das ist ähnlich wie bei Windows das ist auch kein Abo und irgendwann gibts keine Updates mehr (bitte keine Diskussionen diesbezüglich das soll nur ein Beispiel sein) Eine Lifetime Lizenz so wie die Pro version jetzt Ich würde mal noch ein wenig abwarten bis es das nächste Statement von Offizieller Seite gibt, ich vermute mal das der Leak intern die ganze Planung durcheinandergeschmissen hat und dort alle mit Hochdruck dran arbeiten alles aufzuklären. Es gibt auch einiges vom Podcast das herauszufinden ist: Der Podcast ist von November/Dezember sprich die Umstellung des Lizenzmodells ist vermutlich schon länger in Planung und sowas braucht einfach Zeit Neue Website: ich vermute das die neue Website noch nicht fertig ist und somit auch das neue Lizenzmodell noch nicht auf der Website vorhanden ist aus genau diesem Grund Die Updates auf Zeit sollen günstiger werden selbst die initialen Kosten Für bestehende Lizenzen ändert sich nichts egal welche Version man bereits gekauft hat Limetech will expandieren, Features ausbauen bzw. hinzufügen und genau das mit den neuen Änderungen erreichen um Cash Flow zu garantieren (find ich auf der einen Seite auch gut das es nicht so gemacht wird wie bei Windows und alles zugepflastert wird mit Bloatware und Werbung <- das wäre sicher auch möglich gewesen) (die Punkte die ich oben Aufgelistet hab sind selbstverständlichen nur sachen so wie ich sie verstanden hab und interpretiere) Ich bin auch froh das der Leak nicht zur folge hatte das das Lizenmodell gleich umgestellt wurde und alles gleich in kraft tritt. Leaks sind nicht immer gut... Wenn ich noch was vergessen hab bei den Punkten vom Podcast lasst es mich wissen und ich füge es hinzu.5 points
-
For what it's worth, we're over a year away from this being a possible problem, and folks are already looking at how the app/plugin system can accommodate users that decide not to update.5 points
-
5 points
-
I am going to hide these just to stop the reports from coming in.5 points
-
Needed money, developing and maintaining a software like that is not cheap5 points
-
One of the main reasons I suggest users to upgrade is so the community can support them. We can't keep running old versions just so we can help people that won't upgrade.5 points
-
One question, on the yearly supported keys. Will these still include security fixes/patches for the OS if your year has expired? I can understand not getting feature updates/upgrades beyond that but being an entire OS security fixes would be important5 points
-
I'm on unraid due to the one time cost and the community. Given the bugs and issues I've had, I would be leaving in search for something different if a subscription does happen. I would not have even considered unraid if it did have a subscription. Seeing how alot of it is run by the community now, it definitely does not sit right in any way. Even as we speak here, there are multiple threads on reddit proposing alternatives-on the unraid subreddit. I'm looking for them now as if 7.0 does cost more, especially reoccurring, I see little reason why not to go and try all other big name alternatives, again.5 points
-
I think subscription model makes sense from a business point of view but it all depends on the price.. Self hosting is usually to avoid subscription fees. I have paid for PRO. So if moving to yearly fees I'd also be expecting a more polished user experience so they would need to provide more and not just rely on the community plugins. For example more focus on low power use & better fan control. Perhaps an undated GUI experience which I think is planed. Better documentation or at-least willingness to merge the requests that people submit. The unraid policy will need updating to reflect the extra information that is sent when updating - https://unraid.net/policies Unraid is definitely the simpler server software out there & I'd like to carry on supporting unraid. ("Extend License"),title:tee.t("Pay your annual fee to continue receiving OS updates.")}),eee)})) Just say x is x instead of x is y.5 points
-
I think the terminology should be changed from Subscription pricing to Update pricing as it better reflects what is being proposed and has less negative connotations for most people4 points
-
Hallo zusammen, Nachdem ich als Unraid & Docker-Anfänger erst selbst vor dem Thema stand wie man in Unraid PiHole / Adguard & Unbound installieren könnte, hier die Schritte, die bei mir gut funktioniert haben. Vielleicht hilft es dem ein oder anderen bei dem eigenen Setup - Ideen zur Verbesserung, Tipps, Korrekturen usw. sind natürlich immer gerne gesehen Grundsätzlich gibt es verschiedene Kombinationsmöglichkeiten, weshalb ich die Beschreibung auf verschiedene Teile aufbreche damit es übersichtlicher wird. So kann man nach eigener Präferenz dann PiHole oder Adguard mit Unbound kombineren. Übersicht: Hintergrundsdetails & Vorbereitung & Test- und Erweiterungsmöglichkeiten Setup von PiHole Setup von Adguard Home Optionen zur Bekanntmachung des PiHole / Adguard Home im LAN Setup von Unbound PiHole & Unbound Adguard Home & Unbound Filterlisten hinzufügen Stand 2024-02-23 läuft es auf: Unraid 6.12.8 / PiHole 2024.02.0 / Adguard 0.107.44 / Unbound 1.19.0 Hintergrundsdetails zum Verständnis Was machen eigentlich PiHole & Unbound genau? >Klick< Was ist DOT / DOH / DNSSEC und was bringt es? DNSSEC: Gewährt Authentizität & Integrität der DNS Abfragen >Klick< DOT / DOH: Gewährt Vertraulichkeit durch Verschlüsselung der DNS Abfragen >Klick< Rekursiver DNS: Gewährt Privatsphäre (Data Privacy) durch die rekursive Durchführung der DNS Abfragen >Klick< Ich habe mich entschieden PiHole bzw. Adguard und Unbound getrennt laufen zu lassen, da man damit zum einen schneller die jeweils neuste Version erhält und zum anderen, damit man einen Einblick (und damit Kontrolle) über das Setup behält Die Docker-Container laufen mit eigenen IPs auf dem br0 Netzwerk. So kann man bspw. den PiHole einfach gegen Adguard tauschen und braucht die Unbound Installation an sich nicht ändern. Oder man nutzt nur Unbound ohne PiHole oder oder oder.. Durch die Nutzung von eigenen IPs pro Docker per br0 hat man keine Probleme mit doppelt belegten Ports (in diesem Fall dem Standard-Port 53 für DNS von PiHole, Adguard als auch Unbound) In den Screenshots ist mein lokales Netzwerk, also die 192.168.0.x, abgebildet. PiHole läuft bei mir also auf der 192.168.0.5, Unbound auf der 192.168.0.6, Adguard Home auf der 192.168.0.4 Die IPs müssen entsprechend eurem lokalen Netzwerk angepasst werden Bei einer Fritzbox ist das Standardnetz idR. die 192.168.178.x IPv6 habe ich im lokalen Netz in meinem Router komplett deaktiviert, da die "reverse" Namensauflösung von lokalen Adressen zu Gerätenamen im PiHole (unter "Conditional forwarding") mit ipv6 bei mir nicht funktioniert hat. Die reine Funktion als DNS sollte jedoch auch mit IPv6 funktionieren und kann, wenn benötigt, an verschiedenen Stellen in der Konfiguration aktiviert werden PiHole kann DNSSEC (kann im Webinterface aktiviert werden), was wir jedoch nicht benötigen, da die eigentliche DNS Abfragen von Unbound (sollte automatisch DNSSEC machen) durchführt werden. Ebenso braucht man bei Adguard Home DOT & DOH meines Wissens nach nicht aktivieren, da es nur für die Strecke bis zum Unbound aktiv wäre Unbound an sich ist ohne weitere Änderungen so konfiguriert, dass es die DNS Abfragen per DOT an einen Cloudflare DNS Server weiterleitet. In dieser Anleitung geht es jedoch explizit um die Konfiguration als rekursiven DNS Resolver, wodurch eine kleine Änderung an der Konfiguration notwendig wird Als Rekursiver DNS Resolver macht Unbound zwar DNSSEC aber DOT/DOH ist aktuell nicht gleichzeitig möglich. PiHole & Adguard können Ads auf Youtube aktuell (leider) nicht blockieren, da die Ads von den selben Servern stammen, wie das eigentliche Video. Hierzu empfielt es sich zumindest am Mac/Pc zusätzlich bspw. UBlock als Addon im Browser zu installieren Mit "dig" kann man auf der Unraid-Kommandozeile direkt testen, ob PiHole / Adguard / Unbound funktionieren, bevor die Systeme miteinander verbunden werden und ohne die Änderung an das komplette lokale Netzwerk zu verteilen. Alternativ kann man es auch von einem anderen Computer in eurem LAN testen: Auf Win10/11 über ein "nslookup www.heise.de <IP_von_PiHole/Adguard/Unbound>" auf der Kommandozeile Auf MacOS über ein "dig www.heise.de <IP_von_PiHole/Adguard/Unbound>" auf der Kommandozeile Vorbereitung Als Vorbereitung für die Nutzung der DNS Tests per "dig", ist in den Unraid Einstellungen unter "Settings" -> "Docker" -> "Host access to custom networks" auf "enabled" zu setzten. Das sollte dann so aussehen (mit euren eventuell dort zusätzlich durchgeführen Änderungen & LAN Einstellung für Docker) Nach den Tests kann es wieder deaktiviert werden, wenn ihr es nicht für andere Sachen (Stichwort Erweiterung Wireguard) benötigt. Die Verbindung zu und zwischen PiHole / Adguard & Unbound funktioniert auch ohne dem Host (in dem Fall also Unraid an sich) Zugriff auf das br0 Netzwerk. zu geben. Testmöglichkeiten Nach den erfolgreichen Tests mit "dig" und der Verknüpfung von PiHole / Adguard mit Unbound stellt sich die Frage, ob es denn nun funktioniert. Da ja (hoffentlich) alles "einfach" funktioniert, hier ein paar Links, welche bei diesen Tests helfen: https://d3ward.github.io/toolz/adblock oder https://fuzzthepiguy.tech/adtest/ Testet die Ad-Lists in PiHole / Adguard durch verschiedene bekannte Ad-Seiten. Je nachdem wie umfangreich eure Listen sind, sollte alles geblockt werden. Für einen ersten Eindruck ok aber wichtiger ist, wie gut Werbung auf den von euch besuchten Webseiten - also in eurem Alltagsgebrauch - geblockt wird https://www.ipchicken.com Zeigt die eigene IP an, welche wir bei den nächsten Tests nutzen können https://internet.nl/connection Grundlegende Details zu ipv4 / ipv6 & DNS. Hier taucht die eigene IP als DNS Server auf, da wir Unbound als DNS selbst betreiben. DNSSEC sollte positiv sein https://www.perfect-privacy.com/en/tests/dns-leaktest Zeigt den genutzten DNS Server an. Dies sollte wiederum die eigene IP sein, da wir Unbound als DNS selbst betreiben https://0skar.cz/dns/en/ Testet explizit DNSSEC und sollte mit Unbound alles positiv sein https://www.grc.com/dns/Benchmark.htm Interessantes Tools für DNS Benchmarks. Da wir mit Unbind einen eigenen rekursiven Resolver haben, sollten wir beim ersten Durchlauf langsamer sein, als so mancher Public Resolver wie 1.1.1.1 oder 8.8.8.8. Der zweite Durchlauf ist möglicherweise schneller, da die Test-Daten bereits im Cache beim PiHole / Adguard / Unbound liegen. Durch die rekursive Abfragen und die DNSSEC Validierung sowie das Adblocking, wird das eigene Setup jedoch immer etwas länger (im Millisekunden Bereich) für eine DNS Anfrage brauchen, als eine Anfrage direkt an einen Public Resolver. Im Alltag sollte dies jedoch nicht bemerkbar und mit Blick auf die Vorteile akzeptabel sein Erweiterungsmöglichkeiten Eine Erweiterung des PiHole/Adguard & Unbound durch Unraids Wireguard-VPN bspw. um das Handy unterwegs per VPN anzubinden und über den durch den eigenen, optimierten Internetzugang zu schicken, bietet sich an. Ich habe hierzu die folgende Anleitung genutzt >Klick< Meiner Erfahrung nach ist hierbei zu beachten: Der IP Bereich eures lokalen LAN sollte nicht den typischen LAN Vorgaben entsprechen und bspw. auf 192.168.0.x umgestellt werden. Damit beugt ihr vor, dass wenn ihr euch mit eurem Handy gerade bspw. im WLAN eurer Freundin/Oma/Kumpel.. befindet und diese die selbe IP Range im (W)LAN haben wie ihr daheim, es zu Routing Problemen mit eurem VPN kommt. Das heisst einmal den DHCP & LAN Settings in eurem Router anpassen In der Konfiguration von Wireguard ist die IP von PiHole/Adguard als DNS einzutragen Der "Host access to custom networks" in den Docker Settings von Unraid muss auf "enabled" stehen, damit Wireguard mit diesen sprechen kann Für den Zugriff eurer Geräte aus dem VPN auf lokale Geräte (PiHole/Adguard Oberfläche..) ist im Router noch eine manuelle Route notwendig, damit der von Wireguard genutzte IP Bereich (10.x.x.x) mit eurem lokalen LAN (192.x.x.x) sprechen kann. Das sollte dann so aussehen:4 points
-
As a relative newcomer to unraid, I see the tremendous value it offers, but I do have to admit that I would have been turned off by a recurring pricing model and would not have been as eager to jump in to this ecosystem if this were on the radar. This is already paid software in a market against free options (OMV, TrueNas) so I don't believe you're going to win additional users over on this. You're also getting very biased feedback on this forum because the only people who are here largely already own a license, so they don't have a stake in this, as they'll be grandfathered (until this changes, which it probably will, let's face it, every time this happens, it comes to a point where the grandfathered tier ends too) This is why the coverage on reddit is less favorable. These are potential unraid subscribers saying "I don't think this works for me" - these are the voices we need to listen to, because, guess what, if you can't bring in the new subscribers to drive your cash flow issues, it'll be even sooner that you need to cannibalize your grandfather tier to meet the payroll demands. Now, don't get me wrong, I understand that folks need to get paid and that a reliable revenue stream is a necessity, I don't hold this against you, but I do feel very conflicted about how you're choosing to go about implementing this, because there is a solid lack of information on whether security/bug fix/data loss updates will be applied for new users once this licensing goes through. Given that we've only recently discoved a long-standing major zfs bug in the last few months, the idea that extremely critical data loss vulnerabilities will go unpatched for users after a year is a disappointing choice, not a small "detail" as it's been expressed in prior posts. I can guarantee you that once the licensing changes solidify, that the first time there's a major vulnerability, it will blow up everywhere, get carried by all the tech media, flood the support forums - that will eliminate any goodwill that would drive new butts into seats. If the new licensing scheme doesn't readily attract users, the change is all for naught. I'm monitoring this cautiously, but I'd like to strongly recommend that you clarify if security, bugfix and data loss updates are pushed for folks without a subscription. I can tell you now that if another long-standing ZFS bug comes out at a point in the future, and there's an entire class of unraid users who need to re-up/pay to fix it (or worse yet, are left to feel like they have to pay to get support to recover data), they will loudly move to a different product, community support will eventually falter and this will just be another product that was good at one time. Also, I'm curious how much of a cash inflow you've seen now that there's a potential secondary market of folks buying basic keys en-masse to resell/hold their spot in the legacy tier as it will always be a better product than what you're providing now. By fudging this announcement, you've basically just designed a black market resale scheme for years to come. This is a problematic launch and a problematic idea, albeit for a good cause. Seriously disappointed.4 points
-
4 points