Leaderboard

Popular Content

Showing content with the highest reputation on 03/30/21 in all areas

  1. They also said a GPU is required for the host and another for the guest. My take on it is that nothing changes except for less code 43 happening
    3 points
  2. Big News from NVIDIA Just a few hours ago, NVIDIA added an article to its support knowledge base regarding GPU passthrough support for Windows VMs. While we've supported this functionality for some time, it was done without official support from the vendor themselves. This move by NVIDIA to announce official support for this feature is a huge step in the right direction for all of our VM pass through users. This should also help instill confidence in users that wish to pass through these GPUs to virtual machines without the worry that a future driver update would break this functiona
    2 points
  3. Ich lösche eine evtl vorhandene Partition und nehme dann HD Tune Pro und mache die folgenden Tests jeweils 3x im Wechsel: Das dauert vielleicht 20 Minuten und dürfte denke ich 1% der Sektoren auf allen Magnetscheiben und Spuren umfassen. Zum Schluss schaue ich in "Health" ob sich die SMART-Werte verändert haben. Wenn nein, dann verbaue ich sie. Wenn dann wirklich noch defekte Sektoren vorhanden sein sollten, würde sich das ja beim Sync der Daten bemerkbar machen, aber bisher hatte ich so einen Fall noch nie. Immer wenn eine P
    2 points
  4. Hello Unraid Community! It has come to our attention that in recent days, we've seen a significant uptick in the amount of Unraid server's being compromised due to poor security practices. The purpose of this post is to help our community verify their server's are secure and provide helpful best-practices recommendations to ensuring your system doesn't become another statistic. Please review the below recommendations on your server(s) to ensure they are safe. Set a strong root password Similar to many routers, Unraid systems do not have a password set by default.
    1 point
  5. No. The age just set's an "mtime" value for the find command. So it will look for everything greater than 0 days old.
    1 point
  6. It should stay like that now that you've manually activated, you should be able to stop/restart the docker, and do "force update" and verify that it still works after that.
    1 point
  7. You can try the options in the link above, there's nothing to lose.
    1 point
  8. Doh! Sorry for not reading first. Confirmed resolved by the updated runc version.
    1 point
  9. see recommended post at top of the screen 'glibc causing random errors'
    1 point
  10. They need to be installed on the client as well. When connecting to a moded server the client ether a: downloads them from the server or b: marks them as subscribed and lets steam down load them, I'm not sure which... as far as I know the --crossplay flag only allows Epic clients to connect to un-moded servers...
    1 point
  11. Great! This solved my problem. Download unraid ZIP file, find the "go" file (doesn't have a extension), copy it to your server into /boot/config/ and reboot your machine. Thank you very much!
    1 point
  12. New nvidia driver out: https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-465-Linux-Beta
    1 point
  13. Hi Dan, Following this topic. Been having stability issues myself since upgrading to 6.9.1. Random kernal crashes, where i can only do a hard reset, and since 2 - 3 days unresponsive webgui, as in, i can log in, but after that nothing. On next hard reset i will enable sys log to flash too ;).
    1 point
  14. I realized that after posting the comment, but since the comment was still valid I decided to leave it One good side-effect of this last release issue is that it has prompted me to add syntax checking of the plugin's files to the scripts I use for automating deploying files and building the package so hopefully any such issue is less likely to make it into a release in the future.
    1 point
  15. Found the issue! i didnt had device_tags = ["ID_SERIAL"] set in [[inputs.diskio]] All working now!
    1 point
  16. As @limetech stated, I did open up a issue a couple of days ago on an internal bug tracker
    1 point
  17. Click on the disk, in the case above md4=disk4, then click the scrub button, after it's done look at the syslog for the list of corrupt files, then just delete them or restore from backups.
    1 point
  18. Yep right after I switched over to a VM they came out with native support for an SSD on the pi go figure but no regrets its been rock solid since starting it
    1 point
  19. @lnxd Maybe worth mentioning it's an 8 GB model of the RX 570 in here
    1 point
  20. SOLVED Well well, @JorgeB It seems you are my hero of the day! You got anything where i can tip you a drink? Thank you very much. It worked exactly as you said.
    1 point
  21. If Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.
    1 point
  22. A difference is that people here will not complain if you do not use ECC.
    1 point
  23. Try using mlxconfig to confirm SR-IOV is properly enabled on the card - step 3 here: https://mymellanox.force.com/mellanoxcommunity/s/article/howto-configure-sr-iov-for-connectx-3-with-kvm--infiniband-x Edit: You could probably follow the firmware update instructions in my post, but replace fw-ConnectX2-rel.mlx with fw-ConnectX3-rel.mlx I'm not sure if the format of the ini file is the same for ConnectX-3 though, ie this part: num_pfs = 1 total_vfs = 64 sriov_en = true Maybe export what's in the current config mstflint -d mtxxxxx_pc
    1 point
  24. SOLVED I have no idea how I solved it but here is what happened: I created a new usb stick with 6.9.1 on it. Copied all the config files from a backup of 6.8 on it. Restarted my server, selected the new boot drive and restarted. Then the server booted from the old (non functioning one) and... wel it suddely worked. Then proceded to upgrade it to 6.9.1 and everything is fine since. Thanks for your help!
    1 point
  25. At boot time only one of the cache devices (sdd) had a valid btrfs filesystem and it didn't mount with this error: Mar 27 20:11:45 Tower emhttpd: /mnt/cache mount error: Too many missing/misplaced devices This suggests the pool wasn't redundant, you can see here for some recovery options, from sdd only, but even if it works and the pool wasn't redundant it won't be complete.
    1 point
  26. The simplest option would be to mirror the syslog to flash:
    1 point
  27. Yeah I think it was the controller causing it to fail out. Been running for 4 hours in an external enclosure without an error.
    1 point
  28. Danke fürs Feedback. Leider doch nicht die 100 MB/s geknackt. Aber jetzt weißt du zumindest wie du es in Zukunft schneller bekommst
    1 point
  29. I wasn't aware the epic client supported mods. If you do not wish to use the steamCMD tools, then you will want to copy the mods from your PC (<pathtoARK>\ShooterGame\Content\Mods\) muber of the folder that contains the mod and the number.mod file, over to your unraid machine in <pathtoARK>/ShooterGame/Content/Mods/ then ether the modID in ether the Config/LinuxServer/GameUserSettings.ini as ActiveMods=2229978458,1083349027,1211297684 or add them to the docker "Game Parameters:" variable as ?GameModIds=ModID1,ModID2
    1 point
  30. Thank you for the ARK docker @ich777 ! I managed to get it to work even though it was a bit more complicated as I use the Epic Client and wanted to keep a password my server. What is the recommended way if I want to to install Mods on the ARK server?
    1 point
  31. Je reprends le message d'avertissement de @jonp qui mérite d'être aussi diffusé en français. Vous trouverez le sujet d'origine ici : https://forums.unraid.net/topic/104669-warning-unraid-servers-exposed-to-the-internet-are-being-hacked/ Bonjour à la communauté Unraid ! Ces derniers jours, nous avons constaté une augmentation significative du nombre de serveurs Unraid compromis en raison de pratiques de sécurité insuffisantes. Le but de ce post est d'aider notre communauté à contrôler que leurs serveurs sont sécurisés et de fournir des recommandations utiles sur les bonn
    1 point
  32. What version of windows 10? It's like I said with mellanox drivers, they're all kinda tied up in licensing crap... My suggestion would be to use something like 7zip to manually extract an older version of the drivers from the executable and then attempt manual installation. For windows and virtual functions, intel (and some chelsio) are really the only sure fire way to ensure compatibility thanks to the crap nvidia and mellanox have pulled with their drivers.
    1 point
  33. I'm sure someone will post it.
    1 point
  34. Do not run it as privileged. It's a big security risk. Binhex posted in the MinecraftServer (not MineOS) support thread that it can be temporarily fixed with a simple command (after every reboot), until it's permanently fixed in a future Unraid update:
    1 point
  35. Depending on how long your router allows DHCP addresses to be reserved and how often your server is offline will have a lot to do with determining if the server IP address can be assigned to another device. Some routers basically let DHCP assigned addresses persist permanently while others have a limit of 7 days or less. Once your server grabs the preferred address, nothing else should get that same address assigned unless the server is forced to give it up or is offline. I once had a router that did not make it easy to assign static IP addresses but allowed fairly lo
    1 point
  36. I think parity2 should be OK but after rebuilding disk3 you might run a parity check. In any case you will still have the original disk3 and should wait until you are confident in everything to do anything with it.
    1 point
  37. Regarding the icons and authentication, it seems the images are available at the same path in the unraid API docker. I pointed the base url at that port and now it works without authentication
    1 point
  38. Dann verwende doch einfach das existierende Beispiel von swag unter "/swag/nginx/proxy-confs/homeassistant.subdomain.conf". Setze deine Dyndns subdomain bei "server_name deinesubdomain.*;" ein. Dann ersetze "set $upstream_app containername" durch "set $upstream_app deine.ip.adr.esse"
    1 point
  39. How can I get mc to work with a mouse from the built in unRAID terminal accessible from the WEBUI?
    1 point
  40. Ich nutze den Original Plex Container und habe das und noch viel mehr manuell eingestellt: --no-healthcheck = kein ständiges Schreiben auf die SSD (siehe Bug Report) --mount = RAM-Transcoding + Netzwerk-Typ: Plex ID und Nutzerrechte: Lokale IP festlegen damit lokale Zugriffe nicht wie externe behandelt werden (um generelles Transcoding zu verhindern): + Pfade zu den Mediendateien (meine Musik liegt auf der SSD, daher /mnt/cache): Hardware-Transcoding aktivieren:
    1 point
  41. @limetech Here's what I did: Deleted the two files from /boot/config: rsyslog.cfg rsyslog.conf Rebooted Started the Array Reconfigured the Syslog settings Hit Apply Checked the Syslog and saw that rsyslogd started Verified that there was a file in my share Verified that data was in the file
    1 point
  42. @Squid I just tried deleting both files from /config and then stopping and restarting the array. This did NOT fix the issue. Same errors: Do I need to delete /etc/rsyslog.conf? Edit: And I also reconfigured the settings for Syslog.
    1 point
  43. maybe add a feature => buton to mark the topic as solved automaticaly, would be nice
    1 point
  44. I would recommend to switch to postgres11 instead of MongoDB. For me this caused a big improvement in upload speeds and also CPU utilisation. I posted how to set it up on the Nextcloud thread.
    1 point
  45. I don't think the OP posts in anyway "reassure" that it can be done. Code 43 is Nvidia anti-consumer way (which is their MO) to force people into buying expensive Quadro cards to use in VMs. Once you understand that, (most of the) potential fixes will become rather obvious i.e. just hide any potential clues to the Nvidia driver that it is running in a VM. If Hyper-V is on, it probably is in a VM ==> disable Hyper-V. Note: if you are going to disable / enable Hyper V, start a new template! Editing an existing template sometimes doesn't disable Hyper-V correctly - been ther
    1 point