Leaderboard

Popular Content

Showing content with the highest reputation since 02/28/24 in Posts

  1. 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.
    14 points
  2. This is a bug fix release, resolving a nice collection of problems reported by the community, details below. All users are encouraged to read the release notes and upgrade. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully If you have Unraid 6.12.8 or Unraid Connect installed: Open the dropdown in the top-right of the Unraid webgui and click Check for Update. More details in this blog post If you are on an earlier version: Go to Tools -> Update OS and switch to the "Stable" branch if needed. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.
    9 points
  3. I think it's two fold. One, there is a group of individuals that do this for a living and want to play around it to learn it for their job, or as a way to test if it's something they want to deploy at their workplace. Secondly, I think others do it because of the "cool" factor. Don't get me wrong, I still think it's a mighty fine solution (I've played around with it myself), but it takes a lot more configuration/know-how to get it working. Like you said, it doesn't have docker by default, so you either have to create a VM and/or LXC, install docker and go from there. Personally I've played around with Jellyfin on Proxmox...I did it in a VM, I did it with docker in a VM, as well as an LXC and while it was fun, it wasn't no where near as simple as Unraid, where it's click install, change a few parameters and go. I also see a lot of discussion around the "free" options out there. No offence, but these "free" options aren't new. They've been around just as long, if not longer than Unraid and guess what, people still chose Unraid. Why?, because it fits it target market...."home users." Easy to upgrade storage, similar easy to follow implementations for VMs and docker, a helpful/friendly community, plenty of good resources to help you along (ie: Spaceinvader One),etc... There's more to Unraid then just the software and it's why people chose Unraid over the others. People will pay for convenience, it's not always about getting stuff for free. Does Unraid have every feature that the other solutions have...no, but it doesn't need to and IMHO most of them don't really matter in a home environment anyways. I also agree there seems to be a lot of entitled individuals. I feel bad for software developers, because people want their stuff, they want them to make changes, add new features, etc... and oh btw, please do it for free, or charge someone else for it, thank you... I've seen a lot of arm chair business people here offering suggestions to just do what the others do; go make a business version, go sell hardware, etc... No offence, but those things sound way simpler than what it actually takes. Not to mention there's no guarantee that it will pay off in the long run and has the potential to put you in a worse situation compared to where you were before. For example, lets say they do offer a business solution and price it accordingly. Well guess who is going to demand more support, or the ones demanding the new features? It won't be us home users, it will be the businesses, and if they are the ones essentially funding the development, you can bet where the development efforts are going to go. I just want Lime Tech to focus on Unraid. I don't want them to focus of other avenues that can potentially make things worse in the long run because they have too much going on. Just focus on what they do best and that's Unraid. We can go back an forth all day long. At the end of the day, if you are that unhappy then please just move on (not you MrCrispy, just speaking generally hehe). While I can understand the reasoning behind the dissatisfaction, but to be honest, none of the naysayers have given Lime Tech a chance to prove themselves with this change. Sure we can talk about what "other" companies have done in the past, but in all honesty I don't care about "other" companies, all I care about is what Lime Tech does. Just because others have done terrible things, that doesn't mean every company will. It's ok to be skeptical, but you can be open minded as well. Give them a chance, don't just wish for them to shutdown and close up shop. I mean they've already listened and are offering a solution to those who want security updates/fixes for a period of time after the fact. Furthermore they've also upped the starter from 4 to 6 devices, so they are listening....yet people are still unhappy. Which leads me to believe there will be a group of entitled individuals who will never be happy no matter what they do.
    8 points
  4. 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!
    8 points
  5. 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.
    8 points
  6. (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
  7. As previously announced, Unraid OS licensing and upgrade pricing is changing. As we finish testing and dialing in our new website and infrastructure, we aim to launch on Wednesday, March 27th, 2024. What this Means You have until March 27th, 2024, to purchase our current Basic, Plus, and Pro licenses or to upgrade your license at the current prices. New License Types, Pricing, and Policies We are introducing three new license types: Starter $49 - Supports up to 6 attached storage devices. Unleashed $109 - Supports an unlimited number of devices. Annual Extension Fee for Starter and Unleashed: $36 Lifetime $249 - Unlimited devices. No extension fee. Starter and Unleashed licenses include one year of software updates with purchase. After one year, customers can pay an optional extension fee to make them eligible for an additional year of updates. If you choose not to extend your license, no problem. You still own the license and have full access to the OS. If your license extension lapses (as in, you do not pay your annual fee), you can download patch releases within the same minor OS version that was available to you at the time of the lapse. Please review our FAQ section below for more on this security update policy. Basic, Plus, and Pro Keys Will Become 'Legacy Keys' These changes do not apply to current Basic, Plus, or Pro license holders. As promised, you can still access all updates for life and upgrade your Basic or Plus license. Once Starter, Unleashed, and Lifetime are available, Legacy licenses will no longer be sold. Legacy License Upgrade Pricing Changes Along with the new license types, we are increasing our Upgrade pricing for all legacy keys. Legacy key holders will also be able to move into the new system if they choose. The pricing will be as follows: Basic to Plus: $59 Basic to Pro: $99 Basic to Unleashed: $49 Plus to Pro: $69 Plus to Unleashed: $19 FAQs Please refer to our blog for a full list of FAQs
    7 points
  8. 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
    7 points
  9. Es gibt ein Problem mit 6.12.9 unter ganz bestimmten Umständen. Wer diese Konfiguration betreibt sollte 6.12.9 noch nicht installieren. Es geht um CIFS/SMB Remote Mounts die mit Unassigned Devices in Unraid angelegt werden (/mnt/remotes/xxx). Das heißt Unraid ist der Klient einer CIFS/SMB Verbindung. Die Funktion von Unraid als Server einer CIFS/SMB Verbindung ist nach derzeitigem Erkenntnisstand davon nicht betroffen. Es gibt zwei aktuelle Bug Reports, einer ist von mir: Weiterhin gibt es von @dlandon einen Hinweis wohin das Problem zeigt (Kernel/SAMBA): Erkennen könnt Ihr das Problem eindeutig an den CIFS VFS Fehlern in der syslog. Wenn diese auftauchen, dann seht Ihr oder Eure Software nur einen Teil der existierenden Ordner oder Dateien. Das kann erhebliche Probleme nach sich ziehen. Wer 6.12.9 über 6.12.8 bereits installiert hat, und diese Konfiguration betreibt bzw. den Fehler bekommt --> ein Downgrade auf 6.12.8 ist jederzeit problemlos möglich:
    6 points
  10. There are many unexplained stories about Realtek cards and ASPM ... so I made a little investigation: The kernel in-tree r8169 driver is a generic driver for all Realtek network cards, despite its name. It contains lots of workaround for different Realtek chipset. It also has a very strict condition for using ASPM (this condition was removed for a few weeks last year then reverted back...). It enables ASPM only for RTL8125A and RTL8125B chipset and only if a bit in a register is set in the chip by the system vendor, which signals to the driver that vendor successfully tested ASPM 1.2 on this configuration. (Probably not many motherboard vendor bothers to do this ...). If this condition not met it tries to disable ASPM, if it is denied by BIOS then it uses ASPM whatever the chipset is ... This behaviour cannot be overridden. That basically means low chance for having ASPM with the in-tree driver. I also checked the r8125 driver (from Realtek) used by this plugin. It contains CONFIG_ASPM = n in the Makefile but this just sets the default value of ASPM, it is not a real compile time option. After installing this plugin you can easily enable ASMP if you create a file r8125.conf in /boot/config/modprobe.d with the following line: options r8125 aspm=1 It enables ASPM the correct way. With this my server reaches C10 package state... @jinlife please try to enable firmware load support with ENABLE_USE_FIRMWARE_FILE = y. The firmware files are already in /lib/firmware/rtl_nic/ as the in-tree driver uses them. Probably most of these cards are shipped with outdated firmware, so enabling this option would help. Correction: The r8125 source code contains the firmware file in binary form. No need to enable ENABLE_USE_FIRMWARE_FILE. The speed issues can be caused by EEE (Energy Efficient Ethernet) which is enabled by default by this driver. You can check the status with ethtool --show-eee eth0 Or disable it with an extra line in r8125.conf options r8125 eee=0
    6 points
  11. To be honest, based on the level of self entitlement shown by many posters regarding the licence changes, I don't know why Lime Tech should even bother trying to make you happy. From my perspective, Lime Tech have bent over backwards in an attempt to be fair and reasonable to existing and new licence holders. Do people think that software development is free? The entire world is in the midst of massive inflation, the cost of developing and maintaining software is not immune to this. Compared to the cost of hardware, the increases to licence costs are tiny. Some people need to grow up and get with the real world.
    5 points
  12. 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 are
    5 points
  13. 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
  14. Update: We've added additional info around the upcoming changes via some FAQs taken from the community: https://unraid.net/blog/pricing-change
    5 points
  15. We know that Dynamix File Manager is expected to be built-in for the 6.13 release
    4 points
  16. I must say that the new update box, getting the updates notes and known issues before updating (or needing to check them here) is an nice touch!
    4 points
  17. Ich hätte als Threadersteller die Lösung dem Problemlöser (ich777) zugesprochen anstatt sich selbst. Gibt ja auch ein Ranking hier im Forum.
    4 points
  18. I think it is just due to the nature of Unraid development and philosophy. Limetech historically has taken a very long time to develop and test new releases (even minor ones). There are a lot of variables in a product such as Unraid which tries to run on as many hardware platforms as possible. They also thoroughly test to make sure no data loss will result from a new version of the software. It all takes time. The product also seems to be driven a lot by user requests/needs and priorities can change. I think they would rather just "go with the flow" than publish roadmaps that may change a lot. I do not speak for Limetech. If they did provide roadmaps, we would all likely be complaining about versions/features not making published deadlines. I was a software product manager for 25 years and was in charge of many roadmaps. We rarely ever made the published timelines due to unforeseen engineering roadblocks and trying to control "feature creep." It got to the point that I really has to pad the timelines and then customers complained about excessively-long development cycles. Roadmaps are doubly difficult for small companies with limited resources.
    4 points
  19. Data Volume Monitor (DVM) for UNRAID "A plugin that lets you monitor and act on your consumed data volume utilizing vnStat." With much pride I'd like to present my latest project - the Data Volume Monitor (DVM). Dashboards, footer information, notifications, user actions (on VMs/Docker containers) and custom scripting. These are a few of the features being offered - all centred around the data volume consumption of your server. Don't want to your Syncthing container to pull in more than 50 GB a day? No problem, DVM will stop and restart the container for you within those limits. Running a few data intensive VMs and want to pull the plug when it's been too much? No problem, DVM will disconnect and reconnect specific VMs from/to the network. Want to move around some files and folders when you've pulled in too much data? No problem, set up a custom script and DVM will execute it for you when it's time. Please report back if you are experiencing any problems! This plugin was developed with older machines in mind - it's been tested on 6.8.3 and above.
    4 points
  20. Seems fair to me. I likely will never have a need to change my current two pro and one plus licenses, but, at least I know what the path is should I choose to go that way. Legacy users are protected and security updates within minor release will be available even to those with lapsed support. I think this addresses most concerns and everyone has enough information to decide where they go with Unraid. Change is often difficult, but, I feel this has been handled well and with more transparency than is often the case in these situations.
    4 points
  21. 3.21.24 Update: We have a new blog up here that outlines our new pricing, timeline and some new FAQs.
    4 points
  22. Hey team! I have published another RomM CA template now. (it took a couple of days to appear / publish in CA, please excuse the delay) When you are performing a fresh install, you will be presented with 2 options. Please select 'latest' in the option list to get the current v3.X and the template will have all the current variables available for you. Note: v3.X requires a MariaDB container, which is quick to add in Unraid CA. FYI: @Green Dragon - please notify the Discord community if you feel its appropriate.
    4 points
  23. Damn- I'll have to add this to my 'MeanTweets' share. Didn't you say you were leaving? Something about us trying to gouge everyone? (Seriously?) If you're going to stick around, great! Please review our Community Guidelines before making another post.
    4 points
  24. I've been using Unraid for over ten years now and have gotten tremendous value from my perpetual licenses. Personally, I would prefer if things stayed as they were. I have no need for a fancy website and do not plan to use official support. Better documentation would be nice, but it's not crucial. I'm the type of hacker and tinkerer who gets by on his own. Having said that, after watching the interview with Tom and Tiffany, I understand and support their desire to grow the business and move things forward. The new model seems fair. Hopefully, the team will be able to figure out how to deliver critical bug and security fixes to the last stable release, so no one is left with half-baked and buggy software when they decide not to renew. Not having new features for those who do not renew immediately is absolutely fair. I appreciate Tom's ability to build the business by bootstrapping his hobby. This type of feel-good story makes you think not everything is lost in this world. My slight concern is that if the new business model proves successful, eventually there will be a VC or an enterprise willing to make an offer to Tom that he would be silly to turn down. Everyone deserves a retirement, after all. And after the takeover, all bets are off since only profit matters to them. Anyway, I wish Tom, Tiffany, and the team all the best and, hopefully, mild business success so that the existing users can continue enjoying the great product. Cheers from Ireland
    4 points
  25. Thanks! I'll look into setting up a Patreon page. In the meantime, check out our Youtube page and you can support us there: https://www.youtube.com/channel/UCwisndMIdC6iEX9IyVbxBJQ/join
    4 points
  26. I can recommend these: https://www.amazon.de/gp/product/B01N4EUXCU This is an external M2 SATA SSD enclosure that creates a valid GUID which is a mix from the enclosure and the SSD that you put into it, so to speak the GUID is not tied to the enclosure. In my case it looks something like that: (the last part is actually the last few digits from the GUID from the disk itself) As a bonus this enclosure is USB-C and you can use any internal header to USB cable (like: https://www.amazon.de/gp/product/B09NQYXJYS) if you want to put it in your server.
    4 points
  27. 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 people
    4 points
  28. I don't think Unraid is widely used in the commercial space. From it's inception, it has been designed and built to target the home market. Unraid first and foremost is a NAS. Business/enterprise customers looking for a NAS want very fast, robust, tried and true solutions and unfortunately, Unraid doesn't meet that criteria currently. Unraid's default storage scheme is good for ease of expansion, that still provides redundancy, but it's no speed demon. They've added caching to help with writes to the array, but when it comes to reads it's still slow. That being said, by adding ZFS Unraid is closing the gap. Whether or not that's enough to make it an option for businesses, remains to be seen. The other big factor in all of this is that a lot of business/enterprise customer's typically want support contracts and to be honest, I don't know if Lime Tech really wants to go down that path atm. Maybe if they grow enough to support it, but business/enterprise customers are different animals entirely compared to home users. The needs, wants and expectations from businesses are very different than home users. So I'd say for now, Unraid will still remain largely a solution targeted at home users, but who knows, that could change down the road. Yes and no, As I've said in my post above, I do understand the frustrations and skepticism, however, Lime Tech did in fact take some of that feedback and implemented some changes before the actual licensing terms changed (ie: increasing starter from 4 to 6 devices, and offering support updates to those who do not wish to renew the update licensing each year). Yet there wasn't even an acknowledgement of any kind from some of these people to at least say "ok Lime Tech is taking feedback into consideration and trying to alleviate customer concerns." I fully understand and I do not blame them one bit if they still feel skeptical and unsure, but to constantly be overly negative no matter what Lime Tech does to help alleviate concerns is just complaining plain and simple. Edited to make points a little clearer.
    3 points
  29. This is not without precedent. When fiber optic Internet came to my neighborhood 20+ years ago, we were all promised free installation ($2700 actual cost) and speed increases as they became available with just a monthly ISP payment. I was among the first to sign up. For 15 years they kept their promise. About 7 years ago we "legacy" users were told that our speed would be capped at 100 Mbps. If we wanted more, we had to renounce our legacy status and pay $30 a month to the fiber optic provider (a consortium formed by 15 cities) + the ISP fee or pay $2700 for the "installation" and skip the $30 a month fee. I have no crystal ball and have no idea what will happen in the future with legacy Unraid licences, but, given their transparancy up to this point, I don't think they will start penalizing legacy users unless they pay up.
    3 points
  30. NOTE: As of posting this the Unraid CA library may not have picked up my edits yet, it's usually pretty quick though. I have updated the ':latest' tag option in the Unraid CA template. Select the ':latest' option on a fresh install of RomM to get the new variable and repo. Check the 'Repository' is pre-set to "rommapp/romm:latest" If the template is correct the 'UMASK' will be in the "Show more settings..." section and pre-set to "000" Thank you to @Cryptic3258 & @ktfcaptain for posting up the changes here (above). 🏆 Please report back with any issues / results for me to keep the template up-to-date. 💪
    3 points
  31. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- |.|.|.|.|.|.|o|o|o|o|o|o|O|O|O|O|O|O|0|0|0|0|0|0|0|0|0|0|O|O|O|O|O|O|o|o|o|o|o|o||.|.|.|.|.|.| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- ██████╗░███████╗██████╗░░█████╗░██████╗░███╗░░██╗ ██╔══██╗██╔════╝██╔══██╗██╔══██╗██╔══██╗████╗░██║ ██████╔╝█████╗░░██████╦╝██║░░██║██████╔╝██╔██╗██║ ██╔══██╗██╔══╝░░██╔══██╗██║░░██║██╔══██╗██║╚████║ ██║░░██║███████╗██████╦╝╚█████╔╝██║░░██║██║░╚███║ ╚═╝░░╚═╝╚══════╝╚═════╝░░╚════╝░╚═╝░░╚═╝╚═╝░░╚══╝ ░█████╗░██████╗░███████╗░██╗░░░░░░░██╗ ██╔══██╗██╔══██╗██╔════╝░██║░░██╗░░██║ ██║░░╚═╝██████╔╝█████╗░░░╚██╗████╗██╔╝ ██║░░██╗██╔══██╗██╔══╝░░░░████╔═████║░ ╚█████╔╝██║░░██║███████╗░░╚██╔╝░╚██╔╝░ ░╚════╝░╚═╝░░╚═╝╚══════╝░░░╚═╝░░░╚═╝░░ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- |.|.|.|.|.|.|o|o|o|o|o|o|O|O|O|O|O|O|0|0|0|0|0|0|0|0|0|0|O|O|O|O|O|O|o|o|o|o|o|o||.|.|.|.|.|.| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 🅟🅡🅞🅤🅓🅛🅨 🅟🅡🅔🅢🅔🅝🅣🅢 Docker tag: 8.1.113-unraid NEW: Current recommended Home User tag: 11notes/unifi:8.1.113-unraid NEW: Current Company/Corporate recommended tag: 11notes/unifi:8.1.113-unraid Current Critical Infrastructure (no downtime) tag: 11notes/unifi:7.5.187-unraid
    3 points
  32. I think the value proposition of Unraid is not being communicated to users and is getting lost. Unraid is primarily about the array - i.e. shfs using software real time parity, mix/match disk sizes, and NOT striping data. TrueNas or any of the custom NAS OS's don't do this. THIS is what keeps your data safe and allows you to grow. You can use mergerfs to combine disks. But the only alternative for parity is snapraid and its not real time. Everything else - vm's, dockers, community apps. all of that came much later, all of it its just a wrapper around open source projects you can use on any other distro or custom OS, with maybe a little bit more work. No one else has the data safefy. Not if you want to avoid striping and keep data in native format.
    3 points
  33. Ich bin da auch noch etwas Grün hinter den Ohren, aber soweit wie ich es verstanden habe, hängt dies gänzlich davon ab, wie das Image des Containers aufgebaut ist, den man da starten möchte. Gerade für so ziemlich alle Docker, die es in den Community Applications gibt, sind diese bereits so aufgebaut, dass sie auf die PUID und PGID Variablen horchen (und häufig auch UMASK, wenn die Software im Container mit Dateien rumhantiert, damit man die Berechtigungen auf den erstellten Dateien steuern kann). Wofür die Variablen dann genutzt werden, hängt dann davon ab, was im ausführenden Code des Dockers passiert. Z.B. könnte ein dockerfile vorsehen, dass die PUID und PGID Umgebungsvariablen dazu genutzt werden, um eben die Benutzer- und Gruppen-ID eines Linux Users fest vorzugeben, der innerhalb des Containers erstellt wird und darin weitere Prozesse ausführt. Gerade, wenn Volumes vom Host System zum Container als persistenter Speicher durchgereicht werden, werden alle Dateien die dieser Linux User im Container innerhalb der durchgereichten Volumes erzeugt, standardmäßig mit seiner eigenen Benutzer und Gruppen ID versehen. Wäre dann ja naheliegend die IDs 99 für User und 100 für die Gruppe innerhalb des Containers zu verwenden, weil diese im Unraid Host System für den Benutzer "Nobody" und die Gruppe "Users" stehen. Das erleichtert dann den Umgang mit diesen Dateien innerhalb des Unraid Hosts selber, ohne dass man als root User in Unraid unterwegs sein muss. Und wenn man jetzt einen Docker Container erwischt hat, der gar nicht diese Umgebungsvariablen verwendet? Kann sein, dass dieser Docker Container in seinem Code keinen neuen User erzeugt innerhalb des Containers, sondern einfach mit dem default User des Containers los läuft, das wäre dann eben "root" (ID = 0). Möglicherweise kann man sich dann mit dem "--user=99:100" Flag in den Extra Parametern helfen, die steuern eben die IDs des Standard Users. Das sorgt dann wenigstens dafür, dass alles was der Standarduser des Containers an Dateien erzeugt, mit diesen IDs versehen werden. Das kann gut gehen, muss aber nicht. Gerade wenn der Wechsel weg vom "root" User des Containers dafür sorgt, das er dann plötzlich gewisse Prozesse nicht mehr starten darf ("root" darf schließlich alles, aber der Flag sorgt dafür, dass dieser User eben nicht mehr "root" ist). Dann knallt der Container und läuft nicht mehr. Letztendlich hängt es also ganz davon ab, was für einen Container man da hat und was der bei seinem Startup so alles tut. Die feine Unraid'sche Art ist eben die Unterstützung der PUID und PGID Variablen, aber das muss halt auch der Container Code hergeben. Einfach PUID/PGID als Umgebungsvariablen an einen Container klatschen sorgt noch lange nicht dafür, dass dieser mit diesen Variablen auch was macht.
    3 points
  34. I've figured out a way to implement the feature without interacting with the Docker containers and VMs themselves. I've just pushed an update with the new setting (disabled by default), so please let me know if it works for you... 🙂
    3 points
  35. I've done some testing and found out Samba is crashing: [2024/03/14 09:07:19.329402, 0] ../../source3/smbd/fd_handle.c:39(fd_handle_destructor) PANIC: assert failed at ../../source3/smbd/fd_handle.c(39): (fh->fd == -1) || (fh->fd == AT_FDCWD) [2024/03/14 09:07:19.329435, 0] ../../lib/util/fault.c:178(smb_panic_log) =============================================================== [2024/03/14 09:07:19.329442, 0] ../../lib/util/fault.c:179(smb_panic_log) INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in smbd (smbd[192.168.1.) (client [192.168.1.188]) pid 22564 (4.19.5) [2024/03/14 09:07:19.329447, 0] ../../lib/util/fault.c:186(smb_panic_log) If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting [2024/03/14 09:07:19.329451, 0] ../../lib/util/fault.c:191(smb_panic_log) =============================================================== [2024/03/14 09:07:19.329464, 0] ../../lib/util/fault.c:192(smb_panic_log) PANIC (pid 22564): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.19.5 [2024/03/14 09:07:19.329708, 0] ../../lib/util/fault.c:303(log_stack_trace) This is with samba 4.19. I seem to have found a get around, but I'm baffled right now about why this works. Install the recycle bin plugin and be sure it is running. In my testing it looks like file deletes work. Deleting directories works but an error is displayed and the Android app does not show the directory as being deleted until closed and re-opened. The directory delete also crashes samba. Since the recycle bin plugin is for deleted files through SMB, there is something the recycle bin vfs is doing that prevents the file deletes from failing in this situation. Because samba is crashing it looks to be an issue that the samba team needs to fix. At this time, I don't see any way through samba settings we will be able to fix this on the Unraid side. It could also be an issue with the Android app, but I doubt it. In doing some research, there is a samba bug here that might solve the issue.
    3 points
  36. dann beziffere mal eher warum die überhaupt transcoden willst bzw. das Szenario. eine Info hierzu vorweg, @home sollte nie transcoded werden sonder eher schauen das die Clients alles nativ abspielen können. externes / mobiles Schauen, da macht es Sinn um die Datenraten zu reduzieren ... nicht kompatible Clients, da braucht es transcoding ... was aber meist, falsche Konfiguration ist oder wirklich alte Hardware ... da kann man auch mal darüber nachdenken ob man da nicht etwas "aktualisiert" um nicht ins transcoding zu fallen, selbst wenn es dann ein FTV 4k wird ... die UHD630 auf meinem vorherigen 9900 er hat 6 x 4k hevc remux > 1080p h264 im Browser geschafft, ab dann gab es jedoch Artefakte ... den n100er hab ich jetzt noch nicht getestet, aber sicher mindestens gleich oder mehr ... die NV T400 ist mittlerweile für 8 parallele encodings freigegeben, nur als Info @EliteGroup, waren vorher 5, vorher 3. und ist sofern man auf eine dgpu zum transcoden setzt mit die beste Karte dafür, ich meine max 35 W Power Aufnahme. Zusammengefasst, für deine Software Anforderung reicht eigentlich "alles" Deine Hürde lautet ECC Ram für dein Gewissen, bei Intel hat es @EliteGroup schön aufgeführt, da wäre zumindest bei den aktuellen Plattformen DDR5 mit ondie ecc eine Option, oder diverse ältere Intel Systeme wo da unterstützen. Zweite Hürde gegen etwas "Kleines" Boards mit mind. 2 x nvme für deinen redundanten cache. AMD bin ich persönlich (leider) raus da ich immer mit Problemen zu kämpfen hatte, da können andere mehr zu aktuellen Systemen empfehlen. Wenn du dich etwas hier im Hardware Beratungs Bereich etwas einliest, findest du die Antworten, die Entscheidung was dir was wert ist im Bezug auf Anschaffungskosten (ECC, ddr5, ...) und laufenden Kosten (Verbrauch durch ...) liegt dann auch bei Dir @EliteGroup Danke für den Hinweis mit passenden Subforum, verschoben ...
    3 points
  37. Vielen Dank! Das hat mir sehr weitergeholfen. Bin ein Newbie mit Unraid und Docker etc. Aber mit Deinen Tipps habe ich es geschafft, das Ding zum Laufen zu bekommen. Liebe Grüße, Dietmar
    3 points
  38. Nein RAID5 ist ganz anders aufgebaut... Das Unraid Array ist ideal geschaffen für Multi-Media bzw. als Datengrab. Im gegensatz zu RAID5 wird eine HDD als Parität gewählt, die dient zur Wiederherstellungssicherheit, die Daten liegen DIREKT auf den Array-HDDs. Bei RAID5 werden die Daten auf das Array "verteilt". Das hat große Vor-/Nachteile. Als Media-Server hat Unraid große Vorteile: - Es spart mehr Strom und verschleiß, alle HDDs können im Standby schlafen und es schaltet sich nur die HDD ein die man braucht (automatisch). - Du hast dadurch gute Lesegeschwindigkeit und zwar 100% der einzelnen Platte von der gelesen wird, es wird für eine Datei nicht von allen HDDs gelesen. - Du kannst in gegensatz zu RAID5 eine HDD aus Unraid raus nehmen und an den PC anschließen und auf alle Daten der Platte zugreifen was bei RAID5 nicht geht. - Bei einer defekten Platte kannst du das System weiter verwenden, es sind halt die Daten der defekten HDD nicht "sichtbar". - Bei Unraid ist es sehr einfach HDDs zu erweitern, einfach anstecken und loslegen. Bei RAID5 kannst du nicht so einfach eine weiter Platte anstecken... Da kommen wir zu den Nachteil: Das schreiben / bearbeiten von Daten auf das Array ist seeeeehr langsam... Da beim schreiben gleich immer die Parität berechnet wird für die "Wiederherstellungssicherheit". Hier wird eine Cache SSD benötigt/empfohlen (als reiner Plex Server könnte man auch ohne Cache verwenden). Der Cache schiebt in einem Intervall die Daten aufs Array zb Nachts. In deinem Fall sind die Vorteile weit größer als der Nachteil, im typischen gewerblichen Betrieb würde das ganze anders aussehen und ein RAID die Vorteile haben. Wenn das "schreiben" direkt auf den Platten wichtig ist auf grund der "masse" die Täglich geschrieben / geändert werden auf den Platten ein RAID besser. Eine SSD wird umbedingt benötigt, dabei ist es aber egal ob SATA oder NVMe... Wenn dein Mainboard einen M.2 Slot frei hat, ist es ganz klar zu bevorzugen eine NVMe SSD zu kaufen statt einer SATA SSD, und den SATA-Slot für das Array aufzuheben. Das Array kannst du nicht für Docker applikationen / VMs verwerden, für die Apps wird zumindest 1. SSD benötigt. Bedenke eines besonders wenn du dir eine Plex Mediathek aufbaust: Strom sparen mit einem Mini-Board ist schön und gut, wichtig ist aber bei einem Media-Server immer das es einen kleinen Puffer zum erweitern von HDDs gibt. Wenn du weiteren Platz benötigst zb in 2 Jahren und extra neues Mainboard/CPU/Gehäuse etc kaufen musst, was hat das Stromsparen gebracht? Mini-Systeme haben meistens dann den Vorteil wenn du genau weißt was deine Anforderungen sind und du benötigst
    3 points
  39. Friends nearly everyone commenting here already has unraid and thus free updates FOR LIFE™. So please just let new folks choose to either pay a yearly fee or they can choose to pay a higher fee to upgrade to lifetime. When we build 2nd servers we can also make the same decisions. If no one pays then unraid won't get any new features...
    3 points
  40. I just installed 2024.03.06c on unRAID 6.12.8. The plugin is stable and working. All dashboards are loading normally. Thanks!
    3 points
  41. Update 2024.03.06c <- make sure it says "c" and NOT "b" before updating. Commit #294 - BUG: Check for ZFS before executing functions based on it. (reported by @malaki86) Commit #293 - BUG: Deactivated the database lock as it seem to have caused some serious issues. #290 will be incomplete again. Please check if this helps the issue, I'm not home at the moment and can't test it myself. Sorry for the inconvenience etc. and so on Thanks for people who contribute and provide with proper information, wonderful to see people are using the plugin To some others, I would just recommend to read the license, especially §15-§17 😘 https://github.com/olehj/disklocation/blob/master/COPYING
    3 points
  42. I believe the most significant challenge Unraid faces in attracting more customers is not a lack of marketing but the complexity of its setup. I ventured into it a few months ago, and just the initial step of obtaining a supported USB key required substantial research. Then, when you acquire a modern, reputable brand key, it's often too large for the setup to proceed, necessitating the use of external applications and manual installation to make it work. Expecting people to use 16GB sticks today is akin to asking them to revert to using floppy disks. Beyond that, there's inadequate settings information in the os; the wikis are somewhat outdated. The main resource becomes scouring through old YouTube videos for guidance. The absence of setup wizards and the high risk of errors, along with limitations like no WiFi connectivity from the host, compound the issue. Although I appreciate the operating system, I cannot recommend it to less tech-savvy friends. This, in my opinion, is Unraid's most substantial barrier to increasing revenue, not marketing. Marketing will naturally follow if the software becomes easy to set up and stable. Challenge a typical Windows user to install it with a RAID, a VM, and a Docker container without making mistakes or needing to search the internet for help. Achieving that level of user-friendliness and revenue will follow.
    3 points
  43. I fully understood now, what the issue was. I must be blind However: The fix includes supports now to respect excludes as well as skipping external volumes (if the per-container setting does not wish to backup those). The two new ideas are featured by noirsoldats. For anyone who wants to test the fix on their affected setup: I created a small script that patches the file in question. Its a one-liner and it will do the job for you. Running twice will undo the fix! Open a terminal and paste the WHOLE LINE: curl -s https://raw.githubusercontent.com/Commifreak/unraid-appdata.backup/volume_dup_check_fix/vol_dup_fix.sh | bash Please reload the settings page and check if the warnings are now gone or - if shown - correct!
    3 points
  44. Before anyone says anything, my answer is "I know". Try again in about 5 minutes
    3 points
  45. If I hear the word "subscription" used to describe the changes for Unraid one more time, I gonna scream!😣
    3 points
  46. 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?
    3 points
  47. Settings, display settings - color codes in hex
    3 points
  48. Yes, as stated before, that is how I do it now. But with many users (often new) requiring these modifications to the file, it might be best to not have them fiddle with typing and instead make it easy toggles and checkboxes.
    3 points
  49. You can edit this directly in the webUI Main - Boot Device - Flash - Syslinux Configuration The trick is knowing what to put
    3 points