Hoopster

Members
  • Posts

    4119
  • Joined

  • Last visited

  • Days Won

    24

Hoopster last won the day on June 7 2022

Hoopster had the most liked content!

7 Followers

Retained

  • Member Title
    unRAIDy to Rumble

Converted

  • Gender
    Male
  • Location
    Utah USA

Recent Profile Visitors

12287 profile views

Hoopster's Achievements

Experienced

Experienced (11/14)

979

Reputation

26

Community Answers

  1. I get the feeling you could post this every month for a long, long time and it would still be true. Notice how it never shows up as an option for voting in wish lists or feature request polls? It's an often-debated topic in these forums but no one from Limetech has ever hinted that it is even under consideration.
  2. Just as an FYI - here is a description of all the cache settings that can be applied to each Unraid user share:
  3. Read speeds in Unraid are limited by the speed of the single disk on which the file is stored. It is also possible to configure shares as "cache-only" shares. This means the data lives on a cache drive only and is never written to the parity-protected array. As an example some Unraid users put a copy of some Plex data (most commonly viewed movies or TV Shows, etc.) In a cache-only location. However, management of this is manual. There is no mechanism in Unraid to decide what is most-commonly accessed and to move it automatically to a cache-only share.
  4. A cache drive does not function like a cache buffer on a hard drive. Unraid cache is not a location in which frequently accessed files are stored for faster access. The cache drive in Unraid has as one its functions the ability to cache writes to the parity-protected array. Writes to the parity protected array will be slower than to an SSD cache drive. On a share-by-share basis, you can tell Unraid to write the files first to a cache drive. Since the cache drive is not part of the parity-protected array, this initial write to cache does not pay the "parity write penalty." The Mover can then be configured to write the cached files to the HDD array at a low usage time such as 2am. While on the cache drive, files are treated like they are on the array in the designated share and there are no access issues. The "downside" to caching writes is that files on the cache drive are not parity protected until they are written to the array by the Mover. There is an alternative known as "turbo write" which writes files to the parity-protect array much faster than the default read/modify/write method but it does require all array disks to be spun up. There is a also a turbo write plugin which enables/disables turbo write as needed. If you are only getting 7-9 Gb/s on iperf, there are likely some configuration tweaks needed. You are going to be able to take advantage of 10G networking transfer speeds only when writing between fast SSDs on both ends of the transfer. Once you have a mechanical drive in the data transfer path, you will get sub 1G speeds.
  5. After a longer time at idle it did dip down to 24 watts. Perhaps something was going on that I did not detect initially after the disks spun down. Sent from my iPhone using Tapatalk
  6. On the Kill-A-Watt, the idle power draw bounces between 31-35 Watts. This is with all six disks spun down and no active docker containers or plugins. I also have no discrete GPU in this system and rely on the iGPU in Xeon E-2246 CPU. Bifurcation on the single x16 PCIe slot in the E3C246D2I Mini-ITX board is the same as the E3C246D4U. Here is a screenshot taken from my E3C246D2I:
  7. Which one? E3C246D2I Mini-ITX (8 SATA ports; 4 onboard, 4 with OCuLink cable) or E3C246D4U MicroATx (8 onboard SATA ports) Both have IPMI Of course, if you are talking about bifurcation, I assume you mean the E3C246D4U and no the Mini-ITX board with just one x16 PCIe slot. C246 WSI has no IPMI. I have a Kill-A-Watt I could attach to either system. Here are the bifurcation options for the PCIE6/PCIE4 slots:
  8. Check into Jellyfin Emby also requires a paid version for hardware transcoding.
  9. Edit Plex docker container, then add another variable:
  10. WireGuard is a VPN protocol. Many of the docker containers that use VPNs can work with a VPN service/provider which may or may not use WireGuard as the VPN protocol. In the example I gave above of DelugeVPN, I use it with the Private Internet Access VPN service over the WireGaurd protocol. The WIreGuard protocol implemented in Unraid will allow you to setup secure remote connection and even route all remote traffic through the WireGuard VPN connection if desired. However, WireGuard is not full-fledged VPN service/provider. Here is a link to an article which mentions which VPN providers use WireGuard.
  11. Same thing. Containers that use a VPN (DelugeVPN just as an example) have instructions for how to configure them to use VPN protocols such as OpenVPN or Wireguard. However, you still need a VPN provider such as Private Internet Access, AirVPN, etc. Q21. I now see that you support WireGuard, how do i switch from OpenVPN to WireGuard client? A21. Yes you are correct, all binhex VPN created images now support OpenVPN and WireGuard, for PIA and other VPN providers. If you're a PIA user then please follow this procedure:- Change Docker parameter from --cap-add=NET_ADMIN to --privileged=true (WireGuard requires privileged permissions). Add environment variable and set the Key: (NOT the name) to VPN_CLIENT and set the Value: to wireguard. Start the container with the new parameters. Once the container has started you should then be able to see the dynamically generated WireGuard config file /config/wireguard/wg0.conf. If you wish to change the endpoint (default is nl-amsterdam.privacy.network) then open the file /config/wireguard/wg0.conf and change the Endpoint line to the endpoint you want to connect to (the list of all port forward enabled endpoints is shown in the log /config/supervisord.log) If you're a 'custom or airvpn' VPN user (non PIA) then please follow this procedure:- Change Docker parameter from --cap-add=NET_ADMIN to --privileged=true (WireGuard requires privileged permissions). Add environment variable and set the Key: (NOT the name) to VPN_CLIENT and set the Value: to wireguard. Start and stop the container to force the creation of /config/wireguard/. Copy and paste in the WireGuard configuration file for your VPN provider to /config/wireguard/ Start the container and monitor the log /config/supervisord.log to ensure the connection is established.
  12. I use the built-in WireGuard in Unraid and not the WireGuard Easy docker container so I do not know what you can do with it. You might want to ask the question in WireGuard Easy support forum. I am fairly certain other containers do not just use WireGuard by default without some configuration if it is supported.
  13. The WireGuard Easy docker container is not associated with WireGuard built into unRAID. No unRAID WebUI VPN Manager settings will have anything to do with the WireGuard Easy docker container you have installed. Yes, you can use the Wireguard Easy docker container and get the same benefits as the built-in WireGaurd but you can also just use the built-in WireGuard and configure it through VPN Manager settings without having the docker container installed. I am personally not a fan of WOL as it can be flaky and is highly dependent on the motherboard/chipset supporting it and implementing it correctly. If your motherboard does not have IPMI, I would much prefer to use a true remote power on/off solution such as a PiKVM. Yes, it is additional hardware but it just works. There is even an internal PiKVM solution.
  14. I never had a server "die." I have upgraded main hardware components (MB, CPU, RAM) about every 3-4 years and sold the old parts. Even my disks have been swapped out for fewer larger disks a couple of times. I have one 24x7 server and one backup server that gets powered on via IPMI once a week to backup the main server. They are very similar, though not identical, in hardware but the data is identical. If the main server fails, I can quickly switch to the backup. I also agree that I would not attempt to replace 5+ year old MB or CPU if it died. For me, that would call for new hardware.
  15. Well, at least you got my age right. I work in front of a computer all day and there is always a browser tab with the forums open. When I need a break from real work, I just check what is going on in the forums. I can't help on a lot of deeper topics but I figure I can help out by picking off some of the easier things and freeing up the real rockstars to do their thing more. 😀