Leaderboard

Popular Content

Showing content with the highest reputation on 03/31/21 in Posts

  1. 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
    3 points
  2. @Boyturtle an update just rolled out. Give that shot. Resolved it for me so far.
    2 points
  3. currently working on it with a glass of rum&coke
    2 points
  4. Hi All, It has a 2.5G network onboard, updated the unraid version on the USB and it looks to have found the network again. All looks good besides my VM which requires a BIOS setting somewhere. Thank you for the help, things are rocking again this side. Regards, Brandan
    2 points
  5. Yes, I know, the server already built it about 1 and a half hours ago. EDIT: Please give my scripts a little bit, I update the versions every two hours and the build only for the Nvidia Driver takes about 30 minutes so the longest time you have to wait after a new driver is released is 2 and a half hours. EDIT2: But the good news is that the automated build is working.
    2 points
  6. This container will no longer be maintained or supported as of 23.07.2021. Fork it, modify it, do whatever with it if you need it. Docker container for Ethereum mining with CUDA (nsfminer) with Nvidia OC capabilities. This Docker container was inspired by the docker-nsfminer which was inspired by docker-ethminer. It uses the nsfminer with OC capabilities with the Nvidia driver. This docker will allow for over- and underclocking of Nvidia GPU's for Ethereum mining in a docker. One docker template per GPU. GitHub project: https://github.com/olehj/docker-nsfmin
    1 point
  7. Hi, I'm having problem with the 6.9 version of Unraid. The server freezes at random times, and can only be fixed by doing a hard reset on the server itself. It does not respond to ping when it has freezed. It happened a few days after I upgraded, then it ran for around 2 weeks before freezing again. Yesterday it froze again, restarted it and now it freezed again around 15 minutes ago. I did not have these problem with 6.8 and has not changed anything in the setup. I tried to check the log files but it seems like it was reset when server was rebooted again. Is there any way see
    1 point
  8. OK..... problem solved i believe. So i got a message from my ISP last week that they were doing maintenance to the entire township and i was included in that. What i didnt know is that my IP address changed 😆. Steam seems to be able to see it both ways now. I will have a friend try to connect and see what happens
    1 point
  9. Need to run to get the image name that the container is using and find out where the image is coming from and what it is.
    1 point
  10. The mce's are somewhat common when the system initializes the cores and affects certain hardware combinations for some reason, and can be safely ignored.
    1 point
  11. Thanks again, Jorge! Have had a few other things to deal with, and being away for a little while, but working on it slowly here and there. Looks like I've at least got the server array back up and running along with my docker services, etc. The NVMe shows up in the unassigned devices as I removed it from the cache pool for the moment while doing some clean up and reworking. So I think I'm back in a good spot to continue with everything. Thanks again! Considering this solved for now!
    1 point
  12. Yes. That is planned for a future update.
    1 point
  13. That confirms it's a network problem, you should get close to line speed (1Gbits/s), it's at 20/25% expected bandwidth.
    1 point
  14. Das muss nichts heissen. Aktuelle Dateisysteme besitzen wie Datenbanken einen Transaktions-Puffer (transaction log). Alle Änderungen wandern da durch und der Transaktions-Manager arbeitet diese ab. Sobald abgeschlossen werden die Änderungen als "abgeschlossen" markiert (commit). Bei einem ordentlichen Shutdown werden alle hängenden Änderungen, inkl. das Log selbst, noch synchronisiert. Bei einem harten Shutdown geht das naturgemäß nicht. Das geschieht dann nach dem mounten oder bei einem repair. Wie bei Datenbanken können mehrere Änderungen (Metadaten, Daten, ...) in einer Transakt
    1 point
  15. v0.3 ist fertig. Jetzt kann man IP-Bereiche freischalten, die Dateien enden auf .ip und der Firewall-Code steht nun ganz oben in der .htaccess.
    1 point
  16. Genau, @ich777 - mit dem Befehl ließ sich dann die Original FW flashen und die PSID hat sich von "IBM1080110023" in "MT_1080120023" geändert. Die kommenden Updates sind somit auch auf dem ganz normalen Weg flashbar Dank dir - mach ich bzw. deaktivier ich
    1 point
  17. Aber wenn du mit dem parameter "-allow_psid_change" hat es funktioniert oder? Überleg dir auch ob du das BIOS der Karte entfernst wenn du den Netzwerkboot nicht brauchst usw, sieht dann so aus: Sollte bei dir mit diesem Befehl funktionieren: mstflint -d 01:00.0 --allow_rom_change drom
    1 point
  18. Meine Karte war / ist IBM gebrandet Die original FW von Mellanox ließ sich nicht aufspielen. Hab das Ganze jetzt mit einem Crossflash gelöst, so dass ich die aktuellste Mellanox-FW aufspielen konnte und nicht auf die ältere IBM-FW greifen musste: root@Filer:/tmp/mellanox# mstflint -d 01:00.0 query full > flint_query.txt root@Filer:/tmp/mellanox# mstflint -d 01:00.0 hw query > flint_hwinfo.txt root@Filer:/tmp/mellanox# mstflint -d 01:00.0 ri orig_firmware.bin root@Filer:/tmp/mellanox# mstflint -d 01:00.0 dc orig_firmware.ini root@Filer:/tmp/mellanox# mstflint
    1 point
  19. Hab mal kurz was zusammengeschrieben: Lad dir die entsprechende Firmware für deine Karte runter für eine ConnectX2 zB von: https://www.mellanox.com/support/firmware/connectx2en Entpacke sie zB nach "/tmp/mellanox" am Server Gehe in den Ordner in den du Firmware entpackt hast Gib "/sbin/lspci -d 15b3:" ein und du solltest sowas in die richtung als Ausgabe erhalten: 07:00.0 Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0) Gib "mstflint -d 07:00.0 -i firmware.bin burn" (ersetze hier "07:00.0" mit d
    1 point
  20. Welche Karte hast du genau bzw was willst du flashen. Ich hab meine ConnectX2 und 3 damit geflasht und das BIOS entfernt. Vergiss bitte nicht das Plugin basiert auf den Open Source Treibern und die Kommandos sind bei denen ein wenig anders das sind alle verfügbaren: mstconfig mstfwtrace mstmwrite mstresourceparse mstcongestion mstmcra mstprivhost mstvpd mstflint mstmread mstregdump mstfwreset mstmtserver mstresourcedump EDIT: Was meinst du mit nötigen Kernel-Modifikati
    1 point
  21. Also brauchst du einen Slot für eine GPU? Weil dein Board hat ja 2x x8 und 3x x1 (der x4 ist bereits aus, wenn du eine zweite M.2 installierst): Vom Prinzip sollte das aber gehen. Du wirfst die Delock-Karte weg und steckst die zwei ASM1166 Karten einfach in die x1 Slots und verbindest aber jeweils nur 4 HDDs. Ein x1 Slot hat 1 GB/s Bandbreite, also ausreichend für 4x 250 MB/s. Plus die 6 SATA Ports auf dem Board macht das 14 HDDs. Reicht das? Ansonsten noch eine dritte Karte in den dritten x1 Slot oder eben in einen x8 Slot. Der Chipsatz ist übrigens ü
    1 point
  22. okay have fix that, think there is something corrupt inside the docker.img? Is that loop3? as you stated. I will try re-create it.. hope my plex files are gucci I get a tone of errors of this nature when starting plex Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 654, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 in
    1 point
  23. This won't help, if there are uncorrectable errors the corrupt file(s) will be listed in the syslog, you'll need to delete them or restore from backups.
    1 point
  24. This is usually the result of a device dropping offline, see below for more info: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582 That's what likely caused the issues with loop3, which is the docker image and should now be recreated.
    1 point
  25. Wenn du keinen ECC RAM benötigst, gibt es ja viel Auswahl. Zb das ASRock B365 Pro4 kombiniert mit einem Pentium Gold G5400? Kommt auch drauf an wie viel Leistung du benötigst. Oder ein neueres Board wo direkt auch 2.5G LAN dabei ist und 8 SATA Ports wie das Gigabyte W480M Vision, kombiniert mit einem G6400. Das Board ist allerdings deutlich teurer.
    1 point
  26. I had the same issue. Try replacing repository with olehj/docker-nsfmineroc:latest
    1 point
  27. Pre-requisites - You have Nginx Proxy Manager already installed and working - You have installed goaccess from Community Applications but it's not working out-of-the-box There are three main steps 1- Have your log generator container (Nginx Proxy Manager) output its logs into a folder that goaccess can, well, access 2- Configure goaccess to look for the right log file 3- Configure goaccess to understand how to parse the log/date/time format Step One: Map Log File Folder I use Nginx Proxy Manager and by default, it puts
    1 point
  28. I'll keep you updated. It has been stable since the downgrade yesterday at least.
    1 point
  29. Back about ten years ago, I decided I had a storage space problem. So I looked around to see what was available. I don't remember what was around at the time but I came across the unRAID product. So you load something on an USB and then boot to it and it then sees all the attached drives. Create shares, add data and you're good. It has data recovery as well in case of drive failure. Sounded pretty much agnostic as far as motherboard hardware was concerned. Interesting concept. And an online community with all kinds of info. Like any IT guy with 20+ years of hardware ex
    1 point
  30. The error 43 is the exact driver shenanigans they pull with video cards, but with virtual functions its unfortunately even more difficult to get around. A couple things you can try: * instead of running the full installer, open the executable (.exe installer) with 7zip or the like, and manually install the drivers for your OS (using the .inf files) * test against a different version of windows 10 to verify whether its locked to a specific build type (education, pro, pro for workstation, or an enterprise LTS build) * read through the release notes for earlier driver v
    1 point
  31. Not necessarily. There are still many good uses for unassigned devices: Plug in an external USB drive and backup share data to it automatically via a UD script Use a USB device as a location for the syslog A UD for VMs is still preferred by some A UD as a download, personal cloud data, transcode or media conversion location may still be preferable in some cases over a cache pool Unassigned Devices supports formats such as NTFS which allow these devices to read in Windows outside the array.
    1 point
  32. It's a long-shot but you may want to try WinOF v5.50.54000 (the one that's allegedly for Server2019 only) Worked fine with Win10 LTSC (1809) and ConnectX-2
    1 point
  33. Post it here, if you feel like editing it you can delete it later. Trust me, you are not the dumbest person on this forum.
    1 point
  34. I was having issues getting ProFTP running again after upgrading Unraid to version 6.9.1 using ProFTP 1.3.7a. ProFTP just would not start and I could not get anything in the log. I tried enabling debug logging, but still nothing. I removed the plugin and did a clean install multiple times and still nothing. Then I stumbled upon running this command in terminal sudo -u root /usr/local/SlrG-Common/usr/local/sbin/proftpd -c /etc/proftpd.conf which resulted in this error: 2021-03-30 20:12:19,459 TOWER proftpd[24730]: fatal: unknown configuration directive 'IdentLookups' on line 24 of '
    1 point
  35. I am making my final update to this thread because I finally solved this problem. The solution was to return my Asmedia SATA Controller card back to Amazon and get the one shown in the link below: https://www.youtube.com/watch?v=UlVk1Bwkh-Q&t=3s Boxed in YELLOW below are my optical drives shown in the System Devices page in the UnRaid OS. I was not getting the results shown below with the Asmedia card. But this new MZHOU PCIe SATA Card recognizes my cd/dvd optical drives. And I am sure once I setup my Linux Mint VM these optical drives will appear on my Linux Mi
    1 point
  36. Hopefully this opens up the possibility of SR-IOV at a later date
    1 point
  37. Common issue is not selecting the codec that is GPU accelerated.
    1 point
  38. My best for a Linux machine was 4years. We moved and I thought it was safer for me to shut it all down than to carry the UPS and pray the drive didn't get bumped in the back of my car for the 15minute drive. lol
    1 point
  39. Apologies all for the lack of updates on this project. I'll be picking it back up and working on it again very soon. I shall update you all here once I have some news.
    1 point
  40. Maximum size limits on shares. That way i can partition X TB on a single large disk and set the samba settings so only certain users can access Y TB of it. This is nice so i can use something like a single 12TB disk and give 3TB to everyone in the household to use exclusively so no one goes over their quota. Also big +1 to user groups with folder/share permissions
    1 point
  41. The first one failed to mount but the second one did and I was able to recover about 50GB of appdata and the docker.img. Thanks for all of your help!
    1 point
  42. ...das ist "normal"...ein "Feature" des Docker Daemon, glaube ich...hatte da auch vor vielen Jahren Probleme das zu verstehen. Ich habe seitdem meine Docker alle in einem anderen VLAN und dann keine Probleme. Das braucht aber einen VLAN-fähigen Switch und Router. Edit: Ich muss mich korrigieren, das VLAN allein hilft da nicht...brauchte noch ein externes Interface oder eines mit NAT dazwischen 😅 (habe das Feature aber bisher schon ewig nicht gebraucht). ...ist leider aktuell so...liegt wohl am Template/Dockerfile des Docker-Maintainers ...funktioniert aber
    1 point
  43. Are you getting errors, or is it converting files? Just because you have hardware acceleration enabled, does not mean the CPU will not be used. The CPU is still used for decoding, audio encoding and remixing. If the task is only those, then it will use 100% CPU. Sent from my Mi MIX 2 using Tapatalk
    1 point
  44. Hey team, I'm getting ready to push another lot of changes to the staging branch. I have been busy developing a new plugin system for Unmanic over the past 2 weeks. I chose not to merge the current staging changes into the master branch as there was identified some additional issues with conversion tasks and cache files not being delete. I am hoping that the changes that I push to the staging branch tonight fix those. But as always, if you update tomorrow and are still having issues, let me know and I will dive deeper. I have begun writing some documentation
    1 point
  45. I do prefer the mixture of the both. I code up a bunch and drop all that into User.Scripts so I can click a button and it does its things. There's a lot to be said about a nice interface and knowing how things work in the background. I've always been intrigued with how things work in the background and it cracks me up watching people search for that "button". However, you are totally right you can win or loose a user if the interface is to complicated or simply not there. unraid has come a long way for me since 2009 when I started using it the interface was very limit
    1 point
  46. 1 point
  47. Most people think "bitrot" refers to flaws in the physical storage media developing over time, such that data written to a storage block at time 0 is not the same data that is read at time 1, and this fact goes undetected. Indeed storage media does degrade over time, however, storage media devices also incorporate powerful error detection and correction circuitry. This makes it mathematically impossible for errors due to degrading media to NOT be detected and then not reported as "unrecoverable media error", unless there is a firmware error or other physical defect in the device.
    1 point
  48. Just one quibble, the parity drive does not have a format, so don't bother trying. It's going to be *completely* overwritten.
    1 point
  49. You could use unraid as your cell phone! But really, it's more of a "cause I can" thing. My end goal is to get Android TV working in a VM with GPU passthrough so I don't need to buy a physical Android TV. As much as I like Kodi, the lack of official apps for it like Netflix and HBO GO/Now, really kill the WAF. Having an Android TV with native apps for those services, plus Emby as my personal media hub and live tv would finally provide me an all-in-one front end for media conception in front of the TV. So I used Android Lollipop as a jumping off point since that seemed the easies
    1 point