Negatron

If we upgrade to this new version, will all of our existing requests still be there? Or do those all get lost?

I am still having the same issue as well. I updated the container, and even with a fresh config the Requests tab is not displaying any of the requests.

I just updated this morning, and now I am unable to see any requests when I log in as the admin. As a test, I removed my appData directory for Ombi completely and let it replace with a new set of config files. After setting it up again, I made some requests and sure enough, nothing appears under the Requests tab. If I search for something that I requested, I can see that it was requested. It just won't show anything under the Requests tab. Anyone else experiencing this problem?

NM. I searched and found the answer. I think I am back in business. I started in the array in Maintenance mode and went into the settings for Disk1 and ran a file system scan and then repair. Afterwards, I was able to delete that directory, and the five files that were missing appeared in a directory called "lost+found". I am feeling so much better right now. Can someone confirm for me if using xfs_repair in the GUI in maintenance mode maintains parity? Do I need to rebuild parity? I would assume that if it didn't, there would be a strongly worded warning about it...

I hope someone can assist me with this problem. Note that I am NOT very good with Linux, but I am fairly technical overall. I am very comfortable using Putty to SSH into my system and move around, using MC, and other basic stuff. If you don't care about the entire E! True Hollywood back story, skip ahead to the quoted section. I am a dum-dum and didn't bother to properly power my 4x Norco SS-550 5-in-3 units. I am not 100% sure that that's what started the problem, but I would bet on it. I was running great with 2 parity disks and 8 data disks for a while, then I added a 9th data disk. After a few days, I had a disk drop out of the array as I was trying to shut the array down to restart the system. I didn't think anything of it and re-enabled the disk and brought the array back online and it started a rebuild. About halfway into the rebuild of the disk, it dropped out again. I assumed the disk was failing and though, "no biggie, I've got two parity disks protecting my ass." I disabled the disk and ran the array degraded, down one disk. I immediately ordered a replacement disk (8 TB WD RED) and had it delivered same day (go Amazon!). So then, COCKILY, I started writing new files to the array thinking it was no big deal. Almost immediately, party disk 2 dropped out of the array and parity 1 started reporting read errors! I noticed that the activity lights on the parity disks were off, but the file kept writing to the array and I saw disk 9 with its activity light on. I immediately cancelled the file copy and then panicked. I should point out that all three disks (the failed disk 1 and both parity disks) were installed in the same 5-in-3. I would say this was likely a power issue. Anywuts, I assumed that I was going to lose a small amount of data on disk 1 since it was running in an emulated state, a file was being written to disk 9, and neither parity disk was functioning. Sure enough, I did some testing and found that a bunch of TV episode files were missing in one season folder (routinely save off directory and file listings on all disks just in case something like this ever happened). After some playing around, I discovered that I could not write to that directory, or even delete it. The directory existed only on disk 1 BTW. I was able to move it and even rename it, but I cannot delete it. It keeps reappearing. I realize I may have some other files corrupted, but I will worry about all that later. It seems that the overwhelming amount of 7+ TB of movies and TV episodes are fine. So I redid the power cabling to the Norco units so that there are no cables being split, and disks are evenly distributed across all four units. I also have a new PSU being delivered tomorrow (going from 550W to 750W). I received the replacement disk last night (even though the original failed disk 1 may actually be okay...that's also to be determined) and installed it to replace disk 1 and let the rebuild run all night and most of today (no, I did not do a preclear on it...I just wanted to get my data back on a data disk!). It ran with parity 1 active and parity 2 still out of the array (I even pulled it from my system temporarily so it didn't draw power). I was nervous all day wondering if it would complete and if I would lose all that data (in case the failed disk 1 that I pulled really is damaged). Thankfully it finished (20 hours!), and I am almost back in business. I am now protected with one parity disk. So now I need to know how to fix the corruption issue. My syslog.txt is reporting it over and over, and I have at least that one directory that I cannot delete. I don't know how to check or fix file system corruption. Can I do it without invalidating the parity disk? I'm assuming that I need to log into my box and run some commands. I just don't want to mess this up anymore than I already have. Thanks for any help and sorry for writing so much. I tried to describe exactly what sequence of events led me here in case it matters. The bottom line is that I have corruption on my newly rebuilt disk 1. unraid-diagnostics-20160829-2015.zip

I figured out why I couldn't connect to the web interface. I missed the advanced section in the docker settings. I had to change the LAN IP setting to match mine. Is there any way to get autodl-irssi installed? What about changing the version? Is that something that would require a separate docker for each version? I'm hoping to replace my Windows torrent machine (uTorrent 2.2.1) with an rTorrent docker, but I think I might have one or two trackers that are picky with rTorrent and don't allow the newest version. EIther way, I really appreciate the effort to provide this docker. I gave up long ago trying to set up a Linux box with rTorrent and fail-safe VPN.

I just installed this docker, and it appears to be running. However, I cannot access the GUI. The default URL (http://<server ip>:9080) just brings up an error page stating that the site can't be reached. I've been trying to figure this out, but I can't find anything in the documentation. Is there something that I need to change in a setting file such as rtorrent.rc? Do I need to set up a VPN before I can access the GUI, even from within my local network? I really hope to get this working because I really like rTorrent, but I am not very Linux savvy. By the way, can I set up common plug-ins with this? I am particularly interested in autodl-irssi. Also, is this specific to a particular version of rTorrent, or can the version be changed? Thanks.