Leaderboard

Popular Content

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

  1. Great Odin's Raven! Today's blog is a guide on how to set up a dedicated Valheim server on Unraid by @spxlabs! Want to set up a co-op with fellow Unraiders? Need help troubleshooting? Let us know below in the comments. SKOL! 🛡️ https://unraid.net/blog/unraid-valheim-dedicated-server
    3 points
  2. That is correct. Cache-no won't write any new files to cache, but it also won't move anything. You need to get things moved off cache. Disable Docker and VM Manager in Settings Set appdata, domains, system shares to cache-only Set Data and nextcloud shares to cache-yes Run mover without the plugin Wait for it to complete then post new diagnostics.
    2 points
  3. Hello, i have set a Unifi Controller docker and gave it his own ip address, but i also want to make a static assignment on pfsesne. Do anyone know if dockers change mac address when they are updating or whenever? Except in the case i delete and reinstall them i guess. Is there any way to set a custom mac address? --SOLUTION-- I should do a better web search before, for anyone who might need this.. Edit container and on extra parameters add "--mac-adress 02:42:xx:xx:xx:xx" use a mac from a range of 02:42:ac:11:00:00 to 02:42:ac:11:ff:ff as this address are meant for dockers. I dont know it if works for macs out of this range
    1 point
  4. KlugscheesserMode ON: ...eine normale SATA, Consumer SSD schafft das nicht....die Crucial hat max. 500-550MB/s....also nur die Hälfte eines 10GBE Netzwerk-Links.
    1 point
  5. Nasty!, i hate ransomware - https://www.bleepingcomputer.com/news/security/massive-qlocker-ransomware-attack-uses-7zip-to-encrypt-qnap-devices/
    1 point
  6. This is documented here in the online documentation.
    1 point
  7. I see, probably there's a new 'api' to get the other cache pools. I'll take a look, but it might take a bit of time.
    1 point
  8. That's exactly where it was. I enabled the C-states option, and then set the idle current to typical instead of low. I've also created a Docker specific vlan, and moved all of the br0 over to br0.x so hopefully that will keep my call traces and kernel panics at bay. I will update if anything changes. So far so good, but it has only been about 18 hours or so. Longest it has gone in the past was 10ish days. So if I can hit 2 weeks+ I'll consider it a win.
    1 point
  9. Have a read of this.. https://forums.unraid.net/topic/77178-move-docker-image/
    1 point
  10. There is also the fact that the "prefer" setting works even if you do not yet have a cache drive and then later when one is added content gets moved to the cache without further user action. However it does cause a problem if a cache temporarily disappears for some reason as then you can end up with duplicates of files in the system share such as the docker image. Not sure I can see how this could be avoided though.
    1 point
  11. appdata, domains, system shares are cache-prefer by default. This setting is similar to cache-only, but it allows overflow to the array. The point being to keep the files on cache for better performance. And to allow array to spin down, since those shares always have open files when dockers or VMs are enabled. I see these sorts of problems all the time because users don't understand this setting. The webUI has been enhanced with more obvious and complete descriptions of what these do, but nobody bothers to read it seems. There is no single word that adequately explains cache-yes and cache-prefer. Maybe a different word besides prefer would lead to less misunderstanding, but I don't know what that word is. Maybe a warning would make them take the trouble to understand, but often even if they do read they still don't understand. Also see this FAQ:
    1 point
  12. I'll amend the bit I added to the documentation to mention that you can use 'start' if you have already created the container, and use run if you want to either redownload the container or change a setting. I think for practical purposes that is the difference? I perhaps also need to explain how the image name is set up and used?
    1 point
  13. Not your fault. It's confusing because Unraid has evolved and changed immensely over the years, and some legacy settings haven't been renamed because of inertia and nobody came up with a universally accepted way of upending tradition and starting over with new terminology.
    1 point
  14. That should allow you to move other shares data off cache without getting those shares involved. Not until you move the other data off cache to make room.\ You have a couple of other shares set as cache-prefer that should probably be cache-yes, and that is almost certainly your problem. These shares are anonymized as D--a and n-------d. Set those to cache-yes, set appdata, domains, system to cache-only, run mover without the plugin, wait for it to complete, then post new diagnostics.
    1 point
  15. Make sure the cable has no tension that might cause it to pull on the connection. Bundling cables to make them neat can sometimes cause problems.
    1 point
  16. Since I do not know of any specific plans to add this feature to unRaid I have added a section here on what can be done in the meantime to easily set up such a schedule (in the Docker section of the online documentation that can be accessed via the Manual link at the bottom of the unRaid GUI). I would be interested to know if this is considered sufficient in the short term or more detail is needed?
    1 point
  17. Leider nein. Muss man mit dem Dremel dran: Warum verbauen die eigentlich geschlossene Slots. Versteh das mal einer.
    1 point
  18. Problem gelöst, der Fehler war das kein UEFI bootfähiger Datenträger angeschlossen war... Danke trotzdem
    1 point
  19. Kann es vielleicht der integrierte Kartenleser vom Midi-Tower sein?
    1 point
  20. I started getting read errors all over the array. I started to suspect the LSI00244 9201-16i expander card. I have since replaced the card with 2 8X cards and i am running a parity check. Checked all cables and connections. Heres to hoping its just that card.
    1 point
  21. No, and those errors after spin down are not that uncommon, and not a real problem, sometimes changing the disks APM level or disabling it helps.
    1 point
  22. Not the disk errors, looks like disks 9 and 10 dropped offline.
    1 point
  23. Geh mal an den Server und melde dich an. Dann führe die beiden Kommandos aus: lsscsi -v lsblk Dann zieh den Unraid Stick raus und warte ein paar Sekunden und wiederhole die Kommandos. Ist sda bzw das Gerät 0:0:0:0 noch da? Danach Stick wieder rein und Server neu starten. Kann auch sein, dass er abstürzt. Weil Stick soll man nicht im Betrieb ziehen. Also bitte nicht machen während Docker usw läuft.
    1 point
  24. ...Partitionen wären dann aber eigentlich sdX1, sdX2, ... Er hat oben ja sogar eine eigene LUN Adresse auf dem scsi Bus.... 🤔 Irgendein Device muss ja da sein, sonst wäre die LED beim Pluging nicht grün. Kann man für USB im BIOS ein Raid konfigurieren?
    1 point
  25. It's normal, and can be replicated on every OS out there. Here's how this works. The OS (in this case Windows) attempts to do a rename. This fails (because your cannot rename from \\media\,,, to \\downloads\... the same way that you cannot rename from C:\... to D:\...), so it has to do a copy / delete operation. MC operates below the system, and because of that it does succeed in the renaming, so it's instantaneous. To work around this what you need to do is set up a "root share" (space invader one has a video about that). Then the mount points are the same and you're renaming instead of copying / deleting, because you're going from \\rootshare\media to \\rootshare\downloads) There are some caveats with that however. If you did have include / exclude disks or use cache settings different between the two shares, then the renamed file may wind up on the wrong disk (it'll actually stay on the source disk) in apparent violation of the rules, but it's actually not a violation because you're bypassing the system
    1 point
  26. The description actually says that you simply have to restart the container if a update of the game is released: The reason why I asked @Snipe3000 is because I implemented also a update script (because many user requested it) that will check automagically if a newer version is available every hour and restart the container if a new version is found if this variable is set to 'true':
    1 point
  27. That worked, thanks. I added a dummy HDMI key to the on-board GPU and now both are working. Also as a follow-up for anyone else enabling a UHD 720/750 iGPU, I added these two lines to: /boot/config/modprobe.d/i915.conf options i915 force_probe=4c8a options i915 enable_guc=2 The second was required to enable hardware VP9 encoding and additional HEVC encoding profiles root@9362b3a147fb:~# vainfo error: XDG_RUNTIME_DIR not set in the environment. error: can't connect to X server! libva info: VA-API version 1.11.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_11 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.11 (libva 2.11.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 21.1.3 (bec8e13) vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI VAProfileHEVCMain : VAEntrypointEncSliceLP VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointEncSliceLP VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointEncSliceLP VAProfileVP9Profile1 : VAEntrypointVLD VAProfileVP9Profile1 : VAEntrypointEncSliceLP VAProfileVP9Profile2 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointEncSliceLP VAProfileVP9Profile3 : VAEntrypointVLD VAProfileVP9Profile3 : VAEntrypointEncSliceLP VAProfileHEVCMain12 : VAEntrypointVLD VAProfileHEVCMain12 : VAEntrypointEncSlice VAProfileHEVCMain422_10 : VAEntrypointVLD VAProfileHEVCMain422_10 : VAEntrypointEncSlice VAProfileHEVCMain422_12 : VAEntrypointVLD VAProfileHEVCMain422_12 : VAEntrypointEncSlice VAProfileHEVCMain444 : VAEntrypointVLD VAProfileHEVCMain444 : VAEntrypointEncSliceLP VAProfileHEVCMain444_10 : VAEntrypointVLD VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP VAProfileHEVCMain444_12 : VAEntrypointVLD VAProfileHEVCSccMain : VAEntrypointVLD VAProfileHEVCSccMain : VAEntrypointEncSliceLP VAProfileHEVCSccMain10 : VAEntrypointVLD VAProfileHEVCSccMain10 : VAEntrypointEncSliceLP VAProfileHEVCSccMain444 : VAEntrypointVLD VAProfileHEVCSccMain444 : VAEntrypointEncSliceLP VAProfileAV1Profile0 : VAEntrypointVLD VAProfileHEVCSccMain444_10 : VAEntrypointVLD VAProfileHEVCSccMain444_10 : VAEntrypointEncSliceLP root@9362b3a147fb:~#
    1 point
  28. Eine Parität enthält keine Dateien, sondern nur eine Art "Quersumme" der Dateien aller Datenplatten (nennt sich XOR). Aus dem Grund kann eine Parität problemlos 1 von 10 verschiedenen Platten gegen Ausfall schützen. Man braucht also nicht 10 Paritäten für 10 Platten, geschweige denn den selben Speicherplatz. Du kannst dir das ungefähr so vorstellen (erklärt nur grob die Funktionsweise, XOR geht anders): Platte 1 = enthält eine Datei mit dem Inhalt "12" Platte 2 = enthält eine Datei mit dem Inhalt "7" Platte 3 = enthält eine Datei mit dem Inhalt "5" Parität = enthält "24" Fällt nun Platte 3 aus, kann man einfach 24 - 7 - 12 = 5 rechnen und den Inhalt der Platte 3 wiederstellen. Und wie du siehst ist die Menge der Datenplatten dabei irrelevant. Unendlich, aber max 2 dürfen zur selben Zeit ausfallen. Korrekt. Oder du lässt die 2. Parität einfach weg und nutzt sie als Datenplatte. Es hängt einfach davon ab wie betriebssicher dein Server sein soll. Du könntest genauso gut auf eine Parität verzichten und im Falle eines Ausfalls dein Backup wiederherstellen (was du hoffentlich erstellst). Die Parität erhöht also nur den Komfort. Ein Unternehmer würde niemals darauf verzichten, weil ihn so eine Wiederherstellung wo er nicht weiter arbeiten kann, Geld kosten würde. Eine Privatperson kann dagegen abwägen. Ich gönne mir zB ein bisschen Komfort (und den Stress mit der Regierung ^^), weshalb ich 1 Parität bei 7 Datenplatten einsetze. Bevor ich aber eine 2. Parität verbauen würde, würde ich erst mal meinem Backup-Server eine verpassen. Der hat nämlich keine.
    1 point
  29. To clarify, it is a replacement server or a secondary server ? If it is a a server replacement, you could copy your .key file to your trial drive. I think it is in the config folder.
    1 point
  30. Stop Docker and VM services under Settings Change Use Cache setting to Yes Run mover from Main tab to get files moved to array When ready to move them back: Change Use Cache setting to Prefer. Run mover from Main tab to get files moves to pool (cache) (optional) set Use Cache setting to Only to stop option for them being created on array in the future.
    1 point
  31. It's 192.168.50.2 that you're assigning it that's in use by something else, in this case presumably your server since that's the SERVERIP variable you've done. If you're running on br0, you need to assign it a unique address (and keep ServerIP pointed at your server)
    1 point
  32. Hi All , in case you own the firewall in the subject and (like me) are currently going crazy with certbot (SWAG and similar) failing the verification challenge, be aware that on the Netgate forum users are indeed reporting that NAT (pure or reflection) is currently broken . Just FYI in case you are sweating like me :) Cheers, PFsense CE 2.5.1 NAT broken on interface != default WAN | Netgate Forum
    1 point
  33. Welchen verwendest du? Wenn beide (teilweise) die selben Verzeichnisse verwendet haben, ist das durchaus möglich. Ich dachte der Nextcloud-Container zeigt keine IPv6 an? Wo hast du die IPv6 denn abgelesen, die die Fritz!Box nicht akzeptiert?
    1 point
  34. Good answer, this question gets asked so often, I wish someone would just include it in dev tools or something. Clearly there's demand.
    1 point
  35. Funnily I have completely the same after upgrading from 12TB Ultrastar to 18TB White Label, why I wrote this script: https://forums.unraid.net/topic/106508-force-spindown-script/ But I was not able to test 6.9.x by now. Maybe it does not happen there?!
    1 point
  36. 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 to add (mods). Maybe I'll revisit this in a few weeks/months and see where my head is at. It has been an enjoyable ride and I appreciate ALL of your support/contributions since September of 2020. That being said @LTM and I (mostly him LOL) were working on a FULL Documentation website. Hey man, please feel free to host/release/introduce that effort here on the official forum. I give you my full blessing to take on the "support documentation/Wiki" mantel, if you still want it. I appreciate your efforts in this area. If LTM is still down, you guys are going to be impressed! I wanted to say a huge THANK YOU to @GilbN for his original dash which 1.0-1.2 was based on and ALL of his help/guidance/assistance over the last few months. It has truly been a great and pleasurable experience working with you man! Finally, I want to say a huge thanks to the UNRAID community and its leadership @SpencerJ @limetech. You guys supported and shared my work with the masses, and I am forever grateful! I am an UNRAIDer 4 LIFE! THANKS EVERYONE!
    1 point
  37. more searching and then I found this which is the missing piece - whatever that is/does : /etc/rc.d/rc.php-fpm restart
    1 point
  38. Taking just this info from you that I quoted, the way to accomplish this is to go to tools, and do new config. That will allow you to change any assignments you want, and will overwrite any drive assigned to parity slot(s) and leave the data drive slots content untouched. Any new drives you add will need to be formatted after the array is started with the new configuration.
    1 point
  39. https://hay-kot.github.io/mealie/ I would love to see “mealie” as a unraid docker container. looks pretty cool for us cooks,
    1 point
  40. Don't forget you need to map that same directory where your bitwarden log file is into your swag container. Then also make sure the path in the bitwarden_rs.conf file for fail2ban has the same "container" path. This is mine for example: Bitwarden (I manually created the dir and made it nobody:users 777 since bitwarden seems to be running/setting root for all 🙂 ) Swag: Swag fail2ban / filter.d / bitwarden_rs.conf file: # https://github.com/dani-garcia/bitwarden_rs/wiki/Fail2Ban-Setup # - Set up logging to file > https://github.com/dani-garcia/bitwarden_rs/wiki/Logging # - Set logging level to warn or error # Logged in /bitwarden-log/bitwarden.log [Definition] failregex = Username or password is incorrect\. Try again\. IP: <HOST>\. Username: .*\.$ ignoreregex = Swag / fail2ban / jail.local file entry: [bitwarden_rs] enabled = true port = http,https filter = bitwarden_rs logpath = /bitwarden-log/bitwarden.log bantime = 3600 findtime = 3600 maxretry = 3
    1 point
  41. Thanks for the help in this post, works fantastically. TL;DR of original, here's a step by step guide for creating a mount on VM creation (as of unraid 6.8.3). In the "Unraid Share" section, select the unraid folder that you want to make mountable. This can be an individual share or a parent directory of the share for multiple. e.g `/mnt/user` In the "Unraid Mount tag" section, enter a tag name, this can be anything and will be passed to the VM. e.g `myMountTag` Complete VM setup, power on and install your VM OS or normal. The following steps require root/sudo user. Make a backup copy of fstab in case you mess up your configuration `sudo cp /etc/fstab /etc/fstab.orig` Create a target mount directory where you want to mount your share e.g. `sudo mkdir /path/to/myMountedDir` Edit `/etc/fstab` config by adding the following line to the end of the file, (change tag & path to your needs) `myMountTag /path/to/myMountedDir 9p trans=virtio,version=9p2000.L,_netdev,rw 0 0` Save fstab file and run `sudo mount -a` to check your mount works (there should be no output for on success) You should now have a mounted share in your VM Futher detail For anyone new to unraid, looking for an explanation as to what the fstab values are, here is an explanation <device>: myMountTag <mount point>: /path/to/myMountedDir <file system type>: 9P (The protocol that QEMU uses for a VirtFS) <options>: trans=virtio,version=9p2000.L (our transport for this share will be over virtio, and we specify the 9P version (2000.L) because the default for QEMU is 2000.U. "L" has better support for ACLs, file locking and more efficient directory listing, deletion edge cases etc) _netdev (tells the system that this mount relies on the network, and to delay the mount until a network is enabled) rw (mount as read/write) <dump>: 0 (disables backup via the dump command) <pass num>: 0 (disable any error checking) Cheers!
    1 point
  42. Hi thanks for posting the solution. This helped me make sure by modem doesn't change the asigned ip of my docker container. Also please note thate there is a typo in your example. It should be --mac-address not mac-adress
    1 point
  43. Wrong place to look for the share. Press the + sign on the screenshot I quoted above (look to the right of "sdb"), it will expand to show you the mountpoint, which is the same as the "share". It is normally rather cryptic but you can rename it to something more useful (click on it and type in new name and then enter)
    1 point
  44. The Unraid OS is in RAM. Plugins are reinstalled at boot but anything you want to install from the command line will have to be scripted to run at boot with the User Scripts plugin.
    1 point
  45. Also a screen session can cause this - easy to forget they might still be hanging around
    1 point