Leaderboard

Popular Content

Showing content with the highest reputation on 03/26/17 in all areas

  1. Hi, guys. I was frustrated as to why we couldn't use the techpowerup vbios files in our VMs. So I have discovered it is due to a header put there for later Nvidia cards which isn't compatible with KVM. (the header is for the NVflash programme) So in this video, you will see how to pass through a Nvidia GPU as primary in a KVM virtual machine on unRAID by removing the header from a vbios dumped by GPU-z/ Techpowerup making it compatible with a KVM virtual machine. This is very useful as techpowerup.com has an extensive database of GPU vbioses. Also, should you want to dump your own previously you had to have 2 GPUs and 2 PCIe slots to do this. Well now you can do it using GPU-Z easily then convert it for KVM. How to easily passthough a Nvidia GPU as primary without dumping your own vbios!
    2 points
  2. Application Name: Ubooquity Application Site: https://vaemendis.net/ubooquity/ Docker Hub: https://hub.docker.com/r/linuxserver/ubooquity/ Github: https://github.com/linuxserver/docker-ubooquity/ Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.
    1 point
  3. At the present time, there is not way to logout of the GUI unless one shutdowns the browser. This could be a potential security risk (for those users whose computers can be accessible by untrustworthy persons) that could be easily addressed by placing a 'Logout' button in the toolbar.
    1 point
  4. I have recently created several VLAN interfaces in the GUI in order to deploy a new virtual firewall. I have been fighting with it for hours and have not been able to get anything to talk to or from the firewall. I decided to simplify my troubleshooting and install a simple CentOS host to test with. Any VM using br0, works just fine. If I assign any of the VLAN interfaces to a VM, in my case, br0.10, br0.20, br0.30 or br0.5, no traffic will pass anywhere. Attached are screenshots of the config from the GUI, network-1.png and network-2.png. The LACP bond has been in play for a long time and works fine. I can see from the CLI that br0.10 has MAC Addresses for the unRAID interface and the VM interface that is assigned in the VLAN: root@serv:~# brctl showmacs br0.10 port no mac addr is local? ageing timer 1 d0:50:99:6c:7d:b6 yes 0.00 1 d0:50:99:6c:7d:b6 yes 0.00 2 fe:54:00:71:39:f0 yes 0.00 2 fe:54:00:71:39:f0 yes 0.00 Also attached is the output of ifconfig -a showing all of the deployed interfaces and the status of each, ifconfig -a.txt. My switch is configured properly to run both tagged VLANs and one specific VLAN untagged up into the unRAID host. Trouble is, no MAC Addresses or ARPs get learned on the switch from any of the vnet interfaces assigned on a br0.x VLAN interface on the unRAID host. You can also see from the output above, that the switch MAC doesn't get learned on the unRAID host either. There is a complete L2 breakdown happening here somewhere, and it seems to be on the unRAID host. You will find the MAC address learned on the switch in the attached file show mac.txt. You will not find the 39:f0 MAC listed, however, you will find the 7d:b6 MAC which is used on all of the bond and br0 interfaces. From the test CentOS machine I have setup, I have tested with both untagged and tagged settings on the interface, neither allow it to communicate, not even with the unRAID host address. That bit is what tells me that the switch doesn't even matter at this point, since I can't even talk from the VM to the host tagged or untagged. If I alter the VM config to use br0 instead of br0.10, no issue at all, I can ping the host and everything else out in my network as expected. I have read a fair bit about various setups in other distributions, but nothing has pointed me in the right direction so far. Looking for any advice anyone might have to trouble shoot this. Haven't altered anything on the CLI, config is as it was set from the GUI. Any tips? Thanks all! -Landon ifconfig -a.txt show mac.txt
    1 point
  5. Wow, so that is big news, Lime-Tech is having issues too. While I had memtest issues with my original memory, those problems didn't manifest in Windows, even with heavy stability testing. I've since replaced my memory with ASRock QVL'd memory, and have completed 16 passes (and counting, it's been running for several days now) of Memtest86 without a single issue. Yet I still get frequent crashes in unRAID. Only in unRAID. I just reread through this entire topic and gathered the following info. If anyone has any updates, please share: TType85 has an ASUS B350 Prime, and has not reported any issues [presumed to be running Windows VM] hblockx has a Gigabyte X370 Gaming 5 and says it is running great [presumed to be running Windows VM's on his 2 gamers 1 pc] jonp (Lime-Tech) has an ASRock X370 Killer SLI/ac, and appears to be having issues but has not shared any info with us [unclear if they are running any Windows VM's] Beancounter has an ASUS Prime B350 Plus, was having crashes but is running fine [running patched Win10 VM] Naiqus has a Gigabyte X370 Gaming 5, and has not reported any issues [multiple VM's, did not list OS's] puddleglum has an ASRock AB350 Fatal1ty, and has not reported any issues [running Win10 VM] Bureaucromancer has an ASUS Crosshair VI Hero (X370 based), has had 2 crashes when idle and no VM's, no crashes with Win VM's [both Linux and Windows VM's] johnnie.black borrowed for a day an ASUS Prime B350M-A, and did not report any issues [did not report running any VM's] ufopinball has an ASUS Prime X370-Pro and has had 1 crash when only running a LInux VM [now running a Win VM now to test] chadjj has an ASUS Prime X370-Pro and is having issues similar to mine [ran a Windows VM before, but not now] I have an ASRock X370 Fatal1ty Professional Gamine, and I am having lots of issues in unRAID only [No VM's] JIM2003 has an ASUS Prime B350M-A, and had identical issues [No VM's] JIM2003 also has an ASRock Fatal1ty AB350 Gaming K4, and had identical issues [No VM's] Akio has ordered an ASUS Crosshair VI Hero, having assembly challenges with his waterblock cooler urbanracer34 has wants an ASRock X370 Taichi, not known if he bought it yet Reading through the list (and everyone's posts), a few things popped out at me. First, so far only X370 chipset boards have been reported as having any problems. So we might be looking at a problem specific to the X370, and not present on the B350 or A320 (which no one here seems to have purchased). The one exception to this is Beancounter was experiencing issue's on his B350, but those may have been caused by his Win10 VM, and recent Windows patches have fixed it. Second, seems like almost everyone immediately set up a Windows VM on their unRAID box. I seem to be one of the few that did not (I dual booted into Win10, but don't have a Win10 VM set up inside unRAID). This second observation becomes more interesting when you note that both chadjj and ufopinball are running the ASUS Prime X370-Pro, and chadjj is having issues and ufopinball is not. ufopinball does have a Win10 VM running. I don't know if chadjj ever got as far as a Windows VM, but his current testing has paired back the hardware and array to perform troubleshooting, so it seems he is not running one now. Add in Beancounter's note above that he was experiencing crashes (on a B350) that went away after his Win10 VM was recently patched. So now I am wondering, is running a Windows 10 VM somehow fixing the issue? And if so, how? -Paul
    1 point
  6. To be honest, I have no idea at all. I've seen references to people having to do this on installs and on certain updates, but its never affected myself. My pet theory on it however is that AMD chips are far better than Intel
    1 point
  7. I quickly checked over your logs and nothing jumped out leading to the issues you're experiencing. You have a TON of plugins installed so I'd recommend booting with 'Safe Mode' next time you try a newer version of unRAID to see if one of those plugins might be the culprit.
    1 point
  8. You can see the bitrate of the stream in the status view of tvheadend so you can compare it to the 4k streams you have tried. Have you tried using spmc instead of kodi?
    1 point
  9. Is it the same problem on all of them? Does the same problem occur if you watch TV in the webgui?
    1 point
  10. While you're joking around, here's some other inconsistencies: Regular members and moderators have access to change their cover photo (ie: banner, not the avatar) Developers do not. (This is my pet peeve - actually thought about asking for my level to be downgraded) As far as I can tell, nobody has any rights to actually view the posts within the Vendor forum area at all. Regular members can tell who likes posts by hovering over the number. Developer's cannot
    1 point
  11. Listen up, everybody ... Port Multiplication is a can of huge bucket!! of worms. Ever since the pioneering SiI3132 (and its 31xx brethren) [as PM-aware controller] and the SiI 3726 (& 4726/5744) [as Port Multpliers], not a single one of the "me too" followers has come within a mile of correctly implementing even 20% of the [/S]ATA/AHCI Specification for Port Multiplication. Yes, a specific controller chip will actually behave correctly in combination with a specific PM chip (usually with the necessary assistance of a vendor-supplied driver [like a private nurse as the only one who can communicate with the brain-damaged patient]) (or because the two are from the same manufacturer who precisely designed them to inter-operate correctly with each other [but each, independently, is provably brain-damaged]). As an example of that last point, I refer you to the nearby thread on the PEX-40071, which does the PM thing with a Marvell 9235 & a Marvell 9705 (the PM). It actually behaved/performed admirably. But when I tried to connect a SiI3726 (which my gut tells me does a thorough job of meeting the Spec) to a Marvell 9230 (a 9235 with a shoeshine), the results were a total disaster ... even though I can (sort of) get a Marvell 9120 to dance with that same 3726; they dance fine, but they need help getting out on the floor [Don't ask ... just stay away!] Now you know how many shakers of salt you need when you see "port multiplier" used in a bullet list of features for a controller or enclosure ... Caveat Emptor. --UhClem "Hey, mister, is this a game of chance?" ... "Not the way I play it."
    1 point
  12. Not easy to say what is wrong in your setup. Any errors when going to the status tab of tvheadend while playing? What do you use as the client? Do you have sync to framerate enabled in kodi?
    1 point
  13. With all due respect man, this is unwarranted. We take security very seriously. Case in point: totally dropped development last month to incorporate CSRF protection as fast as possible and it was a hell of a lot of work. We are team of 2 developers in unRAID OS core, and one of us can only spend half time at it because of other hats that must be worn. Reality is 99% of CVE's do not affect unRAID directly. Many are in components we don't use. Many apply only to internet-facing servers. We have always advised, unRAID OS should not be directly attached to the internet. The day is coming when we can lift that caveat but for now VM's can certainly serve that role if you know what you are doing. If you find a truly egregious security vulnerability in unRAID we would certainly appreciate an email. We see every one of those, whereas we don't read every single forum post. Send to [email protected]
    1 point
  14. I feel like I should start with a disclaimer... this is my current personal opinion, it comes with no warranty or guarantee. YMMV. etc. etc. Typically what people mean is "don't expose unRAID to the Internet". It is designed for use in a "friendly" network, and doesn't have things like password lockouts or a firewall. The WebUI, SSH, FTP, SMB would be examples of things not to expose to the net. But if you are comfortable running Plex on Windows and exposing that to the Internet, then it shouldn't be any riskier to do the same on unRAID (preferably using Docker). Same with nginx, openvpn, etc. (using non-standard ports when possible) I am pretty sure that the main security scares people have had are because they put their server in the DMZ or otherwise exposed it to the Internet. That and having another computer on their network get hit with ransomware. I think your ideas for securing unRAID are spot on: do not expose to the Internet assign strong passwords to root and all users use read only shares when possible keep unRAID, all plugins, and all dockers current To that I would add: use dockers rather than plugins whenever possible (install the Community Applications plugin to help find apps to install) if exposing dockers or VMs to the Internet, use non-standard ports when possible install the Tips and Tweaks plugin so you can disable the built-in ftp and telnet servers (unfortunately, these are difficult to disable without the plugin) install the Fix Common Problems plugin because it will notify you of repeated password failures (and many other potential problems) consider installing the Ransomware Protection plugin, which makes your shares readonly if one of the bait files is deleted/modified maintain backups that cannot be affected by ransomware do not use the built-in Firefox browser if you can avoid it keep all other computers on your network up to date with security patches / antivirus keep your router current as well And not really security related but worth mentioning: always use a UPS. It will save you a lot of headaches.
    1 point
  15. Is there a way to change the autowatch frequency? It seems to be random in how long it will take to grab a torrent from my watch folder. Sometimes it's a few minutes, and other times it's 10 minutes or more.. edit: answered my own question. first: docker exec -i -t rutorrent bash then vi /var/www/localhost/rutorrent/plugins/autotools/conf.php Change $autowatch_interval = 300; to whatever you want. I changed mine to 30 seconds. Type :wq to save. This setting will survive a container restart, but it will revert back to 300 seconds anytime the container is updated or if you edit container settings so you'll need to do these steps again in those situations.
    1 point