Leaderboard

Popular Content

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

  1. See title of this thread.
    3 points
  2. Danke, hätte ich auch irgendwie selber drauf kommen könne 🙂
    2 points
  3. Hi. Backups, die mit DB-Backup erstellt wurden, lassen sich auch in der Konsole wiederherstellen. Die 2MB Limitierung in PHPMyAdmin ist normal und seit Jahren bekannt. Um das Backup als Restore zurückzuspielen, einfach im neuem MariaDB-Docker eine leere Datenbank, mit dem identischen Namen der gesicherten DB anlegen. Dann die Konsole des MariaDB-Dockers öffnen und folgenden Befehl (natürlich mit den eigenen Werten ersetzt) abschicken (Die Backupdatei muss im Verzeichnis liegen, von welchem der Befehl ausgeführt wird.): cat BACKUPFILE.sql | docker exec -i mariadb /usr/bin/mysql -u root --password=PASSWORT DATENBANKNAME Hierbei spielt dann die Dateigröße keine Rolle. -------------------- Ein weiteres Beispiel, um alle angelegten Datenbanken mit einem Rutsch zu sichern, wäre folgender Befehl, z.B. in einer Scriptdatei reingelegt und täglich aufgerufen: sudo docker exec mariadb /usr/bin/mysqldump -u root --password=12345698 --all-databases > /mnt/user/backups/db-all/`date +%Y-%m-%d-%H+%M+%S`-alldatabases.sql Das Restore dafür wäre dann: cat /BACKUPPFAD/2020-10-12-05+30+01-alldatabases.sql | docker exec -i mariadb /usr/bin/mysql -u root --password=PASSWORT Ich glaube sogar, dass man bei dieser Methode nicht erst leere Datenbanken mit den jeweiligen Namen anlegen muss. Bin mir allerdings grad nicht 100% sicher. Ist zu lange her. LG Da Do Ron
    2 points
  4. As soon as you build the images with the gnif patch you can't install any plugins with drivers included. Just a little note, when 6.10.0 drops you don't have to build a custom Kernel and you can install everything with plugins, even the gnif vendor reset.
    2 points
  5. Summary: Support Thread for ich777 Gameserver Dockers (CounterStrike: Source & ConterStrike: GO, TeamFortress 2, ArmA III,... - complete list in the second post) Application: SteamCMD DockerHub: https://hub.docker.com/r/ich777/steamcmd All dockers are easy to set up and are highly customizable, all dockers are tested with the standard configuration (port forwarding,...) if the are reachable and show up in the server list form the "outside". The default password for the gameservers if enabled is: Docker It there is a admin password the default password is: adminDocker Please read the discription of each docker and the variables that you install (some dockers need special variables to run). The Steam Username and Password is only needed in templates where the two fields are marked as requirde with the red * Created a Steam Group: https://steamcommunity.com/groups/dockersforunraid If you like my work, please consider making a donation
    1 point
  6. ok given path has been deleted, unraid is prompting again with update or install plugin, so i did a restart again to avoid that. and it seems to work now, i was missing the reboot after folder delete, i did not know this to be required thanks again enjoy your weekend
    1 point
  7. In Unraid 6.10 a change is made in docker container monitoring, which may help when a larger number of containers is used. You may want to test the new version when it becomes available.
    1 point
  8. So it’s safe to remove “collabora/code:6.4.9.3” and go back to “collabora/code”? Thanks a ton mate!
    1 point
  9. I am in 6.9.2 its a fresh installiert was never below 6.9.2 Alright i will try, catching up in 10 mins 🙂
    1 point
  10. Can't reboot the server currently, I think so. Have updated the BIOS two weeks ago and normaly I enabled it by default, but it could be also possible that I've missed it that time, will report back tomorrow.
    1 point
  11. disk1 and disk2 are both read-only so anything trying to write to those will fail. Should have no effect on rebuild since rebuilding isn't really "writing" files. Set all your cache-yes shares to cache-no so mover won't try to move them to the array.
    1 point
  12. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
    1 point
  13. Maybe. I found out that the user already reported it as a bug. As he used Ubuntu 21.04 it should be Kernel 5.11. Unraid uses 5.10.28. @ich777 Do you have an Unraid beta build with Kernel 5.11 so I could test and compare it with Ubuntu? Maybe I find the time to test the J5005 with the older Unraid version and upgrade Ubuntu 20.04 to Kernel 5.10 etc as well.
    1 point
  14. I would prefer to be on site, but if you have notifications enable to be able to cancel the rebuild if anything goes wrong it should be fine.
    1 point
  15. Yes, really sad that they did not release a W480N ITX and W580 is nothing I would buy for Unraid (no Legacy boot and no GVT-g support). 😢 Did you try Ubuntu?
    1 point
  16. Hello, Sorry to be a nuisance - could I have my username changed to 'ross232'? Thanks!
    1 point
  17. I believe you have (or had) a j5005? With my j5005 I have the same problem as the German user. ASPM is enabled in the BIOS and apparently supported: root@NAS:~# dmesg | grep -i aspm [ 0.454584] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] But disabled on all devices: root@NAS:~# lspci -vv | grep 'ASPM.*abled' LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ pcilib: sysfs_read_vpd: read failed: Input/output error LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
    1 point
  18. Thanks @JorgeB and @itimpi, appreciate both of your help in this thread. Looks like I've had one bad RAM stick out of the 4, so I've removed that and running the system on 3 RAM sticks, there were no errors in this setup on memtest. Hopefully the data corruption errors would not occur anymore. It would've been very helpful if I've come across the user script to monitor cache pool for any errors when I was getting started with Unraid. It isn't really advertised/well known until and unless you look for the specific error posts in the forum.
    1 point
  19. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
    1 point
  20. If you can see it in steam then it’s just a mater of finding it in ark, ich777 is probably right you need to set the correct options in the server selection window. You are looking for “unofficial” servers, then set the toggles for password, mods, ect…
    1 point
  21. You said that you were updating so I assume that was to 6.9.2 ? The reason for the approach I suggested is that I have seen that in the past occasionally that when updating via the GUI the new files for the new release seem to not have been written successfully to the flash resulting in the symptoms you got and rewriting them outside the update process gives you a good copy.
    1 point
  22. iSCSI plugin in Community Applications for Unraid version 6.9+
    1 point
  23. Let's tag @SpencerJ
    1 point
  24. The quoted syslog mentions that the problem is the fiber module you're using in that port, it's not supported by the NIC.
    1 point
  25. Done and Thanks. In addition, how to know the hardware acceleration working or not?
    1 point
  26. I switched from a Xeon 1230v3 to a Ryzen 9 3900x, replacing the same parts as you. Just update the BIOS settings regarding boot order, and virtualization/IOMMU if needed, and you should be good to go. It was a pretty simple process (at least for me). In any case I'd still suggest to make a backup of your flashdrive as well as your drive order, should anything go wrong unexpectedly.
    1 point
  27. Oh that is awesome news Thanks for the reply too, much appreciated!
    1 point
  28. @ich777 Thanks again for this. I used the tool to create a custom kernel with the GNIF patch and also coral and DVB drivers. I did want to ask - are plugins compatible with this? Initially I just had the GNIF patch on and then installed the DVB and Coral driver plugins from the app section. But as soon as the coral driver was modprobe'd I got a kernel panic. So I rebuilt with GNIF and coral drivers built in. But then I would get a kernel panic when my DVB hardware was initialised from the plugin as well. So ultimately I built the kernel with all three and that works fine.
    1 point
  29. 1 point
  30. I'll ping @itimpi and @JorgeB to see if they have anything to add.
    1 point
  31. I was able to solve it with the help of a user on Reddit. Even though the configuration looked correct, the Unifi controller container was running a bad create command and using my proxynet instead of Bridge mode. So, I migrated my Unifi controller to another instance of it on Br0 with a different static IP address, and that worked like a charm.
    1 point
  32. Hello Thank you very much to all and especially to Ghos82. Now it works again. Remember that you are invited to a few beers, when you come here. Spain.😃
    1 point
  33. Wenn die IP des unRaid Host auf der Bridge liegt und Du in der VM einen virtio Treiber nutzt, der auch auf der gleichen Bridge liegt und im gleichen IP-Netz liegt, dann sollte die mögliche Bandbreite maximal sein...in der Regel die der CPU. Natürlich schluckt das ganze CPU-Leistung,,,ein bischen Bumms sollte die CPU also haben....und das System genug / reichlich RAM für beide "Hosts". Die Netzwerk-Bandbreite kannst Du mit iperf testen. SMB ist single threaded und kostet weitere CPU-Ressourcen. ...das Share sollte auf dem Cache oder einem SSD-Pool, gebaut aus Pcie-NVMe liegen....sonst limitiert die Technologie der Disk, die unter dem share liegt. ...probieren geht über studieren ;-)...hast Du den unraid Host schon? -> mach einen Test, erstmal mit iperf.
    1 point
  34. You can't have multiple disks in the pool unless using btrfs. 6.9+ allows multiple pools though. I have a "fast" pool as xfs for dockers and a "cache" pool as 2x btrfs raid1 for redundancy.
    1 point
  35. All plugins etc on Unraid run as root and there are no users in the linux sense.
    1 point
  36. Nextcloud hat scheinbar ein Problem mit der neuesten MariaDB Version: https://forums.unraid.net/topic/110019-support-mariadb-official/?tab=comments#comment-1016693 Entweder den Workaround anwenden oder MariaDB neu installieren (mit Appdata Clean Ordner löschen) und MariaDB mit einem tag auf eine ältere Version festlegen. Dh beim Repository Namen zb mariadb:10.5 eingeben um bei Version 10.5 zu bleiben bis Nextcloud angepasst wurde.
    1 point
  37. Muss nicht. Geht auch nur lokal. Oder "lokal" über einen VPN Tunnel. Dh wer sich von unterwegs über die Nextcloud App verbinden möchte, müsste erst einen VPN Tunnel aufbauen. Das gilt auch als sicher. Ich nutze für solche Szenarios ZeroTier, da man da keine Portfreigaben im Router benötigt. Und wie gesagt ist die letzte Option, dass man die Nextcloud direkt online über eine Domain verfügbar macht. Also jede Option steht dir zur Verfügung.
    1 point
  38. Would be best to post in the relevant support thread for the thunderbird app (click it's icon, select Support)
    1 point
  39. Yes, the purpose of the Remote Access feature is to give you remote access to the webgui. Check out the docs for more details: https://wiki.unraid.net/My_Servers Do not put Unraid directly on the Internet or in your router's DMZ. But yes you can forward a port to the https webgui now. You should use a high port number (not 443) and you need to have a good rood password. Recent versions of Unraid will lock out intruders after three bad login attempts. For more security best practices see https://unraid.net/blog/unraid-server-security-best-practices My Servers provides the DDNS and certificate to make secure remote access possible and simple. This optional feature is for folks who need remote access to their webgui using just a browser. WireGuard VPN is arguably more secure and gives you access to Dockers and other devices on your LAN as well. Use the remote access solution that works best for you.
    1 point
  40. Yep, exactly you have to download the new version for this Kernel version (so to speak the link has changed): cd /tmp wget https://github.com/ich777/unraid-plugins-repo/releases/download/5.10.19-Unraid/nct6687d-1.txz installpkg nct6687d-1.txz depmod -a modprobe nct6687
    1 point
  41. For anybody else looking up similar questions some 3+ years later ... The very helpful "archived notification menu" can be found from: webui > tools > archived notifications You can then click on a notification, and it will give you further details, as per extrobe's "NOK" paste.. (Thanks for the pointers, resolved my issue, also ended up being a hot disk )
    1 point
  42. There is an option for this yes. If you look under the monitor settings, you will find a 'presets' section. In this you can schedule the presets via a schedule. Simply make a preset, add the camera's to them and apply an schedule.
    1 point
  43. i solved the problem, the bugging reolink cam had not the same firmware than the 3 others . it has an older one. the procedure is : 1- to go in a browser to the reolink interface : https://d.pr/i/2muUCs 2- login 3- i downloaded here the new firmware : https://github.com/hn/reolink-camera 4 - https://d.pr/i/ppAfsh hope this will help someone i searched 2 hours
    1 point
  44. I got this figured out and am able to use the MariaDB inside the container to make this work. No need to run a dedicated MariaDB docker instance. First, make sure the shinobipro docker container is running. Log into the console of the container, either by using the unraid feature or by this command: docker exec -ti shinobipro sh Next, create the database and tables... mysql source sql/framework.sql; source sql/user.sql; exit Now restart the container and it will work.
    1 point
  45. @1812 I simply don't have this view, since it only detects the single rj45 port of the motherboard, and nothing else.
    1 point
  46. Well When I have a intensive task like 150mb/s write, or a parity check, my dockers are not responding. I found that by isolating core I do not have this issue (i7-7700). I was thinking that is I did not pin dockers to core, they would use full CPU... THanks for your help !
    1 point
  47. looking at the above screenshot somehow the driver is not loading correctly, what firmware are you running on the H330 and have you tried another PCIe slot? my H330 is at FW 25.5.5.0005 but I've been running this card for about a year now without any issues on unraid (6.4 till 6.6) and have you tried booting another OS, to rule-out an compatibility issue with your other HW or even a broken card?
    1 point
  48. Did you set up elasticsearch? It is are mandatory to get this working. You should also set up redis. You also need to read the Readme on github for specific setup needed on unraid to get it working. You have to use the 5.6.x branch of elasticsearch You will not get a webgui until elasticsearch is working.
    1 point