Jump to content

aim60

Members
  • Content Count

    70
  • Joined

  • Last visited

Community Reputation

4 Neutral

About aim60

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. For me, building with removable drive bays, then keeping my hands out of the box unless absolutely necessary, has added more to the reliability of my hardware than any other factor. +1 for using server class hardware.
  2. Unless you really need it, make sure UPnP is turned off on the router.
  3. I'm recording to a local drive on the MC pc. Weekly, I am moving the recordings to unraid. They never exist in both places at the same time. After moving recordings, I need to restart the Windows Media Center Receiver Service so MC registers the change in the location of the recordings. Keep in mind that with your method, you are asking unraid to do something that it was never designed to do - receive data on a real-time basis. The more simultaneous recordings that you do, and other things you may have running on on the server (plugins, dockers, VMs), the more difficult it will be for unraid to keep up. The forums on www.thegreenbutton.tv have several threads on user experiences recording to a NAS. In the future, I am going to attempt to run Win7 MC as a VM on unraid. And I'll either direct recordings to a dedicated Unassigned Devices drive, or pass through a physical drive to the VM for recordings. In my house, all sh*t breaks loose if recordings are corrupted.
  4. I've always been reluctant to try your method, except on my test MC server. Especially with reports of array slowness in 6.7.x. I record locally, then weekly, copy the recordings to Unraid, and remove them from local storage. At the very least, consider limiting your recordings share to one disk, and have the link reference \\server\diskx\sharename rather than \\server\sharename, bypassing the overhead of the Fuse file system. There's no problem having MC use unc paths to previously recorded content. Its only the recording drive that needs the mklink trick. Nothing else comes to mind about using MC with Unraid.
  5. The following is from Windows 7 MC. In MC, go to Tasks | Settings | TV | Recorder | Media Libraries | Remove folders from library. Verify that you do not have a reference to the recordings share on Unraid. If you do, delete it. Media Center should only know about your local drive, which is linked to the share. It won't show up in this list because its the recording drive). If MC knows about both, you'll show the duplicate recordings.
  6. I use the Recycle Bin plugin for accidental deletions. Works well, but only catches deletions via SMB, not through the console or a file manager like krusader.
  7. @binhex, consider adding this information to the first post. It will help new users decide which docker to use.
  8. For experimentation, I'm running two Plex dockers (one LinuxServer and one Binhex), using different appdata folders. Since you can't change the port that Plex listens on (38400), I needed to assign a different IP address to one of the dockers. So the Binhex docker is running on Custom:br0, and a fixed IP address. br0 is a Linux bridge, not a Docker bridge, so port mappings are not required. Its like Host mode. I'm still on 6.6.7, but that shouldn't matter.
  9. I believe that within unraid you can only use vlans for dockers and vms. See if you can configure your switchport to send vlan 10 traffic as untagged, while sending the other vlans as tagged.
  10. Make sure all shares are set to COW. Any problem converting the system share containing the docker and libvirt images to COW?
  11. I'm planning on adding a new SSD to my cache pool, and was wondering if and how Unraid users test new SSDs. I give spinners a SMART long test, and 3 Preclear passes.
  12. While testing the "Virtual Machine Wake On Lan" plugin, I discovered that I had two VMs using the same MAC address (sloppy editing of the XML's). It would be useful if Fix Common Problems could scan the docker configs and VM configs for duplicate MACs, and the docker configs for duplicate IP's.
  13. If the interface is connected to a cable modem (not router) or some such device, your upstream provider's first hop is on the same link-local subnet that you are. It seems that the most secure way to run a vm firewall is with a pass-through wan nic.
  14. Testing done with 6.4 RC6, with unRAID and a test client in VM's. Even though an interface is configured for "Network Protocol = IPv4 only", an IPv6 link local address is being assigned to the interface or bridge. This happens if an IPv4 address is assigned, or the interface is configured for "IP Address Assignment=None". The enclosed screenshots show the server Network Settings, an ipconfig, and a Windows client connected to eth1 with no IP addresses assigned. The client can ping the server, access the management GUI, and access server shares, all through the IPv6 Link Local address. This can be a security concern if the interface is Internet facing, with the intent that the bridge will be used for the wan port of a vm firewall . unRAID 6.4 RC6 IPv6.zip
  15. Sure. Watch Gridrunner’s excellent video for background information.