snowmangoh

Guys, I have had this issue for a minute now where it's failing to create folders. It just started out of nowhere... I didn't change any permissions, or anything. Has anyone else experienced this?

Holy crap... I've only looked at that page a few times trying to find other things. Thanks! I have about 1400 audiobooks, lol

How do I delete my database and start fresh? I did the force rescan, but it's saying it missing all of the stuff I moved around.

After reading that discussion, I feel everyone's pain (because I just did the work), but I believe the way you have it now just makes sense... It will also make grabbing future things and automating the organization WAY simpler... Everything has an author/s, but not everything has a series. The kind of fuzzy logic needed just to organize that way doesn't make sense if you're trying to automate... Only now am I realizing how much mental work deciding how to organize and name files in the past was.

I might just cry with joy... That is freaking amazing. I'll go check that discussion out. Now I'm going to go reorganize all of my ebooks in the hopeful expectation you continue to be awesome. Thanks!!

So here's a question... Let's say I use the recommended file structure (which I have spent the last 8 hours reorganizing to😆), but have a series that is composed by different authors (the first 11 Wheel of Time books for example were written by Robert Jordan, but Brandon Sanderson wrote the final 3 books after Jordan's death.) If I have that series under different authors, but the Series name is identical between the two, will they show up in the same series in the app? If so, that would be an awesome solution to the conundrums I typically have with naming conventions anyway! That would solve some other issues I run into with other media types (thinking comic story-arcs) as well.

Well... I've been lurking and watching and simply not wanting to go through changing file structure and the hassle of figuring out what else is watching my books and should be turned off... But this is just looking too sweet! 😆 I'm about to load this bad-boy up and get started!

This is great info, thank you! I found it searching to see if using the flash creator tool I could use a larger flash drive size... Including that info on the https://wiki.unraid.net/Manual/Changing_The_Flash_Device page might be useful to anyone who has the same question. Thanks!!

So when I click on "Apps" I get this massage pop up: On the dashboard, the flash drive looks utilized: but when I click on it to view, it appears empty: I'm scared to turn off my machine to look at the flash drive. What should I do first?

Ah! I get it now... since I am not "rebuilding" the parity, but copying it from the old one, the data will persist... Thanks for kicking my brain... Thanks!!

I saw that but thought it wouldn't work for my situation... Would the emulation of disk 4 remain through the process preventing data loss?

I have an array of five 3TB (very full) data disks. I was just about to order two 8TB drives to upgrade the parity and one of the data disks. Disk 4 is busted and currently being emulated. Am I going to have to order a 3TB drive to recover to before I upgrade the parity and data disk?

Did anyone look at my diagnostics? I'm super frustrated I can't get everything up. Sent from my LG-H900 using Tapatalk

Hey guys/gals, So I've had an issue for the last week or so where upon starting the array, Unraid seems to load up to a certain point in the log, but then it hangs. I can reach the server via PuTTY, so I can restart, make config changes, and then try again, but it always hangs up SOMEWHERE. For a while the log was stopping at "Tower ntpd[1577]: new interface(s) found: waking up resolver", so I disabled NTP (just killing the process from the cli didn't progress things anyway.) I had also just installed a new docker, so I disabled them too (they weren't coming up anyway.) Now it hangs somewhere else. I'm attaching my diagnostics as a starting point... just let me know how I can help you help me! Thanks! tower-diagnostics-20161201-1544.zip

Did this ever resolve for you? My issue is similar. I can connect to the apps that started, but my dockers never start, and when I hang up the log just says, "ntpd[1577]: new interface(s) found: waking up resolver" and never moves past that... everything was working fine, and then this started randomly happening!

Okay... Thanks! I looked at the plexrequests settings and I see where you went wrong. The wording is unclear so it is easy to misinterpret. In the settings where it says "Couch Potato sub-directory" they don't mean where cp files are located. What they mean is the url prefix. Some people set a url prefix so that instead of accessing the cp interface at 192.168.X.X , they access it at 192.168.X.X/cp in that case the "sub-directory" (url prefix) would be "/cp" (that is used for reverse proxy). If you access cp at just the ip address and port, then leave that field blank. No need to map cp locations Well damn, lol... Thanks! Sent from my LG-H900 using Tapatalk

Okay... Thanks!

So if no one has any input on my issue from the previous page, should I just try another docker and see if that works?

So I don't use a lot of dockers, but I got it installed and running. I pointed it to the address for my Sonarr and CP, added my api, and everything said "Success!" when I tested. Then I went to add the directories and realized I had to set up the mapping so I set that up in the dockers's settings. After I did that and everything was running again, I added the directories in my settings and hit the test button and I got "Error". If I remove the directories and test, it still says it is successful. Add them back, and I get an error. Can anyone suggest what I might be doing wrong? Thanks! COMMANDS: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker rm -f PlexRequests PlexRequests The command finished successfully! root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="PlexRequests" --net="bridge" -e BRANCH="master" -e TZ="America/Chicago" -p 3000:3000/tcp -v "/mnt/cache/apps/plexrequests/config":"/config":rw -v "/mnt/cache/apps/couchpotato/":"/couch":rw -v "/mnt/cache/apps/Sonarr/":"/sonarr":rw -v "/mnt/user/TV/":"/tv":rw aptalca/docker-plexrequests 0a0517dd9085eabd9d1cd9af6250d43f10f1075ac2f33700a6fd15226c922413 The command finished successfully! LOGS: <--------------------------------------> <--------------------------------------> Starting container on Thu Sep 1 10:20:19 CDT 2016 Updating repository HEAD is now at 984e05c Add logging for updating download status Already up-to-date. Selecting the desired branch Using the master branch Your branch is up-to-date with 'origin/master'. Fixing permissions Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting <--------------------------------------> <--------------------------------------> Starting container on Thu Sep 1 10:20:19 CDT 2016 Updating repository HEAD is now at 984e05c Add logging for updating download status Already up-to-date. Selecting the desired branch Using the master branch Your branch is up-to-date with 'origin/master'. Fixing permissions Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting Changes to your project's package version selections from updating the release: accounts-base upgraded from 1.2.2 to 1.2.10 accounts-password upgraded from 1.1.4 to 1.3.0 allow-deny added, version 1.0.5 autoupdate upgraded from 1.2.4 to 1.2.8 babel-compiler* upgraded from 5.8.24_1 to 6.9.1 babel-runtime upgraded from 0.1.4 to 0.1.11 base64 upgraded from 1.0.4 to 1.0.9 binary-heap upgraded from 1.0.4 to 1.0.9 blaze upgraded from 2.1.3 to 2.1.8 blaze-html-templates upgraded from 1.0.1 to 1.0.4 blaze-tools upgraded from 1.0.4 to 1.0.9 boilerplate-generator upgraded from 1.0.4 to 1.0.9 caching-compiler upgraded from 1.0.0 to 1.0.4 caching-html-compiler upgraded from 1.0.2 to 1.0.6 callback-hook upgraded from 1.0.4 to 1.0.9 check upgraded from 1.1.0 to 1.2.3 ddp upgraded from 1.2.2 to 1.2.5 ddp-client upgraded from 1.2.1 to 1.2.5 ddp-common upgraded from 1.2.2 to 1.2.5 ddp-rate-limiter upgraded from 1.0.0 to 1.0.5 ddp-server upgraded from 1.2.2 to 1.2.6 deps upgraded from 1.0.9 to 1.0.12 diff-sequence upgraded from 1.0.1 to 1.0.6 ecmascript upgraded from 0.1.6 to 0.5.8 ecmascript-runtime upgraded from 0.2.6 to 0.3.14 ejson upgraded from 1.0.7 to 1.0.12 email upgraded from 1.0.8 to 1.1.16 fastclick upgraded from 1.0.7 to 1.0.11 geojson-utils upgraded from 1.0.4 to 1.0.9 hot-code-push upgraded from 1.0.0 to 1.0.4 html-tools upgraded from 1.0.5 to 1.0.10 htmljs upgraded from 1.0.5 to 1.0.10 http upgraded from 1.1.1 to 1.2.9 id-map upgraded from 1.0.4 to 1.0.8 jquery upgraded from 1.11.4 to 1.11.9 launch-screen upgraded from 1.0.4 to 1.0.11 livedata upgraded from 1.0.15 to 1.0.18 localstorage upgraded from 1.0.5 to 1.0.11 logging upgraded from 1.0.8 to 1.1.15 meteor upgraded from 1.1.10 to 1.2.17 meteor-base upgraded from 1.0.1 to 1.0.4 minifier-css added, version 1.1.13 minifier-js added, version 1.1.13 minifiers removed from your project minimongo upgraded from 1.0.10 to 1.0.17 mobile-experience upgraded from 1.0.1 to 1.0.4 mobile-status-bar upgraded from 1.0.6 to 1.0.12 modules added, version 0.7.6 modules-runtime added, version 0.7.6 mongo upgraded from 1.1.3 to 1.1.12 mongo-id upgraded from 1.0.1 to 1.0.5 npm-bcrypt upgraded from 0.7.8_2 to 0.9.0 npm-mongo upgraded from 1.4.39_1 to 1.5.48 observe-sequence upgraded from 1.0.7 to 1.0.12 ordered-dict upgraded from 1.0.4 to 1.0.8 promise upgraded from 0.5.1 to 0.8.4 random upgraded from 1.0.5 to 1.0.10 rate-limit upgraded from 1.0.0 to 1.0.5 reactive-dict upgraded from 1.1.3 to 1.1.8 reactive-var upgraded from 1.0.6 to 1.0.10 reload upgraded from 1.1.4 to 1.1.10 retry upgraded from 1.0.4 to 1.0.7 routepolicy upgraded from 1.0.6 to 1.0.11 service-configuration upgraded from 1.0.5 to 1.0.10 session upgraded from 1.1.1 to 1.1.6 sha upgraded from 1.0.4 to 1.0.8 spacebars upgraded from 1.0.7 to 1.0.12 spacebars-compiler upgraded from 1.0.7 to 1.0.12 srp upgraded from 1.0.4 to 1.0.9 standard-minifier-css added, version 1.0.8 standard-minifier-js added, version 1.0.8 standard-minifiers upgraded from 1.0.2 to 1.0.6 templating upgraded from 1.1.5 to 1.1.9 templating-tools upgraded from 1.0.0 to 1.0.4 tracker upgraded from 1.0.9 to 1.1.0 ui upgraded from 1.0.8 to 1.0.11 underscore upgraded from 1.0.4 to 1.0.9 url upgraded from 1.0.5 to 1.0.10 webapp upgraded from 1.2.3 to 1.3.11 webapp-hashing upgraded from 1.0.5 to 1.0.9 * These packages have been updated to new versions that are not backwards compatible. plexrequests-meteor: updated to Meteor 1.4.1.1. Changes to your project's package version selections from updating package versions: accounts-base upgraded from 1.2.10 to 1.2.11 alanning:roles upgraded from 1.2.14 to 1.2.15 aldeed:autoform upgraded from 5.7.1 to 5.8.1 aldeed:collection2 upgraded from 2.5.0 to 2.10.0 aldeed:collection2-core added, version 1.2.0 aldeed:schema-deny added, version 1.1.0 aldeed:schema-index added, version 1.1.0 aldeed:simple-schema upgraded from 1.3.3 to 1.5.3 aslagle:reactive-table upgraded from 0.8.18 to 0.8.34 autoupdate upgraded from 1.2.8 to 1.2.11 caching-compiler upgraded from 1.0.4 to 1.1.7 coffeescript upgraded from 1.0.11 to 1.0.17 ddp-client upgraded from 1.2.5 to 1.2.9 ddp-common upgraded from 1.2.5 to 1.2.6 ddp-server upgraded from 1.2.6 to 1.2.10 email upgraded from 1.1.16 to 1.1.17 fastclick upgraded from 1.0.11 to 1.0.12 fortawesome:fontawesome upgraded from 4.4.0 to 4.5.0 fourseven:scss upgraded from 3.4.1 to 3.9.0 iron:router upgraded from 1.0.12 to 1.0.13 launch-screen upgraded from 1.0.11 to 1.0.12 less upgraded from 2.5.1 to 2.5.7 mdg:validation-error added, version 0.2.0 minifier-css upgraded from 1.1.13 to 1.2.14 minifier-js upgraded from 1.1.13 to 1.2.14 momentjs:moment upgraded from 2.10.6 to 2.14.4 npm-bcrypt upgraded from 0.9.0 to 0.9.1 npm-mongo upgraded from 1.5.48 to 1.5.49 percolate:synced-cron upgraded from 1.3.0 to 1.3.2 raix:eventemitter added, version 0.1.3 retry upgraded from 1.0.7 to 1.0.8 shell-server added, version 0.2.1 softwarerero:accounts-t9n upgraded from 1.1.6 to 1.3.4 standard-minifier-css upgraded from 1.0.8 to 1.2.0 standard-minifier-js upgraded from 1.0.8 to 1.2.0 standard-minifiers removed from your project templating upgraded from 1.1.9 to 1.1.14 themeteorchef:bert upgraded from 2.1.0 to 2.1.1 useraccounts:bootstrap upgraded from 1.12.4 to 1.14.2 useraccounts:core upgraded from 1.12.4 to 1.14.2 The following top-level dependencies were not updated to the very latest version available: * ongoworks:security 1.3.0 (2.0.1 is available) * twbs:bootstrap 4.0.0-alpha (4.0.0-alpha2 is available) Newer versions of the following indirect dependencies are available: * autoupdate 1.2.11 (1.3.11 is available) * coffeescript 1.0.17 (1.2.4_1 is available) * ddp-client 1.2.9 (1.3.1 is available) * ddp-server 1.2.10 (1.3.10 is available) * less 2.5.7 (2.7.5 is available) * mdg:validation-error 0.2.0 (0.5.1 is available) * templating 1.1.14 (1.2.14 is available) To update one or more of these packages, pass their names to `meteor update`, or just run `meteor update --all-packages`. Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Sep 1 10:25:21 0a0517dd9085 syslog-ng[491]: syslog-ng starting up; version='3.5.3' [[[[[ /config/plexrequests-meteor ]]]]] => Started proxy. => Started MongoDB. [34mW20160901-10:25:39.775(-5)? (STDERR) [39m[35mNote: you are using a pure-JavaScript implementation of bcrypt.[39m [34mW20160901-10:25:39.807(-5)? (STDERR) [39m[35mWhile this implementation will work correctly, it is known to be[39m [34mW20160901-10:25:39.807(-5)? (STDERR) [39m[35mapproximately three times slower than the native implementation.[39m [34mW20160901-10:25:39.807(-5)? (STDERR) [39m[35mIn order to use the native implementation instead, run[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35m[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35m meteor npm install --save bcrypt[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35m[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35min the root directory of your application.[39m [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection tv [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection movies [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection settings [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection permissions => Started your app. => App running at: http://localhost:3000/

Sigh... too much clicking... don't know how I wound up in this thread. Thanks! EDIT: Deleted my posts and moved them to the proper thread.

Hey Phaze! You ever consider doing a Plex Request plugin? I don't know if it's possible even, but I hate dockers. Thanks!

I'll see if I can compile 3.10 or whatever the latest one is, but I'm not available to work on that probably for a few days still. Thanks brother!! Appreciate all you do!

Hey Phaze, I poster on the Sonarr forums that Archer didn't update to include the new season, and Markus said "Upgrade mono, 3.10 or higher is required (3.8 has some ugly bugs)."... No idea what that means, but in my Sonarr it says that mono is 3.8.0. Is that something that is included in your plugin? Thanks for alll the hard work you do!! Thanks! Here is my post on Sonarr: https://forums.sonarr.tv/t/new-season-of-archer-doesnt-show-up-in-sonarr/10481/1

While you're looking at new plugins, is a PlayOn plugin something you might consider too? That would round out all of my cable cutting solutions being on my unraid box!

I'm having a weird issue when I try to start up Plex now. The settings page says "Installed Version: (Failed to detect version)", and when I click on Update Plugin I get "Cannot write: no space left on Device." at the bottom of the screen once it starts trying to rite the Python stuff. There is PLENTY of room where it is trying to write. Could it be a permissions thing? The only update I made since everything was working was to install the Deluge plugin from http://lime-technology.com/forum/index.php?topic=32457.0.