Leaderboard

Popular Content

Showing content with the highest reputation on 01/06/23 in all areas

  1. Welcome to the friendliest server community around! Tl;dr version: Be nice and cordial. Don't be a jerk or do post anything illegal. This forum is where our users can collaborate, learn, and provide input on new developments from Lime Technology and its partners. We have a strong team of community moderators, devs, and Lime Technology employees who strive to help as many people as possible. Participating in this forum means agreeing to the following community guidelines and rules. These guidelines and rules must be agreed and adhered to to use this forum. Moderators and Lime Technology staff will enforce the community guidelines at their discretion. Anyone who feels a posted message doesn’t meet the community guidelines is encouraged to report the message immediately. As this is a manual process, please realize that it. may take some time to remove, edit or moderate particular messages. Rules and Community Guidelines To ensure a safe, friendly and productive forum, the following rules and guidelines apply: Be respectful. Respect your fellow users by keeping your tone positive and your comments constructive and courteous. Respect people's time and attention by providing complete information about your question or problem, including product name, model numbers and/or server diagnostics if applicable. Be relevant. Make sure your contributions are relevant to this forum and to the specific category or board where you post. If you have a new question, start a new thread rather than interrupting an ongoing conversation. Remember this is mostly user-generated content. You'll find plenty of good advice here, but remember that your situation, configuration, or use case may vary from that of the individual sharing a solution. Some advice you find here may even be wrong. Apply the same good judgment here that you would apply to information anywhere on the Internet. The posted messages express the author's views, not necessarily the views of this forum, the moderators, or Lime Technology staff. As the forum administrators and Lime Technology staff can’t actively monitor all posted messages, they are not responsible for the content posted by users and do not warrant the accuracy, completeness, or usefulness of any information presented. Think before you post: You may not use, or allow others to use, your registration membership to post or transmit the following: Content which is defamatory, abusive, vulgar, hateful, harassing, obscene, profane, sexually oriented, threatening, invasive of a person’s privacy, adult material, or otherwise in violation of any International, US or State level laws is expressly prohibited. This includes text, information, images, videos, signatures, and avatars. Also: "Rants", "slams", or legal threats against Lime Technology, another company or any person. Hyperlinks that lead to sites that violate any of the forum rules. Any copyrighted material unless you own the copyright or have written consent from the owner of the copyrighted material. Spam, advertisements, chain letters, pyramid schemes, and solicitations. (Note: we have an Unraid Marketplace Board that includes a Good Deals section and a Buy, Sell, Trade section, and they have their own rules.) You remain solely responsible for the content of your posted messages. Furthermore, you agree to indemnify and hold harmless the owners of this forum, any related websites to this forum, its staff, and its subsidiaries. The owner of this forum also reserves the right to reveal your identity (or any other related information collected on this service) in case of a formal complaint or legal action arising from any situation caused by your use of this forum. Please Note: When you post, your IP address is recorded. Repeated rule violations or egregious breach of the rules will result in accounts being restricted and or banned at the IP level. The forum software places a cookie, a text file containing bits of information (such as your username and password), in your browser's cache. Cookies are ONLY used to keep you logged in/out. The software does not collect or send any other form of information to your computer. Lime Technology may, at its sole discretion, modify these Rules of Participation from time to time. For Unraid OS software, website and other policies, please see our policies page! If you have any questions, please contact support.
    7 points
  2. This is a Robocopy issue. Ran the following command and all was fine, the destination folder didn't "disappear". Key part is the "/A-:SH" flag at the end. robocopy /E /R:5 /W:2 "D:" "\\NEBULA\Backups\FiLaptop\New 06-01-2023" /XF ._Thumbs.db /XD "D:\$RECYCLE.BIN" /A-:SH Stackoverflow post Blog post with the solution to "unhide" the folder again, and the flag to add to robocopy command to prevent this happening in the first place
    2 points
  3. CA Appdata Backup / Restore v2.5 Welcome to a new epsiode of the appdata backup plugin The previous thread is located here: https://forums.unraid.net/topic/61211-plugin-ca-appdata-backup-restore-v2/ What happened? I stumbled upon some bugs while using Squids plugin and made pull requests. Squid told me, he has only limited time and asked me if I want to publish a new version of the plugin. So we decided to deprecate his version in favor of "my" version. For now, the plugin has fixed for error detection and some other new features (see changelog). More to come. Anything I should consider? YES! Since the updated version shows you error during backup/verification (and even while stopping/starting containers), it COULD happen, that you see errors after update which were not there before. In most cases, these errors/warnings were there before but supressed. Errors like "File changed as we read it" or "Contents differ" (during verification) tells you, that some files are still in use. Post here (with your log) in that case.
    1 point
  4. Unraid貌似用了r8169这个驱动来驱r8125,比较老。r8152也是很老的1.12版本,好像驱不动R8156。 以下补丁基于6.11.5定制,加了最新的V9.010.01的r8125 2.5G PCI网卡驱动和V2.16.3的r8156 2.5G USB 网卡驱动。解压后把所有文件覆盖到U盘根目录重启即可。覆盖前记得备份原始文件。 默认自带r8169的驱动,支持板载网卡r8169和USB网卡r8156共存的情况。 如果不需要r8169,需要r8125 PCI网卡的驱动,可以靠如下blacklist屏蔽掉。命令行跑一次,会存到U盘,重启看看。 echo "blacklist r8169" > /boot/config/modprobe.d/r8169.conf 如果需要r8169和r8125共存,这个比较麻烦,建议换个网卡吧。这个改动需要改bzfirmware文件。bzfirmware里面东西太多,不好改,有需要可以自行去bzfirmware内删掉r8169内置的r8125固件,重新打包(未测试,只是建议可以尝试下)。 原生Unraid内核之外的补丁修改部分: 1. 修改了ACS Override补丁,支持某些主板的IOMMU分组补丁。 2. 增加R8125驱动,修改打开了队列支持和关闭了ASPM节能。 3. 增加R8156驱动,修改了支持最新的Unraid的Linux5.19内核。 只是供测试,如果感觉不稳定,用原始文件覆盖回来,重启就能恢复原状了。 免责声明: 补丁只是用于测试,请勿使用于重要的数据服务器,如果出现数据丢失等情况概不负责。谢谢。 下载链接在: 链接: https://pan.baidu.com/s/1987agT_JHTv6QT3ds1olqg?pwd=zapu Mirror (Google Drive): https://drive.google.com/drive/folders/1wA9UNejVllZfBTjDQ-pquJ-Bx4Tlqluk?usp=sharing 里面还有6.11.3, 6.11.1, 6.11.0, 6.10.3, 6.9.2和6.9.1版本的,都是加了最新的驱动。有兴趣也可以使用。 已知问题1: Unraid内部似乎加了些版本检查的限制,新版本的补丁无法新建队列配置文件,会出现Stale Configuration的提示。有个妥协的办法就是先在原始文件里面将阵列启动好,生成阵列配置文件之后,再替换补丁重启。除非换硬盘,一般阵列配置也不会重新配置。 已知问题2: 某些r8125网卡在Unraid的共享目录拷贝速度跑不满280MB,只有140MB左右,可能跟主板设计或配置或桥接有关。有网友发现关掉Unraid网络配置的br0桥接,使用macvtap,可以跑满速度。推荐使用这种办法,虽然麻烦一些,但是速度确实不受影响了。 例如虚拟群晖,推荐第一个macvtap网卡使用群辉的MAC地址,第二个网卡随意MAC地址,参考本帖第三页 @benwwchen 网友的帖子。
    1 point
  5. Just a quick warning. Because i wanted a new faster controller card to replace my AAR-1430SA i grabbed a rather cheap (30€) Sata controller card with ASM-1166 chipset from Amazon. Okay they shipped a different model than it was advertised on the photos but okay, nearly all of the ASM1166 are unlabled etc. You can only differ them by the board Layout etc. What i got was that here: Using it resulted in kicked out drives etc. For gods sake with much help here in the Forum the situation was manageable. I dont know if the card is faulty or if the model is crap, but at least i could return it to Amazon. What i ordered now was a bit more expensive model, hopefully it works better: https://smile.amazon.de/dp/B09K4WKHKK?psc=1&ref=ppx_yo2ov_dt_b_product_details
    1 point
  6. Rebuild went okay, seems that everything worked out. Files are readable at least. Its mainly Media files, so if there is a bitflip anywere it is not the end of the world. That is the ASM1166 Card card which seemed to be faulty, there is no labeling etc: I have returned it to Amazon and ordered another one: https://smile.amazon.de/dp/B09K4WKHKK?psc=1&ref=ppx_yo2ov_dt_b_product_details Hopefully that works better.
    1 point
  7. Danke, habe es mit meiner auch gerade getestet. Es funktioniert sehr gut. Und sie ist wirklich sehr sparsam.
    1 point
  8. The default is high-water, if a share is set to say split between disk1 and disk2 it'll start writing on disk2 once free space on disk1 is less than half the free space of disk2. So looking at that screenshot if it was the case above it'd start writing on disk2 pretty soon, seems normal.
    1 point
  9. Servus @Eldra ist in der rar der komplette Unraid Stick inkl. deiner Lizenz? Falls ja sofort das teilen beenden und den link löschen. Danach würde ich mal einen Monitor anschließen und da mal sehen wie weit er booted bzw. was da so angezeigt wird
    1 point
  10. Thanks! The subvolume creation created the new share as you indicated. I then used the UNRAID GUI to finish configurating the new share, moved data into the new share, and took a snapshot successfully.
    1 point
  11. Hi, this will be fixed in the next My Servers plugin release. Thanks!
    1 point
  12. You were both right, I was looking to do too many steps at once, but rebooting after adding the parity then adding the other disks worked fine, all is good now! Thank you
    1 point
  13. have a look at NAME_SERVERS, lots of people have had issues with name resolution, link to comment on delugevpn support thread but its the same code as qbittorrentvpn:- for more detailed comment:- also mention of fixing privoxy by resetting config, so delete /config/privoxy and restart container.
    1 point
  14. @b3rs3rk I've opened a PR on GitHub to fix the issue with the AMD GPU. They'll be properly shown in the GPU Settings now. https://github.com/b3rs3rk/gpustat-unraid/pull/50
    1 point
  15. Witzig, genau mit dem Thema hab ich mich auch unabhängig von diesem Thread auseinandergesetzt und bin erst nach Einkauf und Verbau genau dieses U-56n 8GB Sticks auf den Thread gestoßen. Das Ding ist anscheinend rund 175x so haltbar wie ein Samsung Bar Plus (wenn man dem Video von Spaceinvader One folgt), der nur 29 volle Schreib- und Lesevorgänge überlebt hat (< 1 TBW). Der U-500k wäre nochmals DEUTLICH langlebiger, aber ich bin auch auf den Trichter gekommen, dass diese Verbesserung nicht den Preis von 200€ wert ist und denke dass man mit einem U56n extrem gut bedient sein wird. Der Umstieg mit dem Creator Tool ist leicht, die Sticks haben alle eine eindeutige GUID, so dass die Registrierung des Keys keine Probleme darstellt. Ich habe das auch mal für die englischsprachige / internationale Community ausführlich zusammengefasst:
    1 point
  16. 1 point
  17. Because it uses 8b/10b encoding, so it becomes 4.8Gbit/s=600MB/s
    1 point
  18. For all linuxserver containers, the best place to ask for help is via their Discord (Click on the container in question and select Discord)
    1 point
  19. I had an issue this morning but figured it out @binhex, thank you for your support, I found an old post of yours that worked for my issue.
    1 point
  20. Krusader ist nicht die Lösung da er selber auch ein Docker ist. Gehe in die Shell Und öffne dann den MC Unter /mnt/user siehst du dann die Shares Vorteil beim MC du kannst Docker und VMs deaktivieren damit kannst du dann auch Dateien löschen die eigentlich in Verwendung wären. Greets
    1 point
  21. Might be an issue with my motherboard, that's been on my mind for ages, but since the HW where I'm running my system fell into my lap...have to get most of it, even if it means having the same issue as you (no array, no services) To expand a bit, my server is a Dell Precision Tower T7910, in the MB there are several PCIe slots, flagged with different wattage, I have the GPU using one of them flagged as 225w, the controllers are in the ones flagged as 75W. SO MY PROBLEM IS MOST LIKELY THERE I have also pending to test a "temporary solution" which would be see how it reacts if I turn it off and turn it on again (the D800S) using a smartplug once the server is up, but tbh this option scares me a bit. My plan in the future is replace my desktop Ryzen 3700 with a 5900x and move my unraid setup into it, so that's why I didn't give it much thought to the disks issue. Worst case scenario I'm out of Plex until I'm back, but I understand that there's people running more critical stuff than me. Anyway, the main thing is that Unraid supports and detects the expansion unit without issues
    1 point
  22. OK, parity check completed and it indeed corrected the errors. Thank you 🙂
    1 point
  23. Sehr schön, dann frohes schaffen!
    1 point
  24. Nettes Angebot, aber so ne Karte bekommt man ja heute für kleines Geld. Hab für meine 35 pro Stück bezahlt.
    1 point
  25. Merci Daen, Je me suis justement aidé de ce tuto et également celui de votre forum totoleouf 🙂 Et le transcodage fonctionne parfaitement.
    1 point
  26. So far so good. This appears to be a solid fix for my recent reboots.
    1 point
  27. Habe jetzt eine HP NC522SFP eingebaut aber leider hab ich zu dieser Karte keine Bracket. Bekomme die Tage noch eine Intel X520 DP die ich dann auch mal ausprobieren werde.
    1 point
  28. Mit dem Dynamics File Manager konnte ich alle Daten löschen und somit auch die Shares. Appdata habe ich ebenfalls damit bereinigt. Ich konnte soeben die Nextcloud Installation sauber durchführen. Nochmals vielen Dank.
    1 point
  29. Das ist eine gute Frage, ich seh mir das dann mal an.
    1 point
  30. 使用 unbalance 插件的分散模式,将一个盘下某个的文件夹平均分散到多个其他盘或者单个其他盘。如下图是把磁盘1的appdata文件夹移动到磁盘3下。 使用 Dynamix File Manager 插件,选择移动即可。如下图是把磁盘1的appdata文件夹移动到磁盘3下。 使用文件管理类 Docker 容器。如 FileBrowser、Krusader 等。需注意要将 /mnt 文件夹映射到容器内。 进入命令行,cd 到 mnt ,执行 move 源目录 目标目录。如下命令是使用绝对路径(不需要 cd )把磁盘1的appdata文件夹移动到磁盘3下。 move /mnt/disk1/appdata /mnt/disk3
    1 point
  31. Yes, I have 2 D800S on my server and the "only" issue I encountered is that not every disk spins up on startup, which makes me take it out and put it back in again, other than that the units run fine
    1 point
  32. As an update, preclear finished successfully this time around. Installed into array as parity drive, rebuilt successfully and seems to be working fine. SMART test also showed no errors. As mentioned above, the errors were like due to some USB issue and not disk fault.
    1 point
  33. The startup of the container can take some time, especially the step "55-jdownloader2.sh: executing..." if you have a lot of stuff under "/output".
    1 point
  34. Beware that this is one of those "overfilled" boards, which means, you cannot use everything at the same time. For instance, you only get the Sata Ports 5-8 if you disable the onboard wifi! And, if using a "G" type processor, you can only add 3 NVMe SSDs into the 16x slot instead of the 4 that the hyper card could hold. But yes, the board runs fine. I have 128Gigs of RAM, and 5 NVMe drives in use, 10Gbe LAN in Slot and 2*4 Port SATA controllers too. this gives a total of 16 sata connectors.
    1 point
  35. It always checks for the keyfile before starting the array, if it is there it tries it first and complains if it doesn't work. If it is missing it prompts for you to enter the password
    1 point
  36. Alles eingebaut. Die Intel X710-DA2 für den Server kam heute auch. ASPM ist komplett aktiv: Den C-State C7 erreicht der Server mittlweile zum Glück auch - mal sehen welche VM ich noch irgendwie auslagern kann. Die Tage werde ich nochmal die Kabel etwas schöner verlegen. Die nachträglich eingeklebten Gummi-Matten schlucken die Vibrationen wie gewollt - lautstärke-technisch bin ich aktuell zufrieden.
    1 point
  37. 1 point
  38. Tja, das mit Google, Youtube und Konsorten. Ich vertraue da eher auf Manuale und Bedienungsanleitungen der Hersteller. Da gibt es Infos aus erster Hand - ganz ohne Werbung: https://wiki.unraid.net/Manual/Storage_Management#Array_operations Trust me: "New Config" brauchst Du nicht. Ich habe bestimmt schon 200-300 Platten zu Unraid Systemen hinzugefügt. New Config habe ich nur einmal benötigt - bei einem Versuch mit bestehenden Unraid Platten über VirtIO in einer VM. Die Platten hatten plötzlich alle neue IDs. Das löst Du über New Config oder das Entfernen von Platten. Ansonsten brauchst Du es nicht. Nachbemerkung: Du bezeichnest die genannten Informationsquellen als "Meinungen". Mehr ist es auch nicht. Das sehe ich genauso. Es handelt sich um Interpretationen von verfügbaren Fakten. Ich weiß, heute macht man das so. Ich halte das für gefährlich.
    1 point
  39. so, ich bin heute endlich dazugekommen, bei meinem neuen server weiterzumachen. ich habe ein 0815-netzteil eines alten pcs ausgebaut und voila, alles funktioniert wie erwartet; das rm550x geht also mal zurück und ich hoffe, das ersatzgerät funktioniert dann problemlos. danke nochmals an @DataCollectorund @trebeis für eure inputs!
    1 point
  40. Yep, that's a host managed SMR drive, while there's some kernel and fs support (at least from btrfs) for those in recent kernels not sure that Unraid supports them, also those drives should only be used with an OS that is aware of them, or performance will be terrible, IMHO you should return it if possible and get a CMR drive, or at least a device managed SMR drive.
    1 point
  41. Old Topic but maybe someone is interested in my Code: # Get the number of GPUs num_gpus=$(nvidia-smi --query-gpu=count --format=csv,noheader | awk 'NR==1 {sum+=$1} END {print sum}') echo "Found $num_gpus GPUs." # Iterate over the GPUs for ((i=0; i< $num_gpus; i++)); do # Check if there are any processes running on GPU $i if nvidia-smi -i $i --query-compute-apps=pid --format=csv,noheader | grep -q '^[0-9]'; then echo "There are processes running on GPU $i." else echo "There are no processes running on GPU $i. Setting GPU $i to power save mode." nvidia-smi -i $i -pm 1 fi done It first checks how many GPUS are installed and then if there are running processes. If not, Power save mode will be activated.
    1 point
  42. Hi, I wanted to give a little writeup about my journey to getting IGD passthrough working with: - latest LibreELEC 11 nightlies / Kodi 20 Nexus - latest unRAID 6.11.5 --> Both HDMI Video and Audio are working including HDR10 Maybe this will help others to fix their setup! My hardware as follows: - ASRock H570M-ITX - Intel Core i5-11400 (note: This is a Gen11 CPU with UHD 730 graphics which needs Linux 5.12 onwards in both LibreELEC AND unRAID to get Audio passthrough to work!) Be aware of this LibreELEC Wiki entry if you are trying to get passthrough to work. It seems there are quiet a few hardware dependencies (especially with HDR): LibreELEC 10.0 shipped with Linux 5.10 kernel support and Xorg graphics, so it does not have support for HDR or Gen11 hardware. Community created LibreELEC 10.0 images with newer Linux kernels supporting Gen11 hardware and GBM graphics with experimental HDR patches can be downloaded from the LibreELEC forums. LibreELEC 11.0 nightly development images from 21/9/21 onwards also use GBM graphics, include early (pre-Alpha) Kodi 20.0 support for HDR, and an updated kernel supporting Gen11 hardware. IOMMU: Mine look like these: To be able to passthrough the audio device you have to make sure that none of the devices in this group is used by unraid. I actually had one of my two ethernet controllers listed there aswell which was used by unraid. After I switched to the second eth controller in the network settings the group was free to use. I also disabled the first eth controller in the BIOS (that's why it's not listed in group 10 anymore). To passthrough the HDMI audio you need to add all devices in the group EXCEPT interconnects like PCI bridges to the vfio-pci driver via the syslinux.cfg. My entry looks like this (replace the values with the IDs of your controllers): vfio-pci.ids=8086:43c8,8086:43a3,8086:43a4 I also turned on PCIe ACS override - downstream and VFIO allow unsafe interrupts in the VM settings. and added the following in the syslinux.cfg: modprobe.blacklist=i915,snd_hda_intel,snd_hda_codec_hdmi video=efifb:off,vesafb:off To find the modprobe.blacklist value see this post So after all the steps my syslinux.cfg looks like this: kernel /bzimage append pcie_acs_override=downstream vfio_iommu_type1.allow_unsafe_interrupts=1 vfio-pci.ids=8086:43c8,8086:43a3,8086:43a4 modprobe.blacklist=i915,snd_hda_intel,snd_hda_codec_hdmi video=efifb:off,vesafb:off initrd=/bzroot VM creation: I created the VM using i440fx and SeaBIOS. Q35 and OVMF did not work! No ROM Bios and no further xml adjustments needed! See spaceinvaders video if you don't know how to create a LibreELEC VM: Additional BIOS settings for IGD usage: - Primary Graphics Adapter - onboard - iGPU Multi Monitor - enabled - OnBoard HD Audio - enabled - OnBoard HDMI HD Audio - enabled - C.A.M (Clever Access Memory) - disabled (not sure if this is needed but I read somewhere about it) --> The setting is only visible on AsRock Boards when turning on "Above 4G Decoding". C.A.M is also called S.A.M or resizable BAR by other manufacturers! This should be it! Good luck!
    1 point
  43. Klick mal auf '?' auf der Seite. Dort ist das beschrieben: Ein Beispiel aus meiner Umgebung: /usr/local/sbin/rc.unassigned mount //192.168.178.102/disk1
    1 point
  44. Thanks for your reply! I'll look in to the "first model", seems the most simple solution. /my2cents: It should be a nice feature in the My Servers Beta plugin. It's now showing offline or online if the unraid server is offline or online. Simple notification and voila.
    1 point
  45. Die bin ist kein Installationsmedium, sondern eine fertige VM von irgendjemanden. Du willst doch nicht wirklich so bekloppt sein und von einem unbekannten die VM starten?! Und wenn es eine ISO wäre, musst du sie natürlich als DVD einbinden. Also anders: Lad dir die ISO von Google, binde sie als DVD ein und weise X GB als Festplattenspeicher zu und los geht's.
    1 point
  46. 1 point
  47. I managed to kill 2 docker containers that just won't get stopped using this method: The `docker kill` command didn't work either :/
    1 point
  48. For anyone experiencing write-permission errors on Samba shares as I did, please make sure that: Syncthing Container (Docker) configuration has a configuration key set as follows: UMASK_SET => 000 (UMASK_SET as "Key" / 000 as "Value") Such a key can be added by clicking on "Add another Path, Port, Variable, Label or Device". to enable "Ignore Permissions" on each individual shared folder inside the Syncthing Web UI on your UNRAID machine. I have been investigating for hours why my files would keep ending up with the wrong permissions despite the supposedly correct UMASK of 000. Syncthing will, by default, try to synchronize the file permissions when exchanging data between two machines - beware of this functionality. Especially if you sync folders between another Linux machine and your UNRAID machine, Syncthing will initially create the file on your UNRAID machine respecting the UMASK 000 but later modify the permissions to reflect those on the original machine. By ensuring that your synced folders are all set to "ignore permissions", you basically tell Synthing to stay out of setting permissions altogether and respect the default local permissions. (which you have previously set by handing the UMASK 000 to the container) Hope this helps anyone experiencing permission troubles on Samba shares. 🙂
    1 point