Leaderboard

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 6 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, Plus, and Pro keys; We will offer a new Lifetime license that will be more than a current Pro. 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.

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.

We need more of these.

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 🙂

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.)

It's amazing the amount of people that can't read.

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.

You clearly didn't make the effort of even reading the post you're replying to.

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.

@betaman@Elmojo, I know this is an 18 page thread right now, but I really, really recommend reading it all. Keep in mind the first few pages are teething issues with older versions of the software and getting it running in Unraid at all, so maybe just skim those, but really, I think reading through the whole thread will help to get some context on how things work. I currently have 10 different machines actively backing up to one of my instances, and over the years have done many file level retrievals both directly from the server UI and the client app. I've also done a couple bare metal restores to brand new drives that went flawlessly, all this over WAN, as the Unraid server hosting my UrBackup instance is 10 miles or more from all but 2 of the machines or VM's it's protecting. You can also set up UrBackup users with privileges to only manage the machines you assign to them, so when they log in to the UI they only see their backups. This really can be business level backups, I've totally replaced carbonite for several people and saved them a bunch of money, since UrBackup happily manages Microsoft Server products, where any of the cloud services charge big $$$ for their server tiers. The people I do this for know up front what building their data is in, and how it's protected, instead of trusting a faceless corp.

Was war denn an den Links und dem Blog in diesem beitran nicht offiziell genug?

Da man dann auf dem Schlauch steht, wenn Pihole mal abstürzt (unraid Probleme hat) habe ich den DNS (von adguard) nicht im Heimnetz, sondern als DNS Server der WAN Verbindung eingetragen. In der Fritzbox kann an dann darunter noch einen alternativen DNS Server eintragen, falls der Erste ausfällt. Auch braucht man dann nicht auf neue DHCP Zuweisung im lokalen Netz warten, weil die FB das dann sofort macht.

If anything, it makes it seem more likely that Unraid will be able to continue.

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 pain

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?

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 up

Hier überarbeitet ->

If people could read and search, this forum would have 80% fewer posts 😛

I hope it's not too off-topic, it's kind of related to licensing: When can we get rid of USB Key requirement!?!?!?! I hate it, it's the weakest, most annoying part of Unraid for me.

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.

Nein stehst du nicht. sagt er auch im offiziellen Video. Die Definition kommt zwar aus dem Finanzsektor, sollte aber dennoch klar sein: “Im Bereich der Finanzmärkte bezeichnet Grandfathering eine Situation, in der bestimmte Investoren oder Geschäftsmodelle ihre bestehenden Rechte oder Privilegien behalten dürfen, während neue Regeln oder Einschränkungen nur für zukünftige Aktivitäten gelten.“

Here you go.

Thank you @ich777 I have followed the steps to migrate from ich777 to giganode, everything still works fine. without having to reboot any device And Thank you @giganode that brings it into community applications, making it easily accessible to others

The plugin is the same and I'm still compiling the plugin packages for this new plugin for @giganode. Uninstall my plugin Shutdown all VMs Install the plugin from the CA App Recreate your VFs Check the configurations in your VMs if everything is correct Use as usual It is basically the same as you switched over first from the very first plugin to my plugin. The change was done since I don't have any hardware that supports Intel iGPU SR-IOV, this was also the reason why I haven't published in the CA App. Thanks to @giganode for his contributions and continuing with the plugin and support for the plugin.

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.

I guess that because they had to announce earlier than expected, there may still not be a firm date for the change, any keys bough now will be under the current model, including activation keys, and they can be activated later. Yes, that's answered in the first post.

Das script funktioniert nicht. Aber das Prinzip dahinter vielleicht. Sprich via setpci ASPM manuell aktivieren. Ich hab die Adressen mal rausgesucht und teste das gerade. Dazu müssen folgende Befehle ausgeführt werden: sudo setpci -s 00:1c.0 0x50.B=0x42 sudo setpci -s 01:00.0 0x80.B=0x42 Diese zwei Befehle aktivieren ASPM für das PCIe Device und den Realtek Netzwerkchip. Sie sind auch nur für das N100DC-ITX und können bei anderen Boards anders aussehen. Ob das System durch instabil wird konnte ich noch nicht testen. Aber zumindest zeigt: lspci -vv | awk '/ASPM/{print $0}' RS= | grep --color -P '(^[a-z0-9:.]+|ASPM )' ASPM ist aktiv. Das System geht in C8: Das ist alles unter Unraid 6.12.8 Ich konnte noch nicht testen ob das ggf. zu instabilitäten des Systems führt. Gruss, Joerg

Reddit is a slum now. Don’t care about them at all anymore. I suggest you delete them as well. You’ll be happier.

What CD said. You can't sell perpetual licenses WITH baked in upgrades forever. Back in the day, you would buy "Productivity Software '92" and get upgrades to '92 until '92 was dropped from support. At that point, you could either a. Continue using it as it drifted further from current software and became more insecure. b. Pay to upgrade to Productivity Software '95 and start the cycle over again. or c. (usually in enterprise) pay for a perpetual license and then pay for maintenance which authorized you to upgrade and get more support. Moment you stop paying, you're stuck on the major version you're on. Eventually option d. Subscription came out and gradually became the standard. Why? Lower upfront costs gets more people in the door, the cost can be better calculated and budgeted for and the companies themselves don't need to "sell" all the time. The model being implemented here is 100% NOT a subscription model. It is option C. A perpetual license with a year of maintenance. This does allow users to make their own judgements on when to pay. Year is up, nothing new on horizon I need, wait to pay for maintenance until I have a compelling reason to upgrade, then get year of updates to catch up. This would be like having Photoshop 2, skipping 3 and upgrading to 4. We'd all love to get everything forever for free, but that's not how it works. This is the best (or least worst if you prefer) option that provides revenue to Lime, while taking care of everyone. And as long as it isn't 10 times the price for a pro license, you can still pay to not have to think about it. And many companies will because of the difference between capitalized vs. expense. Obviously ALL of this goes out the Window if the grandfathering and new Pro Licenses go out the Window, but the fact that LT is planning to continue to sell new Pro licenses indicates that such a change is not coming anytime soon. Doing that would open one up to litigation.

I am going to hide these just to stop the reports from coming in.

I think this is fine, just don't announce you're being acquired by Broadcom next week!!

Yep, sure was hidden. Right there in the files accessible to anyone running Unraid. I'm shocked it was found.

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.

Does this include unRAID 7.0 and other such future major versions?

My sugestion and i think one of the must important updates to VM's in Unraid:

Hello, Here is the current Diagnostics. qnap-diagnostics-20240220-2218.zip

Thank you JorgeB

Yes, I did that but had to use -L to fix it. It's all working now Thanks

I wanted to follow up on this. The disks were absolutely fine and the HBA being too hot was the issue. My solution in this case was to remove the heat sink on the HBA, re-paste the sink with new thermal compound and then re-attach the heat sink using 25mm Nylon bolts and nuts with a 40mm Noctua fan going on it. This has the card nice and cool and I was able to re-add the same disks back to the array with no issues aside from a 3 day rebuild time. So yes, heat is an issue on these HBAs designed for high-speed air movement in a rack mounted system when not getting the air it's expecting. Cool those cards people.

the people that are complaining are probably still running windows 3.1.1 because they have to pay to upgrade to win95 🤣 I have been running unraid for 12 years or something like that since the 3.xx/4.xx days and this is the first time I can remember that they changed anything. unraid will always have my support, great community and it's rock solid.

Best episode yet, of interest to all Unraid users. Don't know why Tom would rather time travel to the past though. The future (of Unraid) looks brighter than ever!

If you make this a subscription service you've lost a customer.

I appreciate the communication coming out now, but I think I speak for most of us when I say, I wish this had come before the software release. My only question is surrounding the guarantee Limetech are making towards future of "lifetime" (including existing basic/plus/pro) customers. Is there a genuine commitment towards existing customers retaining a perpetual license for all future Unraid versions, or is there a chance that Limetech have an expectation of a small upgrade fee in the case of major upgrades? I understand that you cannot talk from an absolute 100% basis, as who knows what the future will bring, but I would just like to make sure the foreseeable future has no plans for this, and if there is, that we are at least informed of it.

Thanks for the update. Pretty much what I expected from LT, support for existing community. You all haven't let me down yet.

6.12.7-rc2 As before, will update as we go along. 6.12.10 # ------------------------------------------------- # RAM-Disk for Docker json/log files v1.6 for 6.12.10 # ------------------------------------------------- # check compatibility echo -e "8d6094c1d113eb67411e18abc8aaf15d /etc/rc.d/rc.docker\n9f0269a6ca4cf551ef7125b85d7fd4e0 /usr/local/emhttp/plugins/dynamix/scripts/monitor" | md5sum --check --status && compatible=1 if [[ $compatible ]]; then # create RAM-Disk on starting the docker service sed -i '/nohup/i \ # move json/logs to ram disk\ rsync -aH --delete /var/lib/docker/containers/ ${DOCKER_APP_CONFIG_PATH%/}/containers_backup\ mountpoint -q /var/lib/docker/containers || mount -t tmpfs tmpfs /var/lib/docker/containers || logger -t docker Error: RAM-Disk could not be mounted!\ rsync -aH --delete ${DOCKER_APP_CONFIG_PATH%/}/containers_backup/ /var/lib/docker/containers\ logger -t docker RAM-Disk created' /etc/rc.d/rc.docker # remove RAM-Disk on stopping the docker service sed -i '/tear down the bridge/i \ # backup json/logs and remove RAM-Disk\ rsync -aH --delete /var/lib/docker/containers/ ${DOCKER_APP_CONFIG_PATH%/}/containers_backup\ umount /var/lib/docker/containers || logger -t docker Error: RAM-Disk could not be unmounted!\ rsync -aH --delete ${DOCKER_APP_CONFIG_PATH%/}/containers_backup/ /var/lib/docker/containers\ logger -t docker RAM-Disk removed' /etc/rc.d/rc.docker # Automatically backup Docker RAM-Disk sed -i '/^<?PHP$/a \ $sync_interval_minutes=30;\ if ( ! ((date("i") * date("H") * 60 + date("i")) % $sync_interval_minutes) && file_exists("/var/lib/docker/containers")) {\ exec("\ [[ ! -d /var/lib/docker_bind ]] && mkdir /var/lib/docker_bind\ if ! mountpoint -q /var/lib/docker_bind; then\ if ! mount --bind /var/lib/docker /var/lib/docker_bind; then\ logger -t docker Error: RAM-Disk bind mount failed!\ fi\ fi\ if mountpoint -q /var/lib/docker_bind; then\ rsync -aH --delete /var/lib/docker/containers/ /var/lib/docker_bind/containers && logger -t docker Success: Backup of RAM-Disk created.\ umount -l /var/lib/docker_bind\ else\ logger -t docker Error: RAM-Disk bind mount failed!\ fi\ ");\ }' /usr/local/emhttp/plugins/dynamix/scripts/monitor else logger -t docker "Error: RAM-Disk Mod found incompatible files: $(md5sum /etc/rc.d/rc.docker /usr/local/emhttp/plugins/dynamix/scripts/monitor | xargs)" fi

When I had faced this issue upon a migration from Windows Server to BinHex, I had eventually identified that somehow my blobs DB had become corrupted - but only the copy that had been moved over to Unraid. My original copy was OK. I copied the unzipped blobs DB back over and overwrote it, did permissions tweaks and was right as rain. TLDR: Check the integrity of your Blobs DB as well. You may need to do this pragma integrity check manually, outside of the script.

Hybrid or "tiered" storage (NVME + SSD + HDD). Where "hot" data is in NVME, then transitions down the stack. Least used data is on hdd. In other words; a QNAP qtier alternative.

Enable turbo write.

I never used the script, it may have issues with latest unRAID, you can still do it manually (array will be inaccessible during the clear): 1. If disable enable reconstruct write (aka turbo write): Settings -> Disk Settings -> Tunable (md_write_method) 2. Start array in Maintenance mode. (array will not be accessible during the clearing) 3. Identify which disk you're removing 4. For Unraid <6.12 type in the CLI: dd bs=1M if=/dev/zero of=/dev/mdX status=progress For Unraid 6.12+ type in the CLI: dd bs=1M if=/dev/zero of=/dev/mdXp1 status=progress replace X with the correct disk number 5. Wait, this will take a long time, about 2 to 3 hours per TB. 6. When the command completes, Stop array, go to Tools -> New Config -> Retain current configuration: All -> Apply 7. Go back to Main page, unassign the cleared device. * with dual parity disk order has to be maintained, including empty slot(s) * 8. Click checkbox "Parity is already valid.", and start the array

Not until we update it to V12. php.ini is in the container docker exec -it nextcloud bash Then it's in /etc/php7/ Any changes you make won't survive a docker update. Although you could cp /etc/php7/php.ini /config/php.ini Then mount the file in your docker run command/template -v /config/php.ini:/etc/php7/php.ini