lupine_legend

Thanks for taking a look. My hardware is due for an upgrade (beefing up the tower with new CPU/mobo/RAM) as this NAS was built way back in 2009 when it was only running unRAID. That said, things have been running fine (albeit slowly) with the two dockers for at least a year. Also, I tried updating the unRAID Server OS plugin in maintenance mode without the dockers running and it still didn't work. Not sure if that rules out a RAM issue? I'll keep rooting around for the problem, but I guess I should upgrade sooner rather than later.

Hi All, I was trying to update my unRAID Server OS plugin but was getting a File I/O Error after the download was completed. I suspect this has something to do with another thing that Fix Common Problems is telling me - Rootfs is getting full. The only dockers I'm using are sabnzbd and Sonarr and I think they're both set up correctly, i.e. not using any folders outside of /mnt. Any other ideas for what's taking up my /tmp space or how I can clear it? Thanks! tower-diagnostics-20170117-0720.zip

Ha, goes to show you what I know. I check it again when I get home now that everything seems to be running well again.

I ran the check again with -L and then the server was able to start up and mount disks correctly. I guess something was corrupt on the Cache drive?

I started the server in Maintenance Mode and checked the filesystem status of the Cache drive with -nv. The results are attached. It ran the check really fast. I feel like it should have taken longer. I'm not sure how to make sense of the output as it doesn't call out any obvious errors (to my untrained eyes). xfs_repair_status.txt

When I got home yesterday, my Tower was frozen either from a power surge or something else. I gave it a hard reboot since it was non-responsive from the GUI. Now, it's hitting an error when it tries to mount the disks and just hangs forever. I was watching the Log the last time I tried to start up the server (attached) but here's the interesting part: Oct 25 07:21:54 Tower kernel: XFS (sde1): Internal error XFS_WANT_CORRUPTED_GOTO at line 1627 of file fs/xfs/libxfs/xfs_alloc.c. Caller xfs_free_extent+0xbe/0xf1 Oct 25 07:21:54 Tower kernel: CPU: 0 PID: 4308 Comm: mount Not tainted 4.1.18-unRAID #1 Oct 25 07:21:54 Tower kernel: XFS (sde1): Failed to recover EFIs Oct 25 07:21:54 Tower kernel: XFS (sde1): log mount finish failed I'm completely out of my depth. What do I do now? Thanks so much for any help. Log.txt

I tried telling Sonarr to set permissions to 0777 per this post (http://lime-technology.com/forum/index.php?topic=50908.msg501545#msg501545) that I just found, so hopefully that resolves the issue.

Hi all, I've started having strange permissions issues that I don't know how to resolve. I've got a Sonarr Docker that moves new files to their proper place on my array. Newly downloaded files cannot be opened from Plex/VLC/Windows Explorer, but when I run the New Permissions tool everything works as it should. I've never experienced this before and I'm not sure why the permissions on new files are being screwed up. All my Shares have their security settings set to Public. Any ideas? Logs attached. Thank you! tower-diagnostics-20161022-1221.zip

Thanks for the feedback. I nuked my docker.img again, re-added the apps, then I went over the FAQ again and fixed the configurations. Here's what they look like now: Both apps are running again. I'm not sure what was making them hang before, but hopefully it was my wonky configuration as you pointed out. I'll report back in a few hours once they've had some time to run and hit whatever snag was happening before.

Since yesterday, the issue spread to Sonarr too. Here are screenshots showing all the settings: On the Docker tab, both apps look like they're running. However, when I try to go to the WebUI, I get "Site can't be reached" errors. This is the same issue I was having before I deleted my docker.img and started over. Not sure what's causing this.

I got both Docker containers reinstalled using CA after a few attempts. Configuring them now. Last time, they crashed after configuration so we'll see how this goes. UPDATE Sonarr seems to be working fine, but Sabnzbd is acting up. I can't get to the WebUI at all - "Site can't be reached" errors. The Docker page says it's running and uninstalling/reinstalling it don't seem to help.

Working on it. I deleted the docker image and created a new one. The first time I tried to reinstall Sabnzbd using CA Previous Apps, I got this error: Second time I tried, I got this error: Both times the command failed. Then I tried to install Sonarr the same way: Then I got the same error about not connecting to the Docker daemon. I'll keep trying - standby.

Here's a screenshot: Flash 2% // Log 2% // Docker 17%

After a power outage a few days ago, I noticed that my Sonarr Docker app had stopped working. The dashboard showed that it was running, but I couldn't access the app. I restarted it but then it wouldn't start back up again. Convinced my Docker image was corrupted or something, I deleted it and created a new image. Once that was done, I re-added the containers for Sonarr and Sabnzbd. Almost as soon as I finished configuring them, the same issue recurred. This time, both apps will not start. My full diagnostics are attached, but this seems to be the interesting bit from my syslog (to my untrained eye): Does anybody know what the heck is going on? Thanks so much for any help! tower-diagnostics-20160829-1751.zip

Hi all, I hope I'm posting in the right area. I'm running unRaid 4.7. I set up my server a couple of years ago and haven't had any problems until now when I noticed that my files aren't being moved to the right drives. I have two 2TB drives and a number of user shares. User shares are set up as follows: TV (parent) > TV > Series > Season Movies (parent) > Movies> Movie Title TV is set to Split Level 3 and Movies is set to Split Level 2 and both have Min. Free Space set. Each user share was set to high-water allocation and I just noticed that Disk1 is full while Disk2 is empty. I panicked and changed the allocation method to Most-Free. To test the changes, I downloaded an episode of a TV show to see which disk it was allocated to. I expected it to be sent to Disk 2, since it has the most free space, but it was still allocated to Disk 1. I've been reading the manual over and over and I can't seem to figure out where I'm going wrong. Is it an issue with the Split Level? Allocation Method? I'm completely lost. Thank you!