• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Cessquill

  1. 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.
  2. 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.
  3. 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).
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. Not a huge deal, but when a disk is replaced and the data on it is being rebuilt, the manual button to trigger the mover is disabled citing "Disabled -- Parity operation is running". That's fine. However, the scheduled mover still runs, and you can manually trigger a move from the settings, scheduler page. This may be by design (albeit with mixed messages), I'm guessing it doesn't just apply to this version, and it could also apply to parity checks. Nothing breaks, so it's obviously nowhere near a priority. Just thought I'd point it out as it's an inconsistency.
  9. The two posts above yours describe how to stop the container, and scan/repair the database.
  10. 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.
  11. 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.
  12. Try */15 6-23 * * * I had a similar expression that would run a drive spin up every evening
  13. 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.
  14. 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.
  15. 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?
  16. 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).
  17. 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).
  18. 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)
  19. 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.
  20. It's late here, but the instructions are dotted on the previous page
  21. Key: NVIDIA_VISIBLE_DEVICES Value: The ID of your GPU according to the Nvidia plugin page Default Value: leave blank
  22. I don't think you'll have problems. This only affected 1 or 2 of all the Ironwolf models, none of which you have.
  23. I haven't seen any evidence that the drives you're using are affected by the issues this thread addresses - maybe others know better. I haven't got any in my array, and out of the 17 Ironwolfs, only 4 had issues (the ST8000VN004). It's also not established (here at least) whether changing the lowCurrentSpinup is required.
  24. Cheers guys. Yes, other transcoding works fine - both with browser and Chromecast (although haven't tested exhaustively). And I'd added another pool with the intention of pulling all Plex activity off my Cache/regular docker pool. And moved it folder to folder (copy rather than move for safety). Used to have it on an unassigned device pre cache pools, and remembered access needed to be Slave Read/Write. Didn't know whether there were any similar requirements when running from an alternate location. Or whether I'd messed up permissions when copying over. Figured it was more of a Plex issue, but thought I'd try my luck here as support from Plex can be hit and miss. Thanks again.
  25. Hi - I've posted on the Plex forums, but it might be an Unraid/Docker issue - not sure. Last week I... Installed a 500GB SSD specifically for Plex as its own Pool Created a pool, named it "plex", added the drive, formatted it as XFS and put an appdata folder on it Moved my "plexmediaserver" folder from "mnt/cache/appdata" to "mnt/plex/appdata" using MC (copied and then archived the original once all files present) Repointed my plexmediaserver's config and transcode settings from "mnt/cache/appdata..." to "mnt/plex/appdata..." All works except for streaming live TV to the Chromecast. Fine in browser, but casting gives “Sorry! Something went wrong” and have the following in the logs (amongst other things)... Sep 19, 2021 08:57:35.272 [0x145bdb10fb38] ERROR - [Transcoder] [mpeg2video @ 0x15177d248600] Invalid frame dimensions 0x0. Appreciate that this looks like a Plex issue, but checking in here just in case I've done something wrong or somebody else has the same issue. Could also be a coincidence that Chromecast support broke at the same time.