flyize

Members
  • Posts

    429
  • Joined

  • Last visited

  • Days Won

    1

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

Enthusiast (6/14)

75

Reputation

2

Community Answers

  1. I wish I knew the answer to that question as well. I have a similar issue with Chrome, but Firefox works fine.
  2. 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?
  3. 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.
  4. Any suggestions on if/how I can fix this? truffle-diagnostics-20240403-0902.zip
  5. 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.
  6. 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?
  7. So wait, is MAX_SIZE how much free space to keep on the disk? And then it adds older files until it hits that number? Sorry, I'm terrible with bash scripts.
  8. Well hopefully that's correct, cause I'm in the middle of the rebuild!
  9. Okay. So unassign the disks, mount the array. Then navigate through the emulated disks (via the Unraid GUI I guess?) and make sure I see data. Then reassign the disks and rebuild (in-place)?
  10. I went in an mounted /dev/sdk. It's actually emulating the whole device? If so, how will I know when I get it fixed? edit: Added diagnostics truffle-diagnostics-20240228-1458.zip
  11. Any reason I can't just bring them back online and pretend nothing happened (or maybe do a parity check)? edit: FWIW, if I look at the drives, all the data seems to be there.
  12. Thanks! Looks like those two drives are on the same molex to sata power splitter. If I order another one and things spin up, do I have to rebuild?