jonp

Administrators
  • Content count

    5577
  • Joined

  • Last visited

  • Days Won

    7

jonp last won the day on January 25

jonp had the most liked content!

Community Reputation

129 Very Good

About jonp

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • URL
    http://lime-technology.com
  • Location
    Chicago, IL
  1. Done. Let me know if that didn’t work for any reason.
  2. These are all the options we have. I’m inclined to just disable animated profile pictures. They aren’t necessary and I agree with BRiT that they can be downright painful to look at. Thoughts?
  3. I’ll look into this and see what options we have.
  4. Awesome!! Please do let us know if everything works after this adjustment.
  5. You can disable SSL from the Tools > Identification page. That will allow you to circumvent going to port 443.
  6. Your issue is likely the result of not having a minimum free space value specified for the share. Because we don't stripe data in the array, individual storage devices store individual complete files. As such, when a disk is nearing capacity, if you attempt to write a file to that individual disk that is larger than the capacity that disk has remaining, it will result in an out of space error. The way to solve for this is to set the minimum free space value to the size of the largest file you intend to copy to that share. So if we were dealing with a "movies" share, lets say, 50GB would probably suffice for most folks, though that might be larger if we're talking 4K content. Depending on how your backups work, you could be archiving one giant file (not ideal) or there could be a large set of smaller files (better).
  7. All Intel 1gbps/10gbps NICs should work fine with unRAID.
  8. This wouldn't surprise me either and likely explains your issue with the VMs tab not loading. When you click to load the VMs tab, libvirt tries to "check" all the hardware that is being assigned to that VM. This includes the virtual disk(s) and any PCI/USB devices that you are trying to pass through or assign to the VM. If a device query fails to return a response, the tab may appear to hang or be blank, because VMs that have invalid hardware assigned to them won't load. What is likely happening is that when the VM is first started, pass through works as intended and everyone is happy. At some point you want to reboot the VM for one reason or another (maybe a Windows update, maybe software crash, who knows) and when you reboot, the card may not be handling a function level reset properly. Some PCI devices were not designed with virtualization in mind, and therefore don't know how to deal with a scenario where an OS is rebooting without the BIOS itself on the host reinitializing. Unfortunately there is no way to predict what devices will work well or not with VMs until we try, and I've seen many users over the past few years mention lots of difficulty in getting these types of cards to work properly in VMs. Depending on your needs, you could simply opt to go with a HD Homerun type solution which now integrates nicely with Plex itself. These units can attach to your network as standalone boxes and can be managed via Plex (or other solutions).
  9. Hi there! Seems like you're having a heck of a time figuring out what's causing these problems, but I'm very curious if you've tried the approach suggested by Bob and johnnie.black: The basic suggestion here is to start running the system with no plugins, containers, or VMs installed/running. Just shut down those services from the Tools > VM Manager and Tools > Docker pages (set "enable" to no). Let the system run for a few days, maybe trigger a parity check or two to let it run through that process. See if the system remains stable using it like that. If so, next try adding your Docker containers / plugins. Let that run a few days with your containers / plugins. Next I would try adding a VM, but without passing through any PCI or USB devices. Just create a basic Windows or Linux VM and let it run for a few days. Lastly you can start adding PCI pass through and USB assignment if you desire, and see if that works. This is the best approach to take when trying to diagnose a faulty system. More than likely you have some hardware issues at hand here, but until we see what layer of the software is triggering those issues, we really don't know what steps to take. The fact that you have Machine Check Errors in the log is not a good sign either, and very much indicative of hardware issues. Could be that you have insufficient cooling / airflow. Could be a faulty component. I previously used to get a TON of MCE errors on one of my systems that was directly the result of a CPU heatsink becoming slightly loosened. As soon as I tightened it back down, the errors went away. MCE is a general term that could mean LOTS of different things. While I definitely appreciate the frustration because no one wants to deal with these kinds of problems, I do have a comment on this: Whether you use unRAID, Windows, or another Linux distribution, if you have hardware specific issues like these, pinpointing the root cause will require the same approach as suggested by Bob and Johnnie. Operating systems can do a pretty good job highlighting when a component just flat out isn't working, but when something is buggy due to improper cabling, cooling, seating of the device in its slot, etc., software can only do so much. Let us know how testing goes with the approach suggested by Bob and Johnnie and we'll see what we can do from there.
  10. default configuration lost

    Apologies for the delayed response on this issue. In short, I think you have some flash device corruption. Given that you didn't indicate what PCI devices you were trying to stub, my guess is that you were attempting to stub a USB controller and probably accidentally stubbed the USB controller to which the unRAID flash device was connected. What I'd recommend is putting the flash into a PC and running a checkdisk repairing any errors you find. If that doesn't work, you can try using a program like notepad++ to edit the files on the flash from that PC and properly remove the stubbing parameter from the syslinux.cfg file. The evidence of your flash device being corrupt is pretty clear in the logs: Jan 29 00:38:16 Tower kernel: FAT-fs (sda1): Directory bread(block 30290) failed Jan 29 00:38:16 Tower kernel: FAT-fs (sda1): Directory bread(block 30291) failed Jan 29 00:38:16 Tower kernel: FAT-fs (sda1): Directory bread(block 30292) failed Jan 29 00:38:16 Tower kernel: FAT-fs (sda1): Directory bread(block 30293) failed Jan 29 00:38:16 Tower kernel: FAT-fs (sda1): Directory bread(block 30294) failed Jan 29 00:38:16 Tower kernel: FAT-fs (sda1): Directory bread(block 30295) failed Jan 29 00:38:16 Tower kernel: FAT-fs (sda1): Directory bread(block 30296) failed Jan 29 00:38:16 Tower kernel: FAT-fs (sda1): Directory bread(block 30297) failed Jan 29 00:38:16 Tower kernel: FAT-fs (sda1): Directory bread(block 30298) failed Jan 29 00:38:16 Tower kernel: FAT-fs (sda1): Directory bread(block 30299) failed Once you rectify that issue, things should work normally again.
  11. Lose sound in Windows 10 VM when gaming

    Don't mistake my post as a blanket blame on your hardware. It very well COULD be something with 6.4, but without further information on the setup and your diagnostics, we really have nothing to go off of.
  12. No free USB ports error

    More information is needed from anyone with this issue. Please be sure to include your system diagnostics whenever posting for support.
  13. Lose sound in Windows 10 VM when gaming

    More information is needed. What is the sound device you are using? Is it a USB-based headset? If so, are you passing through the USB controller its attached to or are you simply using USB assignment? If not USB, onboard motherboard audio? HDMI audio through the GPU? Sounds like something hardware-specific or driver specific to me. Especially if you don't even need to reboot the guest VM to fix it.
  14. New Forum Registration Policy

    There is no solution that will 100% prevent spam. It's impossible to stop a human being from manually generating it. But that's just the thing, these are human beings that are spamming at this point. We know this because we have had Turing tests as part of registration and they still made it through. We also had a spam service investigate to confirm the same thing. Needless to say we are trying any and all solutions to combat this problem, but good moderation is the last line of defense that we will always rely on to catch bad actors. So please join me.in thanking these unsung heroes for their efforts here!!
  15. Hi Everyone! In an effort to combat spammers that are flooding the forum with spam posts, we are putting a new requirement in place: the first post of any new member MUST be approved by the moderators before normal members can see it and before additional posts will be allowed. We apologize in advance for any inconvenience that this may cause folks wishing to post, but due to the sheer nature of the spammers hitting us, this is one of the better ways for us to combat the issue for the time being. Thank you in advance for your understanding. All the best, The Lime Technology Team

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