codearoni

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About codearoni

  • Rank
    Newbie
  • Birthday February 27

Converted

  • Gender
    Male
  1. My appdata directory (user share) is configured to use my cache drive. But they're moved to disk during my nightly mover job. This is a pretty common configuration, as I understand it.
  2. Getting back to you. I think I see the same bug: 1. I updated my Docker container and created a new path for /serverdata/serverfiles, to ensure a "fresh" install. 2. However, after my mover job runs at 03:40, it seems to stop the backups from being generated. Here's a pic of my /Backups/ directory today. The /Backups/ directory is not on my cache drive at all. So these 9 files are the only backups I have for my image. This matches what I saw in my previous image, and they seems to strangely line up with my mover job.
  3. Thanks! Updated and will get back to you on how backups work over the coming day(s). I just logged in though, and my save wiped on update (i.e. my world is gone). Is this a known issue?
  4. I have a question about backups for my Valheim image. Currently I'm using the defaults (interval = 62, backups to keep = 24). For context, my container has been up for approx 3 days. I would expect 24 tar.gz files to be in my /Backups/ directory, however I only see 9. Additionally, the modified dates on the containers range from 2-20 (19:19) to 2-21 (03:35). I have my mover scheduled for 03:40 daily, so I would expect the latest tar.gz file to have a modified date of approx 3:00-ish this morning (2-23). Am I missing something / misunderstanding how the backu
  5. If you haven't already, I'd install the community applications plugin. On there, search for the jlesage makemkv plugin. It seems to be the most poopular MakeMKV solution right now. Link: https://old.reddit.com/r/unRAID/comments/dek25r/best_makemkv_docker_container/f30i8kf/ I myself am looking for a similar solution at the moment. Hopefully this will give you a direction to go in. Cheers
  6. Couldn't you write a launchd script that runs every night at 2am, etc? One that simply rsync's your photo folder to a share on your unraid nas?
  7. Thanks to everyone for the help on this issue! I've updated my OP with my triage steps. Hopefully it'll help future WD Red users in the future. I've got my array back online. The rebuild process was incredibly easy. Hardest part of this whole thing was waiting on the RMA drive. It's only strengthened the idea that Unraid was the right choice for my NAS.
  8. Everything has been updating swimmingly, just taking a while given the drives I got (14 hours each). I had a question about extended SMART tests though: can I run them while the array is up and running? Will things like mover jobs be interrupted by extended SMART tests if I run them at night?
  9. From the Disk's personal page: go to the section labeled "Self-Test" and click the "Download SMART report" button. If you've done a short SELF test, then yes, the same button.
  10. Also, traditionally it helps to attach general diagnostics in additional to the SMART results. Tools -> Diagnostics -> Download.
  11. Hey! Another WD Red user! See my thread from a couple of weeks ago. The extended SMART results mean different things for different brands of drives. I'll let someone more knowledgeable than me confirm, but your drive might need replacement.
  12. No worries trurl, I imagine you're managing thousands of threads on this board lol. I've begun a rebuild but it'll take 12 hours. Probably tomorrow I'll pop on and update the OP with a summary of steps taken for these particular drives (WD Red Plus).
  13. Right on, ty itimpi! So as a general rule of thumbs: adding multiple data drives at once = fine. Adding data + parity drives = not (do them as separate tasks). Makes sense. I'm just a new user and don't want to make any assumptions as to how unraid operates.
  14. Thanks trurl. Just to be clear: I'll be moving from 1x Parity and 3x Data drives to 2x Parity and 4x Data drives. Sounds like adding a 2nd parity will require a rebuild on Parity #1...so I might be better off doing #1, just adding the replacement data disk and rebuilding the array. Then afterwards, spinning down the array, and adding Parity #2 and Data #4?
  15. Thanks trurl. Looks good now. I was making it more complicated than it needed to be. (i.e. "Attribute = 0" trying to match the checkboxes below). Final question: I'll be rebuilding the array soon. I am adding a 2nd parity drive and one more storage drive. Should I: 1) spin up the array with the replacement disk ONLY, and rebuild FIRST - followed by spinning down the array, and adding the new drives. or 2) spin up the array with the replacement disk, plus the new drives, and rebuild all together. Couldn't find any documentation on this particular scenario in the wiki.