Leaderboard

Hi Unraiders, I just wanted to take a minute to recognize and honor @JorgeB for surpassing 50,000 posts here! Wow 👏 Thank you for all of your help to the Unraid community over these past 15+ plus years! We are sending Jorge a gift as a token of our gratitude and if you would like to as well, please do so here. Thank you Jorge!

7.4.162 is more stable than 7.4.156. Please go directly to this version if you are not on .156. Situation: Legacy systems: 5.14.23-ls76 or 6.5.55 versions seem fine. (AKA "old old old old stable" or "old old old stable"). (Old in wall APs or other legacy APs need this?) Wifi6/New Deployments: 7.2.95 or 7.3.83 tags are fine. (AKA "old old stable" or "old stable"). (Newer APs wont adopt if not at least this?) Current (Production/Business should be fine. Hopefully): 7.4.162 ("stable") (Dont use this if your company builds rockets or does heart surgeries. You dont need it.) Future version (Only recommended for home or if your business requires a new feature missing from an old version): n/a at this time. (Using future versions is risky.) Kind regards P

Can't really believe how I've made so many posts, and due to the increasing number of daily user posts over the years, at this pace it will take me considerably fewer years to reach 100K, if we are not all replaced by ChatGPT by then It really means a lot to me being a valued member of this great community, thanks all!

Overview: Support for Docker image unraid-api-re in the bokker/unraid-api-re repo (fork of the original). Docker Hub: https://hub.docker.com/repository/docker/bokker/unraidapi-re Github/ Docs: https://github.com/BoKKeR/UnraidAPI-RE If you feel like supporting my work: just say thanks! This is a fork of https://github.com/ElectricBrainUK/UnraidAPI I managed to fork and make the original project work on github ci. I will try to keep this project alive with newer unraid releases, its an exact dropin for the original https://github.com/ElectricBrainUK/UnraidAPI just replace the image electricbrainuk/unraidapi with bokker/unraidapi-re I will create a tag for each minor release as in: bokker/unraidapi-re:6.12 which will cover 6.12.0 <-> 6.12.2 I mostly test the functions related to reporting status, if you have special needs as removing/editing containers, vms, switch gpus please tell if the container malfunctions for you. I cant stress enough that this is not a proper solution, this container scrapes the unraid UI. Every minor update will possibly break functionality. I would love to setup automated tests, but to be able to do that I need a way to spin up the unraid os (or frontend) in a test environment. Happy to hear what ideas people can come up with. Until then please call up your local Unraid congressman and tell them how much you care about a publicly available API.

I made an update which automatically resolves the issue when the shim interface is created. This should help anyone with static network settings and "host access" enabled.

helped me out a few times (both in my own threads and when searching for previously solved threads), much appreciated and congrats!

I see what is happening When you create a static IP address + gateway without explicitely setting a metric value, then a default route with metric 0 is created for br0. This is indeed wrongly displayed in the GUI as value 1 (a display error). When creating the interface shim-br0, another default route with metric 0 is added, but this fails because two times the same metric is not allowed and hence there is a missing default route for the shim-br0 interface as a result, and this causes communication loss to the outside world whenever the shim-interface is used. The solution is indeed to set a metric value other then zero for the br0 gateway when a static IP assignment is used and "host access" is enabled. Btw this is not Unraid 6.12 specific but is true for earlier versions too. Need to think of a way to make this clear to the user and avoid this situation. Thanks for all the testing.

Was able to upgrade without any issues from 6.11.5 I think it was before.

This is my routing table I use static routing with explicit settings for metrics. Docker uses ipvlan and has "host access" enabled, hence the shim interface Doesn't give any problems in my network set up.

Is there an “idiots guide” to setting this up? It took me about a month of troubleshooting and reading the docs on the older version and, I eventually got it up and running. I saw that an upgrade was available and there was no way I was going to attempt it after reading the docs as far as what was required to get the new version running. So, I left it alone. Unfortunately for me, I had to stop my Docker service to do some maintenance and the old version of Frigate, for whatever reason, would no longer launch. I made a backup of my config.yml file and attempted to install the new version to no avail. The docs aren't exactly idiot/user-friendly. There has got to be a better “how to” video/webpage out there that I can't find to assist in getting this new version back up and running?

well... just shoot me lol.. i wasted so many hours trying to figure this out.... i am eternaly gratefully sir..

Evtl. kannst du den Share zusätzlich über einen Container (z.B. CrushFTP) per FTP freigeben. Scan2FTP sollte der HP auch können.

Do you have netbios enabled? Problem with netbios is twofold (1) it doesn't support ipv6 and (2) it wants to use a broadcast address, which doesn't exist on a tailscale tunnel. Netbios needs to be disabled and use WSD instead for host discovery.

Darn Spammer. Nice Job and I'm sure the entire unraid Family thanks you for your tireless help and advice.

85 days of uptime. I'd say its fixed at this point. Thanks JorgeB

Ok I upgraded and it seems to be stable while running and it found errors.

Did you modify your "network.cfg" file manually? It is missing the last entry, which should be SYSNICS="1" Tip: since you are using a single interface, you can disable bonding.

Hier findest du vielen Infos und deutsch:

Looks like your router gets confused by the shim-br0 interface. Test again with host acces to custom network disabled.

gerne siehe hier @akazu könnte ein Ansatz sein wenn ... Danke @cz13 für den Hinweis

Ran without errors. Will leave it and see what happens overnight and check the logs in the morning. UUID: 0d3eea3a-97ec-4495-aadc-9bc75f3a2749 Scrub started: Fri Jul 14 16:19:57 2023 Status: finished Duration: 0:05:30 Total to scrub: 193.01GiB Rate: 598.95MiB/s Error summary: no errors found

Re-saving the settings cleared the error. Thank You. ab.debug (2).log

@cshellen and this is exactly what is the case here, the Craftopia Dedicated Server app was not updated: (Source) There is nothing I can do about that, you have to wait until the developers from Craftopia update it.

Thank for all the help @JorgeB

Please post the diagnostics.

ahh my apologies i installed this same container years ago and it needed my credentials for install. just took out my credentials and its working now thanks!!

I just installed 6.12.3-rc3, and I forgot to stop the array before the reboot, and sure enough it got stuck. But I was able to open a web terminal and use umount /var/lib/docker and it stopped the array and rebooted normally. After reboot I also stopped the array, and it didn't get stuck. Rebooted, and that was normal. Stopped the array again, and it stopped and started again normally. So far, the issue seems to be fixed. I'll try stopping and rebooting a couple of times in the next few days. I normally don't reboot my server for weeks at a time, nor stop the array that often. If 6.12.3 still isn't a stable release in the next week I'll provide an update.

Legend.

Of course, the choice is yours but liquid cooling on a server is not generally a good idea. I am sure there are some that do it and perhaps they will share their experiences with you. It is very much discouraged especially if you have a server that runs 24/7. Liquid cooling failures can be very damaging to your server (depending on what type of failure it is) especially if they happen at a time when the server is not being monitored. Air cooling failures are much easier to diagnose and fix and are less likely to happen. Usually, liquid cooling is for the overclockers who want to squeeze every last bit of power/speed out of their CPU, RAM, GPU, etc. None of these should be overclocked in a server.

käme jetzt drauf an wie, aber was immer geht killall weebsync-linuxstatic im terminal ...

Ok yeap maybe I'll go Intel if it's more simple and stable. I was looking at ryzen because of a deal on amazon prime day but I didn't pull the trigger and I'll look at intel combos. I have a Full ATX case but it's also seen better days and I would replace it as well when I upgrade.

Any plugin that put items on the dashboard had to be updated to support the 6.12 series of Unraid. In many cases this was done by forking the earlier one so you have to delete the original and find its replacement via the Apps tab.

100% wäre die ideale Belegung. Der Balken ist recht sinnfrei, die einzig verwertbare Info erhält man, wenn man mit der Maus drüberhovert (musste ich auch erst lernen). Dann wird die wirkliche Speichergrösse angezeigt. Die ist bei UNRAID standartmässig immer 1/8 vom Hauptspeicher. Man kann sie aber manuell pimpen (soll irgendwann auch von der GUI aus funktionieren) Ich hatte anfangs mal 64GB abgestellt, hab nun auf 72Gb erhöht. Wunder verspreche ich mir aber nicht davon, wir werden sehen. Für den Cache Pool ist der Cache relativ sinnfrei (sofern der Cache Pool flott ist), erst wenn ZFS im Array verwendet wird, macht es Sinn, RAM zu "opfern" (bei aktutem Speichermangel wird es aber etwas widerwillig wieder rausgerückt, es ist also keine fixe Grenze, nur ein oberes Limit)

I just pushed an update that should fix this issue... apparently the fix in the last version wasn't completely effective, I used a larger hammer this time

Correct.

Ich hab genau den im Einsatz und bin sehr zufrieden damit

Hey I'll jump on github too but just curious, what's the typical amount of data these speedtests use? I set up Unraid a few weeks ago and I've had this speedtest container running a test every 30 minutes. I'm 975GB/1200GB of my data limit within 10 days! Trying to track down the problem and wondering if the speedtests could be it.

For those wanting to stay on updated versions of bixhex releases, I see he did release libtorrentv1 versions of his apps. Change your repo's to the following. binhex/arch-qbittorrentvpn:libtorrentv1 binhex/arch-delugevpn:libtorrentv1

ProtonVPN support is now in!, the image (just built - please pull down) will now automatically assign and set an incoming port for you in the application, support for both wireguard and openvpn is included, for instructions see Q31:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Found the solution on reddit. Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to use the service credentials instead. You can find your service credentials by following these steps: Please log in to your Nord Account by following this link: https://my.nordaccount.com/dashboard/nordvpn/ Click on the NordVPN tab on the left panel which is under the Services tab. Scroll down and locate the Manual Setup tab, then click on Set up NordVPN manually: Verify your email by entering the one-time code you will receive in your registered email inbox. If you are unable to find the email, please make sure to also check your spam/junk folder. Copy your service credentials by using the buttons on the right.

Thanks, made a fix.

I can do nothing but 100% agree with this. In this world of ubiquitous free/open source software, it's easy to forget that we are actually paying customers for this product. As paying customers, it only makes sense to make certain demands and set some expectations on what we're purchasing. Make no mistake, I like UnRAID a lot, but this whole thing with letting the customers figure out solutions to bugs in the product they paid for... It's just not right. A NAS software product which doesn't support Time Machine backups out of the box? Again, it's just not right.

Hey all - I'm the Docker image author. If people are having specific issues with the image not running or unexpected errors, I can help but would appreciate issues being posted to GitHub. @hedrinbc - No idea where or how the container image is published to the marketplace but there may be an update needed to change how the container is run as it looks like some people are hitting ulimits as you can see here: https://github.com/mbentley/docker-omada-controller/issues/298#issuecomment-1491937963 This would be a change to how the run command is defined assuming it uses docker run type parameters.

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.

The ability to boot the Unraid Operating System off of PCIE / NVME or SATA / SSD drive instead of a USB key. As the title and short description suggests; I would very much like Lime Technologies to incorporate this as feature in an upcoming beta release. This post is a bit of a rant / whinge as an unhappy Unraid customer. RANT ON: The why: Because of the poor experience I have had over the last couple of years with the reliability, durability and frustrating user experience when a USB key has failed as a bootable device for Unraid. Because a USB key no matter what the brand or the warranty period is not an enterprise class solution for a bootable partition. Because in my experience whether you pay $5 or $50 for a USB key to replace the last one, the 5 year warranty period amounts to nothing when it costs you time, money and your server is down. The manufacturer of the USB key won't cover you for lost productivity and ultimately it will cost you more time and money to follow them up on their warranty. Most retailers and manufactures rely on consumers considering the USB key to be disposable and not pursue the arduous warranty / RMA process. Whilst I have the outmost respect for the Lime Technology support staff; my user experience has been less than optimal. To be told that the SLA for a failed USB key replacement within the arbitrary 12 month failure window is 3 days implies that you will need to wait up to 3 days before your server can be up and running again is unacceptable. <- I actually own two Unraid Pro Key licenses; only one of them is used; this was the only way could get my server up and running again in an acceptable amount of time. What is the point of backing up the key if you can't restore it to a new drive to use without having to contact support or request a new key? The 12 month arbitrary self-service replacement window - In a perfect world, we would buy the USB key with the 5 year warranty. The USB key would operate reliably for its 5 year warranty period and when it fails the Unraid user would utilise the self-service online replacement service. <- I have had no less than 4 USB keys fail; all with 5 year warranties (reputable brands, Sandisk, Lexar etc) in the time that Lime Technology has had the My Servers Plugin published to its consumers. All of them have failed requiring manual intervention by Lime Technology Support, I am currently waiting on another replacement. The second failure within two weeks. Its just not green or environmentally friendly. USB keys fail and when they do they aren't usually repurposed because of lack of trust or integrity in the failed storage device. They usually end up as e-waste and the plastics and materials are harder to recycle so normally end in land fill. The rationale: Its 2022 /2023, I find it incredulous we are still relying on this antiquated storage interface. USB keys are for the temporary storage of photos and documents! If you read any of the SanDisk or Lexar use cases; using a USB key as your primary boot partition isn't one of them! We spend so much time, money and effort building our version of the ideal Unraid server. Thousands of dollars are spent on repurposed enterprise server hardware, new enterprise class drives and then we leave uptime, reliability and durability of the entire server to a single device which is based on a memory storage interface standard that is slow, unreliable and was never meant for high durability (read / writes). Review the number of Unraid consumers who have posted a forum message where the root cause has been the USB storage media has failed. <- We have all been there numerous times. <- How many times has Lime Technology told you to plug your USB key into a USB 2.0 interface? I challenge you to find a modern server / workstation class motherboard that has a USB 2.0 port? I own an Asus WRX80E Sage WiFi motherboard. We have a high level of trust in modern NVME / SSD drives; we place some of our most important data on these devices; surely the Operating System for Unraid which includes configuration, passwords, encryption keys and certificates deserves the same level of durability!? NVME / SSD can be run in RAID 1 enough said. Most BIOS's support booting off NVME / SSD natively either in legacy or UEFI mode. NVME / SSD's support native hardware encryption that are TPM / BIOS aware. The current USB Creator tool can be hit and miss; some USB keys it recognises and allows you to format and create a bootable partition. Other keys simply cannot be seen by the USB Creator tool....despite the OS seeing the key....there doesn't appear to be any rationale as to why this may the case; another source of frustration and poor user experience. It should be a fairly straight forward process to repurpose / redeploy the USB Creator Tool onto a USB key....plug this key into your server and have the USB Creator Tools partition / image your internal NVME / SSD drive. NVME / SSD's don't suffer from the same FAT32 limitations; therefore partition limit sizing would not be a constraint. <- How many times have you had to reboot your server prematurely because the USB partition has filled up with logs whilst you attempt to diagnose the issue? How many times have you had Unraid tell you your logs are filling up......there is nothing actually wrong with your system....its just been running for a very long time? To summarise; @limetech PLEASE PLEASE PLEASE introduce the ability to boot off an enterprise class, internal storage medium such as PCIE/NVME or SATA/SSD drives. Hell even a consumer class NVME is more durable than USB key. I can't recall the last time an NVME drive failed because of lack of durability. In my opinion Lime Technology needs to update their support for bootable media; the last email I got from Lime Technologies support suggested I buy a Kingston DTSE9H USB key.....this key has not been manufactured by Kinston for years! NOT HAPPY! :RANT OFF

What are people using these days? I tried Rclone and it's not finding all my files in a dir, and thus only backing up a fraction of what's there. Can't figure out why. Doesn't seem to be permissions related either. Fiddled with it for 18h+ and didn't figure it out. Off-the-shelf NAS solutions and the likes of TrueNAS have replication and synchronization facilities built into them. I feel like this is the missing piece of the puzzle for me with Unraid. It's a big piece, but it's largely there.

With a lot of help from an unraid user on reddit I was able to figure this out and am posting here for anyone else tryin to do this. Prerequisites- Router and network switches must support VLANs. You will need to research the configuration of these for your particular brand. Docker service and VM Manager must both be disabled in settings (set enabled to "No"). In Settings>Network Settings set Enable VLANs to "Yes" for your desired ethernet port (eth1 in the pic) and click "Apply". This will add several new settings. Enter your desired VLAN number, set Network protocol (optional) and set address assignment(s) (optional). Click "Apply" once again. In Settings>Docker enable Advanced View. Check the box next to the new network you have just added (eth1 in the pic) and enter the proper subnet and CIDR. Gateway will be the address of your router. Once you have finished, set Docker Enable to "Yes" and click "Apply" Finally, in the configuration settings for your docker container set Network Type to your newly added custom network (Custom:eth1 in the pic) and click "Apply". Note: I am not an expert on networking by a long shot. It took me quite a lot of digging through various forums to piece this together. Some of it may be wrong. If anyone sees any errors please let me know and I'll make the appropriate edits.

我解决了，反向代理都没有问题。比如用 https://c.b.com:1234 这个地址是不能访问到unraid上的需要后面加 login 变成https://c.b.com:1234/login 才能正确访问！！！！！

awesome info, thanks...I've learned something! So I used Telnet, and this is what I get: Linux 3.9.11p-unRAID. root@unRAID:~# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes root@unRAID:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 6c:f0:49:73:6a:6b inet addr:10.0.1.15 Bcast:10.0.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1075740918 errors:0 dropped:2531479 overruns:0 frame:0 TX packets:405619055 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:723965458 (690.4 MiB) TX bytes:3119341835 (2.9 GiB) Interrupt:76 Base address:0xc000