jonp

Administrators
  • Content count

    5554
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by jonp

  1. Forum vote for blocking

    We've had recaptcha on this forum since we migrated to it. We even upgraded to recaptcha v2. Now we are considering implementing keyCAPTCHA as IPS is recommending it, but I'm not 100% sold on that idea just yet. We are still looking into more solutions for anti-spam. As much as we all want this to be a quick and easy fix, it might not be...
  2. From discussion that start in this thread, we decided to create a simple plugin that installs a set of additional command line tools onto your unRAID server. WARNING: These tools are for advanced users. Their use is not officially supported by Lime Tech. Use at your own risk and do not ask for direct support from us on the use of these tools. Eric put this plugin together mainly so that folks who want to do development or more advanced functions can have access to do so without having to manually download and copy the Slackbuilds to their USB flash device. Here are the packages that are included in this plugin: apr 1.5.0 apr-util 1.5.3 bwm-ng 0.6 cpio 2.11 git 2.3.5 iftop 1.0pre2 inotify-tools 3.14 iotop 0.6 iperf 3.0.11 kbd 1.15.3 lftp 4.6.1 lshw B.02.17 neon 0.29.6 p7zip 9.38.1 perl 5.22.0 python 2.7.9 readline 6.3 screen 4.2.1 sshfs-fuse 2.5 strace 4.10 subversion 1.7.16 unrar 5.2.5 utempter 1.1.5 vim 7.4.898 If someone wants to write up a small description of each of these tools, I will incorporate into the OP here. Otherwise, google is your friend Here's the link to the PLG itself (now on dmacias' repo). Copy and paste this on the "install plugin" page of the webGui and you'll be on your way! https://raw.githubusercontent.com/dmacias72/unRAID-NerdPack/master/plugin/NerdPack.plg
  3. [6.4.0] Strange ASUS 10gb Nic issue

    Hi Alex, We've looked into this issue and have determined this may be the result of a buggy driver implementation in the Linux kernel related to this device. In your e-mail to us, you indicated ASUS has provided you with an out-of-tree driver that doesn't match what is in the Linux kernel that we use. I would encourage you to contact ASUS and urge them to consider implementing this supposedly "better" driver in the kernel tree if it will result in better experiences for their customers. In short, we will not be building in this out-of-tree driver for your device into unRAID. The reason is quite simple: it could break things for others. Previously we implemented an out-of-tree Linux driver for Intel's 10gbe NICs and while some folks reported better experiences after this, others reported numerous problems. Later we reverted to the in-tree driver in a later kernel revision and everyone was happy. The issue here is that we don't know what building this out-of-tree driver might do and we can't guarantee that it will always build correctly against future kernels. So in the meantime, the recommended solution for using 10gbe on unRAID is to procure Intel-based 10gbe NICs (or at least NICs that have been tested and vetted here by the unRAID community). I wish I had a better answer for you, but the hard truth is that ASUS may just not have as much love for Linux as they do for Windows.
  4. Hello unRAID Community! For far too long now we have gone without a proper logo for unRAID. We have wanted one for some time now, but because none of us at LT are graphic artists, we were afraid we'd end up with something like this: So instead of assaulting your eyes with our pathetic attempts at art, we thought we'd throw it out to you, our community, to see if any talented artists out there want to submit their ideas and concepts for consideration. We will be working with a professional designer to generate the final artwork, but your ideas could shape the look and feel of the logo. Here's a quick run-down of how we're going to do this: All proposals must be in before December 3rd, 2017. The logo should be 1024 x 1024 pixels in size, and should look good when downsized to 512 x 512 or even 256 x 256. Creating a vector-based image (think Adobe Illustrator) is highly recommended. No "tagline" is required to be in the logo (e.g. "The Ultimate Home Media Server"), but if you have an interesting one that you want to include, go for it! Feel free to submit multiple options if you have more than one! You must own the copyright to any images/art you use and be willing to transfer said ownership to Lime Technology, Inc. Any fonts you use must be royalty-free, otherwise we can't use them. Open source fonts are a big plus. To submit a proposal, simply reply to this thread and include your work in the post. If you wish to incorporate the use of stock photos/imagery, please provide a link to where it can be purchased along with your submission (original artwork will definitely be looked at more favorably). It is possible that we may want to include concepts from multiple designs. NOTE: If you are a professional designer and wish to be considered for contracting the final work, please indicate as such in your response and be sure to include a link to a portfolio of your work. Thanks in advance for all of your submissions!
  5. Although the allow unsafe interrupts line really belongs right after the "append"
  6. That's fine. No issue.
  7. Hey guys, just wanted to give you all an update on the OVMF issues some of you are experiencing. The issue is the use of the VIRTIO bus for the install media in OVMF. More simply put: Here's the quick fix for those that can't wait to play with OVMF and UEFI. All you need to do is use the XML editor and make a few small changes. Here's the procedure for Windows. For Linux, the steps are the same, but you won't have the VirtIO driver iso. 1 - Create a new VM using "advanced view" to choose the OVMF setting 2 - Set your install media ISO and VirtIO driver ISO 3 - Set your primary virtual disk as you normally do 4 - Create the VM. 5 - Force shutdown the VM. 6 - Edit the XML for the VM. 7 - Locate this section: <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/win81.iso'/> <target dev='hda' bus='virtio'/> <readonly/> <boot order='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-jan15.iso'/> <target dev='hdb' bus='virtio'/> <readonly/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> 8 - Remove the <address> section for each <disk> 9 - Change the bus from virtio to ide 10 - Save the XML 11 - Start your VM 12 - You should be prompted to boot from your install media (no UEFI shell commands required) 13 - If not, type the following commands from the UEFI shell: fs0: cd boot/efi bootx64.efi If none of this works for you, please report back here sharing your complete XML. Thank you!
  8. Thanks everyone for all the feedback on the new release so far!! It really helps to know how people are doing with their upgrades and what issues (if any) arise. Please keep it up!
  9. Just as an FYI, the majority of issues I've seen reported in this thread are from onr of two causes: 1) using non standard / directly supported configurations (such as modifications to go file or use of 3rd party plugins) 2) upgrading from a much older version of unraid directly to 6.4 It appears the majority of folks running stock builds and that were on 6.3.5 have had little to no issues with the upgrade. Please keep the feedback coming!!
  10. Hey guys, Thought I should post this because I've seen multiple threads/posts referencing hard crashes on rc9, many of which do not contain any diagnostics for us to review. Logically this is because when a system hard crashes, you can no longer get to the UI which prevents you from obtaining those logs. Without a log event, diagnosing, reproducing, and resolving a hard crash issue can be neigh impossible. As such, if you can repeatedly cause a hard crash like this, you will need to attach a monitor and keyboard directly to your unRAID system and reboot the system. From the console, login with your root user and type the following command: tail /var/log/syslog -f When the system reaches a hard lockup, take a picture of what's on the screen and post a new message in this forum with a prefix indicating it is a hard crash. Also include your diagnostics from a clean boot so we can review your system configuration as well. Thanks everyone!
  11. Forum vote for blocking

    I should add that we are also investigating setting post limits on new members, but we haven't done that just yet. We really want to be careful about maintaining a balance between good anti-spam measures while not being too restrictive on those who legitimately want to post in here.
  12. Forum vote for blocking

    A few more updates to this issue: #1: We have applied limits to forum search and posting. Users must now wait 30 seconds between created new posts and 10 seconds between searches. Unfortunately we have noticed a lot of bots indexing the forum using search and eating up a lot of system resources. These limits should curtail some of that. #2: We have implemented a secondary spam protection service. Now we have TWO systems in place to try and thwart would-be spammers. Lastly, I just want to say thanks to our moderators this week for helping stomp out these spammers for us. Automated anti-spam protection is very important, but there is no anti-spam system that can systematically prevent all forum spam. Some folks are very creative in working around the anti-spam systems and when that happens, we rely on our mods to help combat the issue in real-time. We think they've done an amazing job and for that, we thank you all.
  13. Hey everyone! I thought it'd be prudent to create a thread with all the tips and tricks to using the new forum software as we discover them. Some users have already pointed out some fairly useful ones and I thought we'd start aggregating those in a common thread here. If you find any good tips or tricks, post them here and I'll incorporate them into the OP. Thanks! Highlight to Quote If you highlight a section of text in a post by clicking and dragging with your mouse, then afterward you will see a "Quote this" hovering above the selected text. Clicking that will automatically quote the text selected into a reply post, even citing the author of the highlighted text correctly. Highlight Thread to Preview OP and Last Post When browsing any particular forum, if you put your mouse over the topic subject, a preview window will pop up allowing you to see both the original post as well as the last post in the thread. Click and hold topic name to rename a topic Mess up with the name for you topic before you submitted it? Not only can you fix this in the "Edit Post" screen, but you can even fix it when just browsing the forum itself. If you click and hold on a topic name (that you created), you can rename the topic right from there! Found a trick? REPLY HERE! If you find any more tricks you think are worth sharing, reply to this post with what you found and I'll update the OP to include the trick!
  14. VM Issues

    Are you booting your server in UEFI mode or legacy BIOS mode (CSM)?
  15. Forum vote for blocking

    Ok, we believe we have identified the issue causing the spamming and have implemented fixes. Part of these fixes includes changing to recaptcha 2 for human validation during account sign up and adding some manual question / answer work for the user to do. These two things alone should heavily combat the spam issue, but we'll be monitoring closely to ensure all is working as intended.
  16. Forum vote for blocking

    Just a public update on this. We are actively looking into this issue. IPS does have forum spam prevention, so we're not sure why the sudden rush of spam bots (spam prevention has been working just fine for some time now). We'll update everyone again once we have some more news. For now we just have to play a bit of whackamole.
  17. Hey everyone, just thought I'd put this up here after reading a syslog by another forum member and realizing a repeating pattern I've seen here where folks decide to let Plex create temporary files for transcoding on an array or cache device instead of in RAM. Why should I move transcoding into RAM? What do I gain? In short, transcoding is both CPU and IO intensive. Many write operations occur to the storage medium used for transcoding, and when using an SSD specifically, this can cause unnecessary wear and tear that would lead to SSD burnouts happening more quickly than is necessary. By moving transcoding to RAM, you alleviate the burden from your non-volatile storage devices. RAM isn't subject to "burn out" from usage like an SSD would be, and transcoding doesn't need nearly as much space in memory to perform as some would think. How much RAM do I need for this? A single stream of video content transcoded to 12mbps on my test system took up 430MB on the root ram filesystem. The quality of the source content shouldn't matter, only the bitrate to which you are transcoding. In addition, there are other settings you can tweak to transcoding that would impact this number including how many second of transcoding should occur in advance of being played. Bottom line: If you have 4GB or less of total RAM on your system, you may have to tweak settings based on how many different streams you intend on transcoding simultaneously. If you have 8GB or more, you are probably in the safe zone, but obviously the more RAM you use in general, the less space will be available for transcoding. How do I do this There are two tweaks to be made in order to move your transcoding into RAM. One is to the Docker Container you are running and the other is a setting from within the Plex web client itself. Step 1: Changing your Plex Container Properties From within the webGui, click on "Docker" and click on the name of the PlexMediaServer container. From here, add a new volume mapping: /transcode to /tmp Click "Apply" and the container will be started with the new mapping. Step 2: Changing the Plex Media Server to use the new transcode directory Connect to the Plex web interface from a browser (e.g. http://tower:32400/web). From there, click the wrench in the top right corner of the interface to get to settings. Now click the "Server" tab at the top of this page. On the left, you should see a setting called "Transcoder." Clicking on that and then clicking the "Show Advanced" button will reveal the magical setting that let's you redirect the transcoding directory. Type "/transcode" in there and click apply and you're all set. You can tweak some of the other settings if desired to see if that improves your media streaming experience. Thanks for reading and enjoy!
  18. Hi Kil0gram, What we need is something in your logs or diagnostics that points to a problem. Right now we are not seeing one. The tailed log you captured doesn't show any errors of any kind. The AFPD messages in your tailed log screenshot are not relevant (they have to do with AFP protocol, nothing to do with SMB or Active Directory and wouldn't cause system hangs). Have you tried a memtest on the system? (asked previously in this thread with no response) Have you tried another OS on the system? (asked previously in this thread with no response) How have you ruled out faulty hardware, cables, etc.? The unRAID community is incredibly helpful and willing to jump in to lend a hand, but when there is not a thread of evidence to support a software problem (such as a kernel panic, call trace, etc.), there is really nothing for us to do. We have plenty of customers using unRAID with an AD domain and I'm sure we'd have a lot more e-mails about the problem if we had a software defect on our hands. My biggest concern with the way this thread is going is that the first time you heard from someone in our community (Johnnie.Black), he posed two questions to you that you completely disregarded. If you want us to help you, you have to respond to what folks say in here, otherwise it feels like a lost cause.
  19. Turbo Write

    Tom M, please add details to this feature before we release 6.0, but essentially, this is the ability for smaller arrays to write data faster without caching.
  20. A feature we are considering REMOVING at some point in the future of unRAID 6 would be that of spin up groups. This feature was originally designed to combat an issue specific to the use of IDE hard drives that are no longer prevalent in today's computers. The poll question here is to ascertain who, if anyone, is using this feature today and if so, for what purpose. Please provide your feedback and if you do use spin up groups, please let us know how they help you! Thanks!
  21. Keyboard freeze/lag

    Hi Mads, That is odd behavior indeed. There are a few things we can try to resolve the issue: Try changing the USB type from the Edit VM page. You'll need to turn on advanced view on that page, but near the bottom you'll see a drop down choice for the USB type and the options will be USB 2 and USB 3. Try toggling that setting and see if the issues persist. Try changing USB keyboards. Sometimes issues like this can be hardware specific. Some USB devices hardcode in functions that cause the device to reset, which in turn can disconnect it from the running VM instance. The manufacturers never previously had to consider a scenario whereby the OS wouldn't automatically pick up the device upon the reset, so this is "working as intended" in their minds. When this is the case, there are two things you can try and changing the device is one of them. Try passing through an entire USB controller. In the event that you have a real attachment to this specific keyboard and the issue ends up being hardware-specific, you can always purchase a USB controller and pass the entire thing through to your VM. That should resolve any issues. With respect to the VNC Viewer, this mode is only supported if you aren't passing through a GPU to the VM. Once passed through, using VNC as a secondary graphics adapter doesn't always work right and is mainly for testing / debugging purposes only. If you want to still access your VM using a VNC client, you can install a VNC server inside your VM. All the best, Jon
  22. Correct. It's untenable for us to support AMD specific issues with a special kernel build. The purpose of the rc17b separate bzimage file was to confirm whether or not the patch even worked for those users to see if they were at least on to something. Unfortunately the "ugly patch" is ugly simply because of the fact that it can break stability for other users that aren't on AMD platforms. The unfortunate state of affairs with AMD right now is that they have some Linux-specific issues they need to address before Ryzen / TR can be truly recommended. I love the idea of a high-core count low cost CPU solution that competes with Intel, but it has to be feature-complete and stable first.
  23. One of the biggest limitations of managing game installations in Windows is the inability to move games from one storage location to another. Instead, we are forced to uninstall and reinstall games from scratch, increasing the time and effort required to manage our storage needs. In this video, we show you how to more efficiently manage your game library through user shares, enabling you to easily move games between high-performance and high-capacity storage without needing to reinstall them. We specifically highlight the proper procedures to configure this for both Steam and Origin.
  24. In a recent reply to a post by another forum member (archedraft), I provided this guide to help him assign one of his NIC devices to a virtual machine, leaving the other for host networking (unRAID OS). I didn't see much point in this because with KVM and VirtIO, we can create virtual network interfaces that offer little to no overhead over a physical NIC, but after testing with pfSense, archedraft confirmed for me that he saw a dramatic performance increase. The reason? In this particular instance, pfSense was acting as a firewall and is based on FreeBSD. The FreeBSD kernel used by pfSense, while having support for VirtIO, appears to be out of date and was not allowing full 1gbps LAN throughput as it does with Linux or Windows VMs. Passing through a physical Ethernet controller to his pfSense VM in this instance resolved his issue. So we have found at least one use case thus far to consider such a method, but in the future, we may find more. And since the question comes up from time to time, I thought it prudent to post this here as an advanced guide for those that want to try it. WARNING: If you do not have multiple NICs in your system, doing this will result in your server losing all network connectivity. IMPORTANT: Regarding VM to Host Networking Performance When VMs utilize VirtIO, their is another distinct advantage in that networking between the host and guest can take place without traversing the copper wire. This allows for much faster throughput than the physical NIC hardware even supports at the port level. As an example, in mounting an SMB share to my SSD-based cache pool from inside my Windows VM, I was able to see IO throughput to the share exceed 250MB/s (that's megabytes, not bits). When a VM is assigned a physical network controller, this advantage disappears as the VM will communicate with the host as if it was a separate physical machine, going out the one NIC, down to your router/switching infrastructure, and then back in. This will limit your network throughput to that of the physical hardware. In my previous Windows VM / SMB example, I would be limited to 1gbps or 125MB/s. Guide 1 - Login to your server via ssh. 2 - Type the following command: lspci You will get a list like this: 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4) 00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series] 02:00.0 VGA compatible controller: NVIDIA Corporation GK110 [GeForce GTX 780] (rev a1) 02:00.1 Audio device: NVIDIA Corporation GK110 HDMI Audio (rev a1) 04:00.0 Multimedia video controller: Device 1a0a:6202 (rev 01) Identify the Ethernet controller you wish to assign. Note the PCI address for the device (from my list, it would be 00:19.0). From my list, I only have one network card, so I shouldn't do this, but if you have multiple, either one SHOULD be fine to select. 3 - Type the following command: lspci -n 00:00.0 0600: 8086:0c00 (rev 06) 00:01.0 0604: 8086:0c01 (rev 06) 00:01.1 0604: 8086:0c05 (rev 06) 00:02.0 0300: 8086:0412 (rev 06) 00:03.0 0403: 8086:0c0c (rev 06) 00:14.0 0c03: 8086:8c31 (rev 04) 00:16.0 0780: 8086:8c3a (rev 04) 00:19.0 0200: 8086:153b (rev 04) 00:1b.0 0403: 8086:8c20 (rev 04) 00:1c.0 0604: 8086:8c10 (rev d4) 00:1c.3 0604: 8086:8c16 (rev d4) 00:1f.0 0601: 8086:8c44 (rev 04) 00:1f.2 0106: 8086:8c02 (rev 04) 00:1f.3 0c05: 8086:8c22 (rev 04) 01:00.0 0300: 1002:68f9 01:00.1 0403: 1002:aa68 02:00.0 0300: 10de:1004 (rev a1) 02:00.1 0403: 10de:0e1a (rev a1) 04:00.0 0400: 1a0a:6202 (rev 01) 4 - Identify your network card by PCI address (first column of results). 5 - Obtain the vendor/product ID for that device from the last column. 00:19.0 from my example is 8086:153b. 6 - Edit your syslinux.cfg file and add the following after the append but before initrd=/bzroot. pci-stub.ids=8086:153b REPLACE THE VENDOR/PRODUCT ID FROM MY EXAMPLE ABOVE WITH THE ONE YOU OBTAINED IN STEP 5. 7 - Reboot your system. 8 - Edit your VM using the XML editor mode. 9 - Add the following between the <devices> and </devices> tags. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x19' function='0x0'/> </source> </hostdev> Modify the address line entering in the two digit bus, slot, and function from your ID. So 00:19.0 translates to what I have above. Save the XML and start your VM. All should be right as rain! NOTE: If you get an error, it could be because your NIC is in an IOMMU group with another in-use PCI device (either assigned to the host or to another VM). In this instance, you can attempt to use the PCIE ACS Override option under the VM Manager settings page, but use of this toggle is considered experimental.
  25. UPDATE 4/27/2015: --cpuset will be deprecated in Docker 1.6. For those using unRAID 6 beta 15, you are not affected, but when we upgrade to Docker 1.6, this will be impacted. The new method will be to use --cpuset-cpus (it's just being renamed). Hey guys, wanted to share something cool we figured out today that can substantially impact how Docker and VMs work together on the same host. In short, you can force individual containers to be bound to specific CPU cores inside unRAID. Why is this useful? The number one thing that can affect user experience for VMs running on an unRAID host that are localized is context switching. When applications are competing for access to the CPU, they essentially take turns and when that happens, the processor performs a context switch where it unloads data from within the processors L1, L2, and L3 cache back into RAM temporarily so that the other process can load into that cache quickly to perform it's job, then unload and reload the first process. While this is a normal thing to occur, it can cause some undesirable effects when severely processor intensive activities are happening in both a container and a VM at the same time. By pinning specific containers to specific cores, similar to how we can with virtual machines, we can completely eliminate the need for context switching to occur and as a result, avoid undesirable impacts to user experience. How to do it The plan is to implement this into dockerMan in an upcoming release as an advanced configuration option that you can choose to apply to all docker containers or individual containers, but for now, you can take advantage of this TODAY by modifying your existing containers in dockerMan like so: In the "repository name" field, simply add the following code before the name of the author/repo: --cpuset=# If you want to set multiple cores, you can do so by using commas or to specify a range of cores, you can use a dash. Examples: --cpuset=0,2,4,6 --cpuset=0-3 Note that cores are numbered starting with 0. Also note that you can check the # of cores you have in total on your system by typing the following in a command line session (SSH or Telnet): nproc

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.