• Posts

  • Joined

  • Last visited

Everything posted by bigbadblo

  1. Looking for some troubleshooting suggestions or advice as to why one of my array drives is not being utilized / written on? Each of the disks on the array was set up in a similar fashion when I first put this together last spring. I went through and precleared all drives, did the suggested health checks, etc. before ramping up the system for regular use. Everything checked out to my knowledge/awareness. My Disk Settings's default partition format is set to MBR: 4k-aligned, file system is xfs . 8TB parity drive (GPT: 4k-aligned) 1TB disk1 (MBR: 4k-aligned) | 35% utilization 8TB disk2 (GPT: 4k-aligned) | 75% utilization 2TB disk3 (MBR: 4k-aligned) | 0% utilization 8TB disk4 (GPT: 4k-aligned) | 57% utilization Every disk has been utilized to some degree -- EXCEPT disk3 -- and I'm stumped. Does anyone have any ideas? Note: obviously those tiny 1 and 2TB drives will be the first ones replaced with larger 8TBs later... but for the time being, I'm super curious as to why this issue is happening.
  2. Just a quick thank you Djoss -- I'm loving the ease of setting up reverse proxies for all the ridiculous stuff I previously had port-forwarded through my router. Using a DDNS integration between my router directly (AsusWrt Merlin firmware) to Google Domains, once I had the awareness to generate CNAME entries for the services I wanted access to -- and pointing those CNAMEs back to the synthetic DNS address -- using this proxy manager worked flawlessly. Really impressed with the ease and simplicity of this setup - especially since it's allowed someone like myself with little to no understanding of the complexities involved in manually creating a reverse proxy into a simple 10 minute affair. Thank you very, very much!
  3. Very cool. Does this allow for the handling of subfolders by chance?
  4. Running into issues today with FCP -- my error log states that I'm experiencing connection time outs. The only thing I've changed to my system is installing a dockerized version of pihole in the past week. Could this be causing the error? Dec 21 14:28:47 Tower root: Fix Common Problems Version 2018.12.07 Dec 21 14:30:47 Tower nginx: 2018/12/21 14:30:47 [error] 13756#13756: *21253 upstream timed out (110: Connection timed out) while reading response header from upstream, client:, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "", referrer: "" Thanks for any insight.
  5. @Squid and @trurl -- thanks for the guidance. That was stunningly easy to recover from; deleting the docker image and reinstalling previous apps took all of about 10 minutes, and so far, everything seems to be ship-shape again. Much appreciate your assistance. Cheers!
  6. Thank you trurl. A couple questions: If I understand correctly, you mean that I should delete the entire docker image (which in turn will delete all dockers applications as well)? In doing so, all currently installed docker applications will then appear as previously installed in the Apps - Previous Apps section (somewhat obviously, in checking that area now I don't see any of my current applications listed)? Docker image settings are stored outside of the image / apps themselves, and won't require any configuration again? Finally, to your question re: the docker image size being 25GB -- when I first configured Docker in Unraid, I followed the video tutorial provided by SpaceInvader One on Youtube. In that, he adjusted the Docker image to 25GB, and I followed suit. Is there any issue / concern in my having done so? I have been doing my best to educate myself on Unraid and Docker specifically. Up to this week, I've had a resoundingly successful time installing and configuring docker applications, and so far hadn't run into any issues until these errors popped up this week. To clarify, I have been trying to roll my own docker application and install it (a bit of home-automation / Alexa-bridging-goodness) which failed to install correctly and I have since removed the Docker app... but perhaps it was the root cause? Thanks again for stepping in to provide some context and direction for how I can resolve these issues. Cheers.
  7. Hello. Running Unraid 6.5.3, I received the following error msg from the Fix Common Problems utility: "Unable to write to Docker Image - Docker Image either full or corrupted." When investigating the Docker setting tab, I see the following: Label: none uuid: 1ddda053-7119-48ab-adf3-c5f3956e966c Total devices 1 FS bytes used 6.27GiB devid 1 size 25.00GiB used 10.02GiB path /dev/loop2 I don't know if it's related, but in Fix Common Problems I also have a warning that my /var/logs are filling up (68% right now) and the system has only been up for less than a week. I've attached the diagnostic zip file. As someone new to Unraid (I muddle through with online walkthroughs, forum posts and videos predominantly) I'm a bit unclear as to what the root of the problem(s) might be here. Any help would be super appreciated. Thanks very much,