Leaderboard

Popular Content

Showing content with the highest reputation on 04/12/21 in all areas

  1. Just a friendly reminder everyone, discussing how to circumvent other vendors licensing will get content removed / banned from this forum. Tread lightly here
    3 points
  2. Please provide the instructions for doing this in the Official Unraid Manual (the one you get to by clicking lower right-hand corner of the GUI) and not just in the release notes of the version number when the changes are introduced. Remember that many folks are two or three releases behind and then when they do upgrade they can never seem to locate the instructions which results in unneeded queries that the folks who provide most of the support for Unraid have to deal with. Having an updated manual section that deals with these changes makes pointing these folks to find what they will have t
    2 points
  3. PLEASE - PLEASE - PLEASE EVERYONE POSTING IN THIS THREAD IF YOU POST YOUR XML FOR THE VM HERE PLEASE REMOVE/OBSCURE THE OSK KEY AT THE BOTTOM. IT IS AGAINST THE RULES OF THE FORUM FOR OSK KEY TO BE POSTED....THANKYOU The first macinabox is now been replaced with a newer version as below. Original Macinabox October 2019 -- No longer supported New Macinabox added to CA on December 09 2020 Please watch this video for how to use the container. It is not obvious from just installing the container.
    1 point
  4. This release contains bug fixes and minor improvements. To upgrade: First create a backup of your USB flash boot device: Main/Flash/Flash Backup If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg Bugs: If you discover a bu
    1 point
  5. DEVELOPER UPDATE: 😂 But for real guys, I'm going to be stepping away from the UUD for the foreseeable future. I have a lot going on in my personal life (divorce among other stuff) and I just need a break. This thing is getting too large to support by myself. And it is getting BIG. Maybe too big for one dash. I have plenty of ideas for 1.7, but not even sure if you guys will want/use them. Not to mention the updates that would be required to support InfluxDB 2.X. At this point, it is big enough to have most of what people need, but adaptable enough for people to create custom panels
    1 point
  6. Well, I'm good, but I didn't know I was that good! 🤣
    1 point
  7. Honestly this is pretty cool and I'm going to use it myself, thank you 😁 Just as a warning to anyone who decides to use this it's definitely worth taking note of above: This script also assumes your Default VM storage path is /mnt/user/domains/, if it's not, it will create a share called domains unless you update the references to this path. Also note that VM Manager needs to be started before you run the script if you are using the default Libvirt storage location which is a disk image that gets mounted when you start VM Manager. Otherwise when it gets started /mnt
    1 point
  8. That was the plan and it seems to work. It should be the default save since the others aren't really useful for much. Sorry for the delayed response, I don't get email notifications for some reason.
    1 point
  9. Tu peux tester sur n'importe quelle version 6.9 d'Unraid
    1 point
  10. Ha! Yeah I realize you are the same guy now. I was reading too quickly and overlooked that. Thanks again for the help! I will be ordering a dummy plug.
    1 point
  11. Wow! This forum is awesome. Such quick replies and willingness to help! Well, I am not sure which step got it to work but thanks to you both! When I initially tried the steps suggested by TAFKA Gridrunner it did not work. I had not yet restarted at that point though. So I restarted and in the meantime noticed SI1's response. I had not even thought to test it out using a real monitor! I made no further changes expect hooking it up to the monitor. And it all booted up just fine! Thanks to you both! I had been working on this one thing for almost 2 whole days to this point.
    1 point
  12. 1 point
  13. Ah okay zenstates in go isnt necessary for your cpu
    1 point
  14. 1 point
  15. Yes SimonF the normal console was functional.
    1 point
  16. I upgraded from 6.9.1 to 6.9.2 on both my servers with no problems. In fact I thought the upgrade went faster than normal. Not complaining one bit. You guys are awesome thank you for continue support of Unraid.
    1 point
  17. Howdy SimonF.....anything to help out the team!
    1 point
  18. Problem solved. I'm documenting this in case someone runs into the same issue. The last 2 lines had already been removed from the go file. touch /boot/config/modprobe.d/i915.conf worked, and I've rebooted since just to be safe, but the graphics card was still not working with Intel GPU Top nor GPU Statistics. I then noticed that my Windows VM was set to iGPU. I stopped the VM, changed this to VNC and re-started the VM. Boom. Everything is working. So there you go, if you're having a similar probl
    1 point
  19. OMG.... rsync is doing something. @JorgeB - I could kiss you on the face right now! I'll refrain until this is done and actually works or something Seriously, let me know how I can send you something as a token of my gratitude.
    1 point
  20. Ich habe dir hier geanwortet: https://forums.unraid.net/topic/105609-migrate-synology-docker-to-unraid/?do=findComment&comment=975782
    1 point
  21. Thats all you need. You don't need the containers itself. They contain only the app which can be re-installed at any time. The only requirement is to use the same docker container from the same maintainer and use the same container version. Creating a tar would be the first step. The only culprit could be the owner of the files. Unraid needs the user id 99 and group id 100 and Synology probably uses different ids. So it could be possible that you need to change the owner after extracting the files as follows: chown -R 99:100 /mnt/user/appdata/path_of_your_container
    1 point
  22. Hi @lnxd, thanks for checking, it at least confirms in not doing anything obvious and it should "just work". FYI no CPU maxing out, just for the first few seconds during bios start and then it all levels out. I have previously done the vendor ID, but i will re-do again as well as the other options as that was when i first started troubleshooting so i may have missed something out, i will let you know how i get on. The disablement of the SR-IOV in the BIOS was a line of thought i had been down in before, but made no difference @giganode Unfortunately yes, using the t
    1 point
  23. Server seems fine for his "workload". Within you NIXDESK I would passthrough the 1TB M2 directly to a Win 10 VM. So you are able to use your Win 10 Installation within a VM or if you want to boot directly from it, you can just boot directly from it 🙂 It should then looks like this: With this setting you can use your already installed and setuped Windows within Unraid as VM, and you are still able to boot directly from it. (If you want to). Keep in mind that just one VM at once can be booted up with passthrouged Graphicscards, USB-Controllers an
    1 point
  24. Which bonding mode? Do the ports show as up? i.e. have you tested with just one port no bonding.
    1 point
  25. Not arguing against docker-compose, but as a general rule, docker is docker is docker, and there aren't really any "Unraid Specific" images present.
    1 point
  26. Hatte ich ja versucht. Bin auch der Meinung, dass ich das getan hätte, aber ich habe ja hier erfahren, dass CA evtl. nicht sauber arbeitet. Muss ich heute Abend nach der Arbeit mal schauen. Melde mich, wenn ich es getestet habe. --------edit-------- ich habe mal wieder den container gelöscht und mit CA den Ordner gelöscht. Dieses Mal nachgeschaut und der Ordner ist wirklich gelöscht. Neu installiert und ich konnte die Seite wieder nicht laden. Das ganze mache ich über Safari auf einem Mac. Dann nichts verändert und parallel über Chrome auf die Seite zugegr
    1 point
  27. I would like to apologize to everyone for the way I posted my frustrations. I truly regret it and I deserve to. After a couple of days of testing, I was very happy that the UnRAID OS never failed in the slightest. The WebUI might be a different story. To be brief; I provisioned an SSL certificate via UnRAID and then didn’t want the “public” record of my WebUI address being available (least of all via “unraid.net”). My valid/proven “unraid.mydomain.tld” certificate worked (for a bit?), but it has no DNS/Public record. I’m pretty sure this screwed up the UnRAID flash dri
    1 point
  28. ...nutze es zwar selbst auch nicht, aber das ist - wie bei IPv4 keine Frage des "findens"....Du solltest ipv6 auf dem unraid host aktivieren (unter network-settings, network protocol) und dann solltest Du aus dem ipv6er Pool Deines Anbieters auch eine IPv6 vergeben können. Im Zweifel weiss Dein router welche noch frei, nicht vergeben sind und auch ausserhalb des dhcp6-pools sind
    1 point
  29. The two new drives have type 2 protection, so maybe that causing the issue. JorgeB posted this link a few years ago. http://talesinit.blogspot.com/2015/11/formatted-with-type-2-protection-huh.html Looks like do a low level format to remove the protection may make them usable.
    1 point
  30. Puh ipv6 nutz ich in Unraid nicht, da weiß ich jetzt gerad auch nicht weiter
    1 point
  31. Du kannst in den jeweiligen Container-Einstellungen das Netzwerk auf "custom br0" ändern, dann kannst du für den Docker eine IP aus deinem "normalen" Netzwerk festlegen
    1 point
  32. I connected all the power cords for the cpu and the motherboard, and later found out that it was a memory problem.
    1 point
  33. hi @Masterwishx! that's correct, when mounting gdrive using remote smb, the host machine with the google drive application must be online for unraid to find and use it. there are some containers in community applications that allow you to access your gdrive, but after looking at one or two of them, i was not impressed with the security work arounds incorporated by the containers. in fact, one container author even offered full disclosure that his private server was used to handle some of the traffic involved. while i appreciate that disclosure, i felt it was too insecure. for now, i still thin
    1 point
  34. Thanks all. I went ahead and renamed the network.cfg file and as hoped, and Unraid created a new one. I'm now able to access my shares files and am in the process of copying them over to my new unraid server.
    1 point
  35. nope, all good as long as you dont put extra stuff manually in the /www folder, then you should know what you doing.
    1 point
  36. Still 43? sudo apt install backport-iwlwifi-dkms Did you try this one?
    1 point
  37. @xthursdayx It is actually much easier than that. Simply copy the contents of your "/mnt/user/appdata/rutorrent/rtorrent/rtorrent_sess" into the following folder : "/mnt/user/appdata/binhex-rtorrentvpn/rtorrent/session" Everything should be good to go.
    1 point
  38. 1 point
  39. If you want to have 3 domains all point to your public WAN IP it is very easy to do. The Cloudflare DDNS container would update your main domains IP (yourdomain1.com ) by means of a subdomain . For example you would set the container to update the subdomain dynamic.yourdomain1.com to be your public WAN IP So then dynamic.yourdomain1.com will always be pointing to your public WAN IP. Then any other domains or subdomains that you want to point to your public WAN IP, you just make a CNAME in your cloudflare account which points to dynamic.yourdomain1.com So fo
    1 point
  40. I purchased the ASRock Rack E3C246D4U and there is a way to enable the iGPU without installing the beta BIOS. I'm currently running P2.30 with iGPU enabled. There is a key combination you need to press when booting your system. After powering on the boot splash screen will display the ASRock Rack image and the message “Updating FRU system devices”. When you see "Updating FRU system devices" press ctrl+alt+F3 and it will load the BIOS menu. In BIOS menu, you will see an additional page labeled IntelRC Chipset. Select System Agent (SA) Configuration, then Graphics Configuration,
    1 point
  41. [I just spent 3 hours documenting the step by step work I'd been doing on this for logging in this thread. I have the same UPS and the same errors and the same problems. I don't use unRAID though but I'm sure it's nothing to do with unRaid. I've spent several nights attacking this problem from a low level USB /HID driver problem. Then, 5 minutes ago, I tried something different. And it fixed it. What... the... No guarantees, but here's what I did: # usb_modeswitch -v 0x051d -p 0x0003 --reset-usb (Check lsusb output to find out your vendor a
    1 point
  42. Here is another key element to the UUD Version 1.5. This new datasource should have been created WITHIN GRAFANA if you follow Varken's default installation instructions. However, I thought it would be helpful for everyone to see it! NEW DATASOURCE FOR THE UUD 1.5 (VARKEN): Once setup, you should see 2 datasources. The default one we used for UUD 1.4 and prior (yours may be named differently than mine), and the new one named "Varken" which will be required for UUD version 1.5 onward if you want real time Plex monitoring.
    1 point
  43. Same. I now have catalina (instead of Big Sur which is what I chose) running though and I see the apple update thing for Big Sur. Can I update from with Mac OS Catalna to Big Sur or is that gonna cause problems? **EDIT** I completely deleted then reinstalled the container with method 2 instead of just changing after the vm was installed and it worked.
    1 point
  44. Self-replying as this is now resolved and I can get a sustained 300mbit+. The solution was to add a new variable to the Syncthing docker container named UMASK_SET with a value of 000. I'm using the linuxserver.io docker image and it appears permissions were the cause of the speed issues.
    1 point
  45. There are a few in this thread that have the same array/shutdown issue, but you've got a point that it may not be enough to pull it immediately. There is another thread on this forum about the startup message, and I cannot fathom how many people might be experiencing "can't shutdown" issues. I know I searched through the forum enough times and trawled through logs to find my own conclusion. Still, I still think it's important to highlight this link, so that others might find it. I disagree that this doesn't warrant further discussion, it definitely does, but certai
    1 point
  46. As docker's --link option is decrepated, we're no longer able to use multi-container apps like owncloud. Their only approach is now via compose. Am I wrong here? Also: people arguing that compose "is just a command line tool", while docker works in somewhat of the same way. It's a service with a CLI and some people built gui's, like the unraid guys. There are gui projects for compose going on outthere. No reason why the Unraid team shouldn't see this as a future project. 😉 And docker-compose is no longer available in the nerdpack. As I try not to mess with my unrai
    1 point
  47. The problem is when you have something like this https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml It would be nice to have in dockerman a way to configure something the way docker compose does it, as a group. In the UI all the dockers could be nested in only one, and lets say you will configure all the dockers in the same template. It should be hard since more changes are in the UI. Somehow dockerman teamplates could be as a dockercompose yml
    1 point
  48. is an example where something is not supported. the workaround is a hack.
    1 point
  49. I've tested these two options; 1) this Piwigo docker, accessing a separated mariadb instance. Rather complex and slow loading large amounts of images. 2) Piwigo, mariadb, nginx, php-fpm and CSF, all on 1 debian minimal VM. Both instances of piwigo access the exact same folders from an unraid share with terabytes of imagefiles. The second option performs noticeably faster, even without doing proper IO tests etc. The difference is so obvious, that I'm not even going to bother testing it with tools. Could be because I run unraid with a decent Xeon and 32GB RAM,
    1 point
  50. 09 Dec 2020 Basic usage instructions. Macinabox needs the following other apps to be installed. CA User Scripts (macinabox will inject a user script. This is what fixes the xml after edits made in the Unraid VM manager) Custom VM icons (install this if you want the custom icons for macOS in your vm) Install the new macinabox. 1. In the template select the OS which you want to install 2. Choose auto (default) or manual install. (manual install will just put the install media and opencore into your iso share) 3. Choose a vdisk
    1 point