Leaderboard

Popular Content

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

  1. @Ford Prefect Danke. Die Befehle aus dem Link sind mir bekannt. Die Reihenfolge halte ich auch ein. scrub kann ich aber leider vergessen, weil ich nicht schreibend mounten kann. Was ich noch herausgefunden habe und was wohl durch den Wechsel auf Single passiert sein muss, dass "data" auf Single steht und nicht auf RAID1: btrfs fi us /mnt/nvme0n1p1 Overall: Device size: 1.82TiB Device allocated: 136.06GiB Device unallocated: 1.69TiB Device missing: 931.51GiB Used: 112.67GiB Free (estimat
    4 points
  2. Disk Location is a different disk tray layout plugin which uses the harddisk path to locate the drives. It supports only drives found by the SCSI Generic drivers, which is usually SATA and nVME including devices attached to hardware storage/raid cards. This also include a handy "Locate" function which help you allocate the tray from where the disk is installed in, if you have hotswap trays with their own HD-activity LED (or made your own custom ones). This might not work on SSD's or maybe even some other types of harddrives. You can change the direction of the trays hor
    1 point
  3. Welcome to the new method of working around HP's RMRR problem on unRaid. For the previous/deprecated method which was no longer working, see: https://forums.unraid.net/topic/72681-unraid-hp-proliant-edition-rmrr-error-patching/ First the disclaimer: This has been tested with no negative attributes observed. Many have been running an RMRR patched version since mid 2018 when we first started producing them, and so far have had no reported issues. As it only omits RMRR checks, it should not affect any other core function of the OS. But a
    1 point
  4. Das kommt durch einen Parity-Check, der Änderungen festgestellt hat. Dh die Parität war nicht in Ordnung bei diesen Sektoren. Das kann bei einem Crash durchaus passieren, darf aber nicht im laufenden Betrieb auftreten. Denk dran, dass wenn du das Plugin aktualisierst, deine Änderung nicht mehr vorhanden ist. Die müsste man dann erneut einbauen.
    1 point
  5. A new version of my qbittorrent-vpn Docker has been pushed (should be available within 1 hour after posting this message). Most of these changes won't be noticeable, since qBittorrent still is qBittorrent 😉 However some background work has been done. The issue that @tmor2 had, should be fixed with this new version. Together with resolving that issue, the other new big change is the decision to switch to Libtorrent 2.0 instead of Libtorrent 1.2.xx. Hereby the changelog: * Switch to the Libtorrent RC_2_0 tag instead of RC_1_2. * Self-compilation of Boost to stay up to date wit
    1 point
  6. @KrisMin Thank you for pointing this out. I tested it and it seems that indeed something has changed in unraid docker implementation since I last created a node. This argument is now necessary on the first run. I added this info to the template and the topic.
    1 point
  7. Sorry, I removed the API and cookie because I couldn't get them to make a difference. What does make a difference is changing the IP the container is going through every couple days whenever I get 429'd, typically every 36 to 48 hours. I'm already using a VPN container, so I just changed this container to network none and added --net=container:<name of vpn container> to the extra parameters line. Whenever I restart the vpn container it gets a new external IP. It's a little inconvenient, but it works. I suppose if I get too irritated I'll script something that watc
    1 point
  8. dont bother with the wizard, your adapters are there so it looks all good when the tuners work.
    1 point
  9. Ganz ganz lieben Dank an dieser Stelle, echt super! So ein dummer Fehler passiert mir nicht nochmal. Und bitte nicht nachmachen! 😂
    1 point
  10. Fehler scheint behoben zu sein. Der Wechsel der Knopf Batterie auf dem MB hat die alle MB Einstellungen resetet und jetzt gehts und der Bootvorgang ist auch viel schneller. Ob es nun an der Batterie lag (die Zeit lief im Bios aber weiter, wenn ich das Netzkabel entfernt hatte. also leer war die Batterie nicht) oder einfach nur eine Einstellung nicht ganz koscher war, obwohl ich alle Einstellungen so häufig kontrolliert habe und auch das Handbuch gewälzt habe, weiß ich nicht. Tatsache ist, dass ich wohl mir "default" Einstellungen im Bios und der neuen Knopf Batterie endlich eine Sorge weniger
    1 point
  11. Danke für die Info. Dann werde ich die Daten einfach mal löschen. Ich hab alles noch auf einem separaten Backup. Wäre also kein Problem wenn die Dateien in Unraid weg wären. 👍
    1 point
  12. You don't have to do this anymore, you can also do this by installing the Plugin Intel-GPU-TOP from the CA App so no edits to the go file are required and you also have the benefit of having the tool 'intel_gpu_top' installed natively to Unraid to watch the usage of your iGPU or you additionally install the GPU Statistics Plugin from @b3rs3rk to see the usage of the iGPU on the Dashboard page. Please make sure that you set the iGPU to the Primary Graphics adapter in the BIOS.
    1 point
  13. Doch, der Grund steht da. "File exists". Die Datei existiert also auf der SSD und HDD. Die Frage ist warum. Ich tippe darauf, dass du diese Dateien 2x auf Unraid kopiert hast. 1x als der Share Homeserver die Cache-Einstellung "No" hatte und einmal als sie auf "Yes" stand. Oder du hast sie mit rsync synchronisiert?! Jedenfalls ist nun Vorsicht geboten. Die einzige Lösung ist nämlich löschen. Je nachdem ob die von der SSD oder HDD bleiben sollen muss man sie vorher auf die HDD kopieren oder einfach nur von der SSD löschen. Mehr dazu in diesem Post: https://forums.un
    1 point
  14. Sorry for my confusion. To install p7zip: Install the NerdPack plugin. Go to SETTINGS and click on Nerd Pack. Turn on p7zip-16.02-x86_64-1sl.txz. Then click on APPLY at the bottom. You may have to reboot for it to take effect if the apply doesn't work.
    1 point
  15. Yes that is possible, you can enter the ID of the GPU: '0,1,2,3,4' or you can simply type in 'all'
    1 point
  16. I don't believe it's as random as I'm thinking. It seems to reset every time this error pops up in the logs: usbhid-ups[3459]: nut_libusb_get_report: Input/Output Error. I cannot find much on google about this. What I've done for now is setup a raspberry pie to be the netserver and I've had no issues so far. Thanks for the tutorial. It helped me get to where I needed to go!
    1 point
  17. Ach das steckt einfach in mir drin. Wenn man Backup sagt, dann sollte man es auch richtig machen. Die Abwägung, ob ein Datum wichtiger als ein anderes ist, blockiert nur und im Zweifel ärgert man sich dann doch. Und der Aufwand ist lächerlich gering. Wie gesagt: Keine 10 Zeilen, und saubere Backups lassen ruhig schlafen.
    1 point
  18. So you certainly have a lot of information already.. I can't really tell you anything useful but I can comment on my experiences thus far. I don't know about the headers and such and if or why you'd need/want to back them up. My experience is that the encryption can be a pain in the ass... Unraid's encryption system -- in my opinion - was implemented like it was an afterthought and not designed or implemented correctly to make using it easy. I have not used the passphrase option, only the key file, and perhaps that's the real issue. Any attempt at creating
    1 point
  19. @ich777 and @alturismo I got it! FYI: The new extension did unfortunately not bring the solution, but extension of the USB cable did. So no I have the cable from the satellite directly plugged in the usb adapter and the usb cable from the adapter is extended to the server. Now, all channels work as expected.
    1 point
  20. Dafür müsste man aktuell selbst Hand anlegen und die rsync Kommandos anpassen. Filtern steht aber auf der Todo ^^
    1 point
  21. If the container does not establish a connection to the VPN then the UI will not load. Sent from my CLT-L09 using Tapatalk
    1 point
  22. If the docker can’t connect it won’t start.
    1 point
  23. I had a same issue. Apparently when running the first time -e SETUP=true --mount type=bind,source="/mnt/user/storj/<identityfolder>/",destination=/app/identity --mount type=bind,source="/mnt/user/storj/<datafolder>/",destination=/app/config is needed.
    1 point
  24. https://wiki.unraid.net/Shrink_array
    1 point
  25. This thread made me try out unRAID on a newly purchased QNAP TS-453D. I hooked up a monitor and keyboard, held down F2 during startup to enter BIOS, changed boot order to make 'UEFI: my usb drive" first and it worked beautifully. As far as I can tell unRAID recognizes all hardware correctly, except for the fan, but that is set to "auto" in BIOS (and it's spinning), so I think it doesn't matter. I'm very pleasantly surprised!
    1 point
  26. New Zealand. So, I've pushed x3 new features today... Quicksync HW Encoding (VAAPI) support. Quicksync was not fully enabled after the NVIDIA encoding feature was added a few months back. It was missing some testing and additional configurations. I finally managed to get my hands on an Intel laptop a couple of months back, so I was able to finally finish that part off. There are no configuration options at the moment for HW decoding, but I think I would like to get around to that some time also. However, there is now a way you can configure Intel decoding and enc
    1 point
  27. I have a 7700K, 64GB, 2xNVME in Raid-0 cache drive, GTX1070 passed through to Win10... I run the VM's off the Unraid Cache... Make sure the VM is set to Q35-3.1.0 in the Unraid 6.7.0-rc2 or Q35-3.0.0 if you want the Unraid 6.6.6... I had several issues when using the Unraid default of i440fx, some are performance related, some compatibility issues... This is because the i440fx was an ancient chipset for the old Pentium 1+2 that knew about old PCI and AGP slots... and so has to translate everything PCIe into PCI, and other translation overhead... The Q35 chipset actually knows
    1 point
  28. If as you try to access unsecure unRAID, you see this panel, insert \ backslash for user ID and click OK, your in.
    1 point