Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


flyize last won the day on July 27 2022

flyize had the most liked content!

Recent Profile Visitors

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

flyize's Achievements


Enthusiast (6/14)




Community Answers

  1. What have I done to get here and how can I fix it? edit: Looks like I needed to run a repair on one of the drives.
  2. Just wanted to come back and say thank you for this. It's working perfectly!
  3. This was a self inflicted error. I was connected to the wrong wifi network. UGH
  4. Hmmm, I just saw this email from 5 hours ago. According to Unraid Connect, all my containers are stopped (which isn't true because Plex is working). * **disk3 (ST8000DM004-2CX188_WCT0EE4D) has read errors**
  5. So I'm having a weird problem. I can't access the UI for any of my Docker containers or Unraid itself. I also can't ping the server. However, Plex is fully working and Unraid Connect shows the server as online. What in the heck am I missing here?
  6. Actually, not sure what I've done, but the mover now moves everything off.
  7. I finally got around to adding this. I used this version. I have 1.3TB on my 'cache_media' drive and set the script MAX_SIZE at 1000000000000 (1TB). Right now its at 600GB used. It made a list of files to ignore, and has then started moving files anyway. What am I missing here? edit: Oops, I think it was self inflicted. I see that by default using the Move Now button does not use the Mover Tuning settings.
  8. I wish I knew the answer to that question as well. I have a similar issue with Chrome, but Firefox works fine.
  9. Someday, I'd love to not have to bother you guys, and maybe be able to help. Where do I go to see that those CRC errors in the diagnostics?
  10. You're an angel! That's wonderful news, as I'm about to be travelling for a week and didn't want this thing to die while I was gone! I'll get the cable swapped out. Yeah, the OOM errors are annoying. It just started happening with the latest version of Frigate. I've notified the devs, but its pretty much just me with the problem. For some reason, ffmpeg likes to occasionally try to grab 80GB+ of RAM. It was bringing down the whole server before I limited the RAM available to the container.
  11. Any suggestions on if/how I can fix this? truffle-diagnostics-20240403-0902.zip
  12. Just so that I can keep track of all my scripts in one place, can I use User Scripts? It puts scripts in /boot/config/plugins/user.scripts/scripts/. I'd still call if from the Mover Tuner, but at least all my scripts are in one place then.
  13. So in your example, if it gets over 750GB, the script will make a list of files from newest to oldest. Then remove the oldest file from the list and recalculate total space used, and do this over and over until it gets under 750GB. Then pass all this off to the Mover, with a list of files it can't touch. Am I understanding correctly?
  • Create New...