thatonethur

Members
  • Posts

    18
  • Joined

Recent Profile Visitors

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

thatonethur's Achievements

Noob

Noob (1/14)

1

Reputation

  1. So my proxynet network still exists. I have no idea how to explain that it's constantly bouncing up and down status. I started using Uptimerobot to monitor if it's up and down and I can say that it bounces between up and down at least 30 times per day.
  2. Trying to rack my brain as to what changed as SWAG as worked perfect for years. My scenario: Multiple dockers (primarily used for Plex and Emby) proxied using SWAG (latest version). Local SWAG docker is on separate "proxynet" network per SpaceInvaderOne's video and points to local port of 3553. From my router/firewall, I port forward inbound traffic to 3553 docker IP (which is same as Unraid box) NOTE: I have another docker container that connects directly to a specific port and while 443 is timing out, the other specific port is working just fine. This narrows down the issue to SWAG specifically for me. Problem is that I can check my port 443 on home IP address and it works, and then 3 minutes later the connection is refused for another 2-3 minutes and then it's back up accepting connections again for the next 5 minutes and this pattern repeats. It alternates from connection succeeded to connection refused. I've seen nothing in the SWAG logs or Firewall logs for that matter, that is jumping out at me. I think my next step will be to delete the container and start from scratch. I had a failure on an ssd that config was stored on a few weeks ago and while every single other docker worked just fine when i restored data to it, perhaps something was missed. Any ideas?
  3. I'm trying to route the binhex-resilio-sync container back through binhex-privoxyvpn container and I can't get the webui to work. I've ensured that port 8888 is defined within the vpn container and it's still timing out. Is there something else I should be looking at?
  4. As an FYI, it looks like the developer has very early (Intel based) GPU support: https://github.com/jshridha/docker-blueiris/pull/40 It looks if you pull the "gpu" version, it may work. I'm not 100% sure how we might test without building two separate systems altogether, but may be worth the hassle.
  5. This is still an issue. Is there any way to bring it to someone else's attention that might be able to resolve? Not being able to use on iPad and phone is a pain when wanting to manage something very quickly.
  6. Hi all- I'm currently evaluating Unraid, about 9 days in so far, and have a few questions regarding permissions. I switched from Windows Server 2019 My migration plan was: Copy as much data as possible from 2 smaller drives to external drive using largest available (12TB) Build 2 drive array using 2 smaller drives mentioned above Used Krusader docker to copy from USB to 2 smaller drives Rinse and repeat for the other drives Shuck and pre-clear 12TB former external USB drive and add as parity So, using the above method, everything seems to be working just fine. I even converted my former Windows Server 2019 to a VM for future use, just amazing. My issue is that I'm noticing permissions at the file level seem to be varying. The folder/share permissions for ISOs is nobody:users while some of the files underneath are root:root. Is this correct? Do I need to do something to get the permissions correct across the board? My guess is this is a function of using Krusader to copy the files across AS the root user? Second, I setup an old 128GB SSD as an unassigned device and moved my docker and appdata over to it. Everything has started up fine and works as expected with two exceptions: 1. AutoStart (I use delays) does not always work for all the dockers; it seems random which ones start and which don't. 2. Fix Common Problems is complaining about some data being mounted on Unassigned Devices, but LinuxServer-based docker's do not have the option to change to SlaveRW like some other dockers, specifically for configs. Perhaps I'm missing it? If I need to split these questions in to different sub-forums, please let me know! Thanks in advance for all your feedback!
  7. Understood. My critical data has multiple backups both on-site and off-site, it's more of the various JBODs of entertainment media. It was split logically based on content type, but yeah, getting it pulled in to unraid with it's parity drive(s) would be a win for it.
  8. This is great news... thank you for the quick reply. This was my last obstacle before making the commitment to move. Now, I've just got to plan moving all my data across from Windows Server to Unraid with basically only one spare drive to do it!
  9. Not sure if this is the right forum, but I'm interested in moving to Unraid from Windows Server for a more stable platform. Right now I run WS2016 with Plex, Emby, Blue Iris and a few other items on the system. Blue Iris, Plex and Emby all "share" access to Intel IGP and thus quicksync, in other words, since it's Windows I don't have to dedicate usage to a specific application. Now, if I move to Unraid, will I be able to utilize quicksync on my I7-7700 across multiple docker containers? Will I be able to "share" it with both Plex and Emby to allow for hardware acceleration in both containers, possibly at the same time? I understand that I won't be able to pass the IGP to a VM and utilize it in a docker container, but I'm more interested in allowing it in multiple docker containers. I'm looking in to moving or at least review Shinobi in place of Blue Iris, so that would also likely utilize quicksync. Please move this topic to the proper forum if I posted in the wrong one.
  10. I was literally writing my response when I saw your post... but adding the bit to the "go" file did it! I finally played a test file in plex and saw the magical "transcoding (hw) to transcoding (hw)". The official response from ASRock is as I suspected: Yes, you can use Intel on-die GPU for transcoding. In BIOS – Advanced as you see, you just need to set Enable to Intel VGA Device Control and allocate your desired memory size to it. Now, does anyone know if it's possible to use both Emby and Plex at the same time? Well, not at the same time, but certain files playback better in Emby than Plex and vice versa, so my family often goes between the both of them. Thank YOU so much for doing the research. I was literally ready to throw in the towel completely after getting this new lower power system together. It looks like I will be moving forward with this build. I just now need to find a replacement for my security camera NVR, Blue Iris. I really don't want to spin up a VM just for it and am investigating other possible Linux / Docker based VMs, but none seem to be even remotely close to Blue Iris.
  11. I tried set memory to both 1GB and 2GB (neither had an effect) and then ran through the various Onboard vs. PCI Express and those seemed to have no effect either. The only one that seemed to matter was the Intel VGA Control option. I enabled that and it seemed to kickstart everything. I still can't quite get Plex and/or Emby transcoding to work yet, but I'm guessing seeing renderD128 means I'm getting close?
  12. Well, after playing with a few settings in the BIOS, I *THINK* I may have gotten it to show up in unraid: Linux 4.14.49-unRAID. Last login: Tue Jul 17 16:07:26 -0500 2018 on /dev/tty1. root@tower:~# cd /dev/dri root@tower:/dev/dri# ls -la total 0 drwxr-xr-x 3 root root 120 Jul 17 16:07 ./ drwxr-xr-x 16 root root 3560 Jul 17 16:07 ../ drwxr-xr-x 2 root root 100 Jul 17 16:07 by-path/ crw-rw---- 1 root video 226, 0 Jul 17 16:06 card0 crw-rw---- 1 root video 226, 1 Jul 17 16:07 card1 crw-rw---- 1 root video 226, 128 Jul 17 16:07 renderD128 This is the first time I've actually had it plugged in to a monitor and NOT had IPMI plugged in as well. Off to do more testing, but this is highly encouraging.
  13. So, this makes me believe that quicksync IS actually available which of course is all I care about. i'm sending yet another response back to them and looking for specific details on how to enable. after I questioned the Intel options in the BIOS, this is what I got back: Thank you for your patience! It is confirmed by our BIOS team that the integrated GPU by Intel’s CPU is for transcoding purpose only. It is not used for video output for this server board. Hope you understand. Thank you!
  14. Well, guess I’m going to have to hope AMEX will do a return guarantee as my CPU and motherboard purchase isn’t able to be refunded. The official response from ASRock: Thank you for reaching out to us for support! Please note that the JViewer remote video stream heavily and solely relies on the integrated GPU ASpeed AST2300. Video output processed by any other 3rd party GPU cannot be passed through to the BMC, thus it will not be streamed to the JViewer, the Console Redirection feature. JViewer capability will also be affected if a PCIe-based video card is installed because video output processed by PCIe video card will not be passed through to be used in JViewer (Console Redirection).
  15. I think I may and try to load Windows and see what it reports. If it’s truly not reporting the Intel graphics properly the. I just spent several hundred dollars for nothing. Also, once I hear back front Asrock I’ll report back here as well.