2twisty

TL;DR: "Open web gui" menu option does not link to the correct IP:Port, but can access by typing IP:port manually. Here's the example I'm using so someone might try to duplicate it: My Network info: 192.168.3.0/24 GW: 192.168.3.1, pfSense 2.4.4-RELEASE-p2 on actual separate hardware DCHP from pfSense, range 192.168.3.100-199 DNS from pfSense UnRAID 6.6.7 box @ 192.168.3.21 I have several containers using the standard bridge mode that maps ports from the host IP to the 172.16 private docker subnet. I want some of my containers to have unique IPs on my network. I added the OwnCloud container from Owncloud. I chose network Custom:br0 and set the static IP to 192.168.3.249. I left all the default options in the container. For reference, it SAYS that it will map port 8000 to 80. Then I complete the config and return to the docker menu, and it's running. The docker screen then says its listening on port 80, but the "open web gui" option tries to open on port 8000. The Open Web Gui choice results in a "connection refused" error. If I manually type the address using port 80, it loads the web gui as expected. If I go back into the container config and specify port 80, the "open web gui" option STILL tries to open port 8000. See attached image.....

I figured it out. Since my single was formatted XFS it was confused. So here is what I did, since there was nothing on my cache volume I wanted (I moved it all to the array before trying this) Stop the array. Find the offending drive and click its link. Change file system type from auto to btrfs (or btrfs-encrypted) and hit apply Start the array WHen it asks to format, do it. Poof. All good now. Now to move things back to the cache from the array.

I have searched on this and am not getting useful results. Other threads talk about changing the format type for the cache, but I can't seem to find where to change that setting. I have 4 drives in my main array and a single cache drive. I have a basic license key. When I try to add a second cache drive (brand new, unused), the new one says that its part of a cache pool, and the original one says that it cant be mounted. It wants to format the disk. I give it permission and it goes through the motions of formatting the disk, but them gives the same result. Am I running into a number of devices limit? I didn't think the flash drive counted as one of my 6 devices. If I go back to a single cache drive, all is well.

Is there a way from the UNRaid UI to force a complete re-download of all the FS layers?

I'm having issues with both the linuxserver Radarr docker AND the Sonarr docker. Both of them claim to be unable to reach my deluge docker. If I install binhex/Radarr, it can connect. But I don't want to reconfigure Radarr in Binhex. I'd like to repair the linuxserver versions if I can. Any ideas? This just started this morning with both clients -- no updates applied. It just plain broke. Here's my log file. Full of errors. radarr.txt

ooooookkkkkk.. It just started working all on its own. BIzarre.

Just did an update to the Docker container and now it will not load properly unless I disable PIA. I noticed the fact that the NL endpoint is no good for forwarding anymore, so I tried switching to Toronto. Still no dice. If I turn off the VPN in the docker config, Deluge loads and operates properly. Just to be sure, I reviewed SpaceInvader1's video and I have it all configured the way he suggests (except for using the Netherlands endpoint). Please advise. I'm stuck torrentless at the moment. NOt even sure what logs you might want to see.

Update: I think the culprit is Sonarr and Radarr. They just love to scan the array all the time, and there's no way (per the devs) to change the intervals at which is scans. So, I am testing the following: I wrote a user script that runs hourly that checks to see if its between the hours of 5pm and 9am. If it is, it runs a docker stop command to end both Sonarr and Radarr. Hopefully, this will allow the array to settle down long enough if there is no other activity to perform the shutdown. Since most of what my array does is serve video to Kodi and I've got wakeonlan configured, this may be a workable solution for me. Wish me luck!

Well....I'm back. It's not working again. And this time, reinstalling the plugin didn't work. I have the plugin set to wait for array inactivity and then shut down after 15 minutes. It never seems to shut down. Where should I look in the logs to find out why? When I log into the webUI, I see no activity on the drives for long periods, then a tiny little spike. I think that may be what's causing this, but I'd like to nail it down rather than keep guessing.

Since posting, I reinstalled the plugin and it seems to be working now. But to answer your question, I hadn't made any significant changes. If it acts up again, I'll come back and post again.

I am having trouble with S3 Sleep. It used to work just fine and recently just stopped shutting down. I've got it set to sleep after 5 minutes of array activity, with cache excluded no other options enabled. I don't know where I should look next. Before people ask why: I am off grid on solar and don't use the array that often, but often enough that manual shutdown and startup is a problem. I don't need the array to run all night eating my batteries. How can I track down where the failure is?

Nothing? Giving this a bump. I would figure this would be the place to ask this question. Lots of views, but no replies. Have I erred? I searched the forum, but didn't find very good tips. Saw people talking about GPU Bios, do I need to do something with that?

I am having trouble getting my GPU to work with my VM. VNC works fine, but I want to output the video to my TV. My Hardware: Asrock FM3A88Pro3+ (Radeon R7 graphics) AMD A8-7600 APU 16GB RAM 240GB SSD cache 4x 4TB WD Red for array Second GPU: Radeon HD 5450 in first PCIe x16 slot TV: Vizio E48u-D0 (4k TV, 48") I'd prefer to have a VM that runs Win7 (and therefore SeaBIOS), but am willing to settle (begrudgingly) for Win10 on OVMF. I have tried both OSes with both GPUs set as passthrough. I have had only marginal success. Only once when I was on Win7 on the APU did I get any output to the TV. Then, after a reboot, it failed to give me output again. When I am getting the "black screen," my TV shows "no signal," so it's not that the video card is sending a black image, but that it's not sending anything. I have used this TV on this exact same hardware before moving to UnRAID, so the hardware is compatible. Nothing seems to work. I plan to use this hardware for light gaming and retro gaming. Can you help me figure out what I'm doing wrong?

I am using Linux Mint. I open an xTerm and use the command line SSH app. The problem can't be in the terminal app I'm using since I don't get this behavior with any other *nix system I've connected to. Only unRAID.

This doesn't happen in any other *nix machines I use except for UnRAID. When in an SSH session and I reach the end of the line, instead of line-wrapping to the next line, it jumps forward, much like when you're using nano and cursor to the edge of a long line. I can't figure out how to change this behavior. I often will SSH into the machine to move large files around or do other tasks more easily done with the command line. Because of the file structure I use, I often have paths that are rather long (example: /mnt/user/Video/TV/Star\ Trek\ The\ Next\ Generation\Season\ 01/Star\ Trek\ TNG\ S01E01-Encounter\ at\ Farpoint\ Part\ 1.avi) Once I get past the "edge" of the terminal, the line jumps forward and I can't see what I've already typed (to check for errors) and I can't back up (with cursors or backspace) past the point of the "jump." Can anyone direct me to the setting that will make the terminal session behave like all my other *nix (OSX, Mint, Ubuntu, Raspbian) terminal sessions?