Coogan2007

I apologize in advance if this has been covered ad nauseam here already but I'm not even sure what to search for, much less how to fix it. Please point me in the right direction if this has already been addressed. I had an issue that left me with no alternative but to kill the power to my unRAID server. The issue wasn't with the server itself, just an ongoing network problem that I'm still trying to figure out. This isn't the first or second or third time this happened, but it is the first where the server had a critical issue. When I powered the system back on the first thing I did was to check my Docker containers, but there weren't any there. I verified that the docker.img file is present and started searching but a few threads mentioned deleting this file and I didn't want to touch anything, especially since the parity check was still going. The parity check completed and on the main page it said all the disks in my cache were unmountable. I searched for this and found THIS guide on Data Recovery, which lead to the page on Storage Management. I followed those directions up until the Repairing the File System steps because I didn't want to go any further without another set of eyes taking a look. Here's what I got when I checked the file system in Maintenance mode: [1/7] checking root items [2/7] checking extents [3/7] checking free space tree free space info recorded 1338 extents, counted 1351 wanted bytes 319488, found 258048 for off 50643865600 cache appears valid but isn't 50563383296 [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sdc1 UUID: 9c7b3ee3-4edf-4543-a216-62f203b71a1b found 143473057792 bytes used, error(s) found total csum bytes: 26882928 total tree bytes: 288391168 total fs tree bytes: 159842304 total extent tree bytes: 87572480 btree space waste bytes: 52782186 file data blocks allocated: 214446366720 referenced 135832350720 Several of these containers took literal weeks to configure (not the templates themselves, the actual apps) so I'm trying to avoid having to start over from scratch if possible. If not possible, well, that sucks but OK, but I'd also like to know how/if I can fully back up the containers to save all the app data. What's the outlook and how should I proceed?

I've suddenly started to get this error whenever I try to download anything. I've tried restarting the container and trying different videos but it keeps failing. Any ideas? Error while retrieving info on video with URL https://www.youtube.com/watch?v=HPH0HgotIE4 with the following message: Error: Command failed with exit code 1: node_modules/youtube-dl/bin/youtube-dl -o audio/%(title)s.%(ext)s --write-info-json --audio-quality 0 -x --audio-format mp3 --write-thumbnail --no-clean-info-json -j --no-simulate --dump-json http://www.youtube.com/watch?v=HPH0HgotIE4 Traceback (most recent call last): File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main return _run_code(code, main_globals, None, File "/usr/lib/python3.8/runpy.py", line 87, in _run_code exec(code, run_globals) File "node_modules/youtube-dl/bin/youtube-dl/__main__.py", line 14, in <module> File "<frozen zipimport>", line 259, in load_module File "node_modules/youtube-dl/bin/youtube-dl/yt_dlp/__init__.py", line 4, in <module> ImportError: You are using an unsupported version of Python. Only Python versions 3.9 and above are supported by yt-dlp

Sorry for asking, but how exactly did you do this? And where are the country IDs found? Edit: nm, did some googling on the NordVPN API and managed to splice together a QUERY string to get me going.

I did not; I thought it was automatic when the container started. But I just found it in the hardware presets. Thanks! Edit: jeez, just started a x265 encode and it's 20x faster, and the CPU load is down by about a third.

How can I find out if QSV is being used? The activity log says it's detected but my h264->h265 (using MKV 1080p30 preset) encodes are still hitting around 5-7fps and the 2 CPUs I've got enabled for it are roaring along at 99%. Just wanted to make sure this is normal.

OK, I was able to add the ports and get those going, and set a variable to put the transmission directory actually on the disk (although I still can't see where the ovpn file should be put), but now there's another problem: I'm getting "Permission denied" when trying to download a torrent and write it to the the disk. QBittorrent and Deluge have downloaded the exact same file to the exact same directory with no problems, yet Transmission can't do it even after I changed the share setting to Public. So I'm officially at a loss as to what the heck is going on.

I'm having a lot of trouble getting this to work properly. I can't get port 51413 to open, and there's nothing in the configuration to set it. And second, there's no config directory being created; I've searched the entire array and cache pool and there's not a single reference to the container anywhere. It's like the entire thing is being run in RAM or something. Because of this I can't upload my NordVPN ovpn file that I prefer to use instead of the default one the container auto-selects for me. I've tried both DelugeVPN and QBittorrentVPN containers and they're working just fine, but I'd prefer to use Transmission because I'm much more familiar with it and want to use the remote client instead of the web interfaces.

I'm hoping someone can help me with this, because I'm lost. I've tried a ton of different guides, watched the video, and been troubleshooting this problem for 4 days now. I simply cannot open the sabnzbd webUI. I posted some details and my docker configs here. I really need some help before I start pulling out what little hair I have left. EDIT: Nevermind, I finally got it working. EDIT 2: And now it's not working again. Sonarr and SABnzbd are working, but I've downloaded both Deluge and Transmission containers and both are having the same problem. I'm flummoxed and perplexed, and getting really cheesed off at the insanity of this. Some help would be GREATLY appreciated, guys.

Just reposting a request for help I put on the unRAID subreddit; haven't gotten much so I'm hoping someone can help me figure this out and I don't have a $700 paperweight. === I know this has been discussed 1000 times already. I've googled, read at least a half-dozen guides and how-to's, watched SpaceInvaderOne's video, and done everything I can think of to fix this. Nothing has worked. I'm sure I'm just overlooking something but can't figure out what it is. I've tried this one, this one, this one, as well as this and this. I'm at an absolute loss as to what the problem is. I've got the binhex sabnzbd container working so it can access the VPN via the NordVPN container. But I cannot get the sabnzbd web ui to come up. Here's the NordVPN and sabnzbd container configurations. I've been banging my head on this for 4 days now and gotten nowhere. === I've attached my NordVPN and Sabnzbd container settings. I do have the LAN Net set to my local LAN /24 (it's not shown in the image). I cannot access the Sabnzbd UI via the IP/Port at all. And the guides I've followed are from all over the place, but so far nothing has worked. I'm stumped, flummoxed, whatever you want to call it.

I'm having an issue that is confusing me greatly. I just set up unRAID this weekend and PiHole was the first thing I installed on it. I set the Network Type to "Custom (br0)", set the Fixed IP address to the LAN IP I wanted it on, and also set the Server IP to the same. If I connect to the IP from a remote system on my home LAN, it connects up just fine. However, if I try to connect to it from the host system (the unRAID server), I can't connect to it. If I open a terminal in unRAID and ping the PiHole IP, it times out (I can ping the gateway, tho). For the life of me I can't figure out what's going on, unless it's some wonky way unRAID handles internal routing between containers. It's not a show-stopper but it would be good to know what's going on and how to fix it in case I run into similar issues later on. Also, at some point in my fiddling around with it, I can no longer resolve pi.hole. The first time I set it up it worked, but not anymore.