Cessquill

I just did it as per the Plex instructions and had no problems - signed out of all clients. Signed back in locally, went to general settings, clicked Claim Server and it set itself up. Didn't need to curl or change files. It was a bit slow, but it got there. Remote access is fine, etc. From what I understand, I think the Plex servers have been over-run with people resetting their credentials. Therefore, I *suspect* that most of these solutions would work under normal circumstances, and they may have worked for you guys now because their servers have calmed down some.

Hi - came to my machine this morning and could not get to the web interface (constantly loading). Could get to network shares and dockers appeared to be working (with the exception of Plex). I could putty onto the server and ran a diagnostics (attached), but when I tried a reboot it looked like it was working (The system is going down for reboot NOW!), but nothing happened. Tried an orderly shutdown using Supermicro IPMI, but no dice, had to fully power cycle. My server is normally pretty stable (if not a little full), and goes for months without rebooting. I had recently started to get something periodically maxing the CPU for a couple of minutes that I was trying to locate, so over the weekend I'd uninstalled the File Integrity plugin and rebooted. Backups normally take place on a Monday night, but are typically completed by the morning (and the dockers were running). Any ideas?

It only takes a couple of minutes, can be done on existing drives while running <6.9 and on new drives while they're formatting. The instructions are only long to walk through every step - it's really pretty straight forward. Heck, if you're on 6.8.x, go through the steps anyhow - you won't break anything. You're good to upgrade then when you want. As I understand it, It's more of a Seagate/Linux issue. Whilst I'd love to test 6.10, I don't have spare hardware.

As I understand it, this issue causes the drives to drop off when they spin down/up whilst the array is running. If you're losing drives on a machine restart, I suspect that may be a different issue.

Are you sure the drives are set correctly? And they are dropping offline during normal running of Unraid (ie, not during a reboot)? I have 8 of the models in my array, and all have been stable since applying these settings to all of them. I occasionally get a drive drop off during a reboot, but I think that's because I'm pushing my PSU too hard (need to cut down on drives)

I would guess entering a value in the "Delete backups if they are this many days old" field that's more than your frequency. So, if you run weekly, then entering - say - 8 would keep two backups. 15 should keep 3. Haven't tried it though, but I'm guessing that's what would happen.

It is likely trying NPM, but it is failing to start as one of the other dockers it wants is not yet running. I used to have a docker (Jitsi I think), and NPM would not start unless Jitsi was running. I forget which configurations make the starting of NPM depend on something else, but I'd check there. I'm guessing in your case the docker it wants running sometimes starts in time, sometimes doesn't. When you go back and start NPM manually, it will always work, as all other dockers are running by that point. Check the logs of NPM. If that doesn't show you anything, turn off a docker in turn and restart NPM. I haven't played around with docker start orders in Unraid, but it might be possible to start NPM last (I'm not sure whether this plugin observes Unraid's start orders, or whether there are other options that would fix this). It might not be this, but I had the same behavior a while ago.

Thanks - I'll check that out, but these are mainly split level situations (e.g. extra files in a TV series where I've set it so each show should not split, or upgrading an existing movie from DVD to Blu-Ray).

Whilst I may have plenty of free space, it's very common for mover to fail on some files due to full destination disk. I regularly check logs and cache, but if I forget then files can go unprotected for a while. For users less familiar or hands-on with Unraid, this could leave files unprotected for a long time, and cache drives filling up. A convenient feature would be Unraid optionally notifying me of any failures it encounters. Bonus points for detailed errors, but I'd be happy with just knowing. Then I can either free up space on a drive, or move a folder to an emptier one.

From the first post... Possible fix to get it back going again... On your Unraid flash drive, go to \config\plugins\user.scripts\scripts Rename the folder in question that applies to your script Inside that folder, edit the "name" file to repair the title Refresh the User Scripts page in your browser Or, just delete that folder and start again.

Give 0 */6 * * * a go. Might not give you a definite start hour, but might help identify the issue. I have custom schedules working, but I've never quite worked out which rules of cron apply.

Still working for me - just sent a test mail from Ombi. I'll describe what I have, but if it's what everybody else does then apologies (maybe I'm lucky)... End of last year set up an "App Password" in Gmail - https://myaccount.google.com/apppasswords Created one for Mail with a custom name of Unraid and used it for all dockers that want to send mail. The password it gives you can replace the regular password you've currently got and all should work. I can't remember what the password is or whether I logged it anywhere for re-use. That's not a problem though, since you can just create a new one.

The two posts above yours describe how to stop the container, and scan/repair the database.

Very useful, yes - thank you. If I had a USB SATA dock, or benchtop test PC I'd probably do that. My Unraid drives are in hot swap caddies though, so it's easier for me to do it in Linux. However, think I've changed 4/5 drives since writing this, and have had to refer back to this thread every time for the commands.

Just by tweaking the post above yours, this will get close: */5 7-12 * * 7 It should run every 5 minutes on a Sunday from 7-12, not 7.30. I'm not personally aware of any way to put fractions in to hour ranges (somebody else might know), but if it has to be from 7.30 onwards then you could tweak your script by putting a quick bit of logic at the start. Something like startTime="07:30" begin=$(date --date=$startTime +%s) now=$(date +%s) if [ "$now" -le "$begin" ]; then exit 1 fi ...would exit the script straight away for all times between 7 and 7.30. Haven't tested it though - just patched it from a script that I used to run before I realised custom schedules were a thing.

Try */15 6-23 * * * I had a similar expression that would run a drive spin up every evening

When I was looking into it, I seem to remember that the other use was if more than two people were in a chat - it was no longer peer-to-peer, so relied on a third party to manage the feeds (also the turn server could be resource intensive). I gave up in the end, but will probably pick it back up again over a wet weekend.

Just to say that it worked fine for me. However, I did have to restore from backup about a month ago when moving my appdata to a different cache pool and movie list was empty. Maybe I got lucky.

some www/ files hidden over network - might be a general Unraid thing, but we'll see... I'm developing a site in appdata/nginx/www from a windows box, and occasionally files and folders that I can see on Unraid are not visible through smb. EG, /appdata/nginx/www/assets/internal/js/scripts.js is not visible over the network, but another js file in that folder is. If I try and recreate the file from Windows, I get a message saying it already exists, but I can't see it to open and edit it. Any ideas?

Just the opposite of the instructions to implement it. That is, remove "--runtime=nvidia" from Extra Parameters and blank the "Nvidia Visible Devices" field in the docker template. You could then uninstall the Nvidia Driver plugin (not sure whether required, but if you're removing the card you might as well).

I can't see the rest of your settings, but you haven't filled in the "extra parameters" on that screenshot (instructions at the top when you edit the docker).

You could try "Refresh All Metadata" and maybe "analyze" across each of your library entries (just a guess, but it might help flush out issues like this)

Turn off downloads for any friends/family might be worth looking at. AFAIK you can't remove downloads that somebody else has set up, and if their client doesn't log on and download it, it will constantly get converted and sit there waiting.

It's late here, but the instructions are dotted on the previous page