• Posts

  • Joined

  • Last visited

  • Days Won


wgstarks last won the day on October 29 2022

wgstarks had the most liked content!


About wgstarks

  • Birthday 01/14/1959


  • Member Title
    Devolved Member


  • Gender
  • URL
  • Location
    North Carolina USA
  • Personal Text
    Fake quotes will ruin the internet ~ Ben Franklin

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

wgstarks's Achievements


Experienced (11/14)




Community Answers

  1. For me the error has only showed up on reboot in the console. Not in the system log. Started mover manually (didn't want to wait an hour) and see this in the system log- Feb 24 20:42:21 Brunnhilde emhttpd: shcmd (129): /usr/local/sbin/mover &> /dev/null & Feb 24 20:42:21 Brunnhilde root: Starting Mover Feb 24 20:42:21 Brunnhilde root: ionice -c 2 -n 0 nice -n 0 /usr/local/sbin/mover.old Seems to work properly. root@Brunnhilde:~# ls -l /usr/local/bin/mover -rwxr-xr-x 1 root root 161 Feb 24 20:28 /usr/local/bin/mover* root@Brunnhilde:~# # Generated mover schedule: 0 */1 * * * /usr/local/sbin/mover &> /dev/null Tried uninstall-reboot-reinstall. Didn't work. performed another reboot after the reinstall and still seeing the error.
  2. I’m also getting the same error.
  3. I've never had this issue with this docker but often with unraid I have to do a recovery reinstall of macOS after updates. Might be worth a try for you.
  4. Yes. It will correct empty paths for anyone who hasn’t updated to 6.12.8 and FCP will recommend it’s installation.
  5. It’s the same thing. Whatever you enter in settings will be stored in the config file.
  6. Would an FCP warning be possible? In my case I ran into this problem with the LSIO Plex docker. IIRC the template was originally setup with users adding their own paths for movies, tv shows etc but at some point LSIO added these paths to the template. Since I (and others) already had these paths as host path 2, host path 3 etc the newly added paths were never used and that worked just fine until 6.12.8. It was an easy fix after the update since someone else had already found the fix and posted it in that support thread but I think an FCP warning might help people who unknowingly have this problem prior to them updating to 6.12.8. Just a thought.
  7. Thanks for this. Exactly the same thing happened to me but I knew how to fix it because of this post.
  8. Macs will connect to networks in the order set in the network settings on the Mac. If wifi has priority over ethernet you can drag them into a different order. If Ethernet already has priority then this would suggest that your Mac is experiencing issues connecting to your network via Ethernet and is reverting to wifi instead. Possibly a bad cable or port.
  9. Did you also get the correct LAN network setting?
  10. Correct. If you have the schedule set at hourly and the percentage at 75% then once an hour the mover will check to see if the cache is above 75% and start moving if it is.
  11. Did you try the online calculator? Honestly I’m not sure this has anything to do with your error. Just a misconfigured setting. Have you also tried rebooting?
  12. I can see one error right off- This is not correct. https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Scroll down to Q4.
  13. You need to update unRAID to at least 6.12.0 to be able to continue to update CA. I would suggest updating to the latest stable unRAID version.
  14. You could try one of the other settings for version.