Jump to content

Hoopster

Members
  • Content Count

    2682
  • Joined

  • Last visited

  • Days Won

    16

Hoopster last won the day on May 22

Hoopster had the most liked content!

Community Reputation

501 Guru

5 Followers

About Hoopster

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Utah USA

Recent Profile Visitors

4624 profile views
  1. You can reinstall them from the Apps tab (Community Applications) Previous Apps section. They will retain all previous settings. If your prior appdata path in the docker containers was something like /mnt/user/appdata/{name of container} you should not have to change anything with appdata now that it is on the cache drive. It is often recommended to change the appdata path to /mnt/cache/appdata/{name of container) with appdata on the cache drive as this solves some issues with certain containers. However, I would not be too concerned about it unless you have issues. Many of my containers are still using the /mnt/user/appdata/... paths without issue.
  2. Cache only tells the mover to take no action with files already on the array. They will stay there but new appdata files will go to cache. Here's the help from the Shares screen which explains that: You want to set the appdata share to Cache Prefer which will move everything from array to cache. Disable Docker first so there are no open files. After it has been moved, you can set it back to cache only if that is what you want. Same with isos and domains share if you have VMs but disable VMs before moving.
  3. Special BIOS gets you the ability to use the iGPU for transcoding. Without it, you could not even use the iGPU at all and all "onboard" video is BMC only.
  4. Yes. The license is tied to the unRAID flash drive and every server that runs unRAID must boot from a flash drive with a valid license (trial or purchased).
  5. i915 contains the video drivers for the integrated GPU. When 'modprobe i915' is run from the go file, you will lose video output from the BMC to the VGA port and will have a blank monitor screen as well as a blank KVM in the IPMI console. There is no way around this. Once the iGPU becomes the active onboard video adapter, the BMC is no longer outputting video to the VGA port/KVM. There is no path from the iGPU to the VGA port as this is controlled exclusively by the onboard BMC. You will get no video output from the iGPU but it can be used for transcoding. If you want console output, you can still use the unRAID terminal, PuTTY or something similar. All other aspects of IPMI continue to function and KVM video will be active for BIOS changes and through the boot process until i915 drivers load.
  6. Another possible option: Norco ITX-S8. A bit expensive perhaps.
  7. U-NAS does not make a 6-bay case; just 2, 4 and 8. Lots of requests for a 6-bay case, but, they have never made one. Fair enough. No use going bigger than you need.
  8. Perhaps the U-NAS 810A could be an option? It has 8 hot-swap bays plus an internal 2.5 SSD bay. It has two 120mm fans.
  9. Perhaps the U-NAS 810A could be an option (or have you already purchased the NAS6 case?) It has two 120mm fans and capacity for up to 8 hot-swap drives. I am not sure what the CPU cooler maximum height is but it is a top-mounted motherboard without a lot of clearance. EDIT: It looks like max cooler height is 58mm based on some user reviews (U-NAS does not tell you this) but you need some clearance if it is a top-flow cooler. My favorite compact cooler is the Noctua NH-L9x65 but at 65mm it is too tall for this case.
  10. Depends on the video settings and encoding parameters; however, relatively high CPU loads with Handbrake QSV encoding is normal; especially if you are comparing it to CPU utilization with Plex and QSV. Handbrake only uses QSV encoding. Decoding is still done by the CPU as are all subtitles and audio tracks. With QSV encoding in Handbrake my CPUs average in the high 60% to mid 70% CPU utilization. Without QSV encoding (all CPU for everything), CPU utilization is in the mid 90% range across all CPUs. However, QSV encoding is much faster than straight CPU encoding.
  11. I would be a bit concerned about cooling as the case has only one 80mm fan and no room for more. Does the drive hotswap cage have its own cooling? No mention of it in the specs. One 80mm fan is very little for six HDDs. Also, the CPU cooler height is limited to 40mm which you have noted based on your CPU cooler selection. That cooler is listed as compatible with the 3200G but with zero overclocking/turbo boost headroom. In other words, you'd have to disable, if possible, the automatic turbo frequency boost on the CPU or you could run into CPU cooling issues. It's a small, compact case and looks nice. My only concern is cooling, but that is often to 'gotcha' in these small Mini-ITX cases. The Fractal Node 304 case I am using for my backup server also accommodates 6 HDDs, but in a non hotswap configuration and it is a huge pain to access and modify drives and cabling. However, it has one 140mm and two 92mm cooling fans.
  12. I have my backup server in the Node 304 and yes, this is a big pain. Opening the case and swapping drives or modifying cabling in this case is a huge pain. Nice, compact case, but difficult to work with when you need to make changes. It also accommodates a maximum of 6 HDDs and you said you wanted capacity for up to 8. The DS380 does have cooling issues; however, there are some well documented and easy to make fixes that will improve drive cooling. I have the big brother of the DS380, the CS380, and the hotwap bays are very nice. Even the CS380 needs drive cooling mods. There may not be a perfect case for a small build, at least not since the Lian-Li PC-Q25 disappeared from production; so, pick the one that best meets your needs and work around the limitations. As mentioned, motherboard and CPU requirements will dictate which type of ECC RAM is supported; registered or unbuffered. Both of my servers require the UDIMM (unbuffered) ECC RAM. RDIMMs would not work even if I wanted to use this type.
  13. Yes, this is true. The BIOS provided by ASRock does allow the iGPU to be used for transcoding while also still having IPMI/BMC active for all functions except video output. This is working great. What it does not do is keep the video output to the VGA port/KVM active once the i915 iGPU drivers are loaded. The iGPU has no path to the VGA port so there is no video output (just transcoding) when it is loaded. Loading the iGPU deactivates the video output from the BMC to the VGA port as the BMC is no longer the active onboard video adapter.
  14. Not sure about these Supermicro boards but the ASRock IPMI server board I am using behaves the same way and I really don't expect it to be different. With the iGPU enabled in the BIOS for Plex transcoding the KVM video output via the IPMI console is lost when the iGPU drivers are loaded. This happens at the point modprobe i915 runs from the go file and takes over the video output. You cannot have video output simultaneously from both the BMC/onboard VGA and the iGPU. As soon as the iGPU video drivers are given control, there is no output to the VGA port or the KVM. This does not really bother me as I can get console output via the unRAID terminal, PuTTY, etc. Again, the Supermicro BIOS may magically enable both somehow, but the ASRock IPMI boards (I have two) do not. I am OK with the tradeoff in order to use the iGPU for transcoding.
  15. Rsync - yes, with the right flags, it can verify the files reach the destination and are an exact copy of the source files With the transfer running, I was still able to use the source server. I really did not see too much of an impact My backup server has an IPMI motherboard. The rsync backup script powers backup server on before running the backup and powers it off when the backup is complete. Before the IPMI motherboard, the script just woke up the server from S3 sleep and put it back to sleep when the backup ended Parity checks are run manually in my case, but it could be automated I assume through user scripts My backup script backs up only new files or those that have been modified. Once every three months or so another script runs to delete files from the backup server that are no longer on the source server. This is plenty of time to figure out if something important is missing from the source server. The whole process is documented in this thread. It is set-it-and forget it and has been running automatically with no user intervention at all for over two years. The script does the following: power on backup server prepare log files and email information perform a share by share backup write to logs for each share email backup summary to me when complete power off backup server The script is automated to run once a week through User Scripts.