Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Flick

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. I knocked out /mnt/user/appdata/Plex/Library/Application Support/Plex Media Server/Media/ and that seems to work fine. Once in a blue moon I'll remove it, let the backup take everything, then store the backup elsewhere. That way if I do need to recover, I can pull that snapshot and then the latest as an "incremental" from there.
  2. Had the same issue and this solution resolved it. Thanks!
  3. After I upgraded to Unraid v6.4, I moved Pi-hole to its own IP. Since then, many ads are popping up a username/password prompt rather than failing silently or showing a Pi-hole page. Any suggestions? Thank you.
  4. Done, looks like all went well. Fingers crossed! Event: unRAID Parity sync / Data rebuildSubject: Notice [LIBRARY] - Parity sync / Data rebuild finished (0 errors)Description: Duration: 1 day, 5 hours, 52 seconds. Average speed: 57.5 MB/sImportance: normal
  5. Yup, I did and was ignoring it. Since you didn't quote, I assumed you'd gotten us mixed up as I was the last "non-support person" to post in the thread. No worries, mate, I appreciate you helping to keep the forums clean! Perfect, I'll give this a go this evening. Thank you!
  6. Yeah, I was afraid of that. Normally I'm pretty good at working through all the steps but I simply missed doing so this this time. I appreciate the feedback. I've never had to rebuild an existing disk; could you point me towards instructions to do so? I've only put in new disks in the past but, in this case, the drive has only been going for three months so I'd like to give it another shot. What would be ideal, actually, would be if I could put it into a different slot. That way, should it fail again, it points to disk rather than cables/connections. Thoughts? I did go in and clean all cables, reseat connections, etc. This has been a rock solid system for several years now. 1. Ah, I did not know that about the SMART kick off. TIL. Thanks! 2. Shouldn't be an issue, this has been a controller in play for many years with no issues. Thank you for the assistance. Love this community!
  7. Unraid v6.4. Attached are the diagnostics as requested, although I've already done a reboot since the error first popped up, I'm afraid. I shut down to check cables and connections. Thank you! library-diagnostics-20180122-0755.zip
  8. Any ideas? This is rather confusing to me, that it's offline in Unraid but passes the SMART extended self-test. Attached is the full report. Any help is appreciated! Thank you.BadDrive.zip
  9. Anyone figure out how to get alerts to go to Telegram? Thanks.
  10. Did you ever figure out how to do this? This is of interest to me as well. Thanks!
  11. To be clear, though, I'd still like the option for incrementals. Seven hours of downtime isn't ideal for a single backup. Thank you.
  12. Backup ran for 7 hours and 11 minutes. Verify and compression both turned off. TAR is 617GB in size. So, for doing a full backup, I am indeed impressed. I don't mind not having compression turned on but not having verify makes me a wee bit nervous. That would double the time, though, so I guess it's a trade-off. Now if I could just figure out why it insists on creating a new folder called "Backup" on my disk10 when it completes the backup job. Sigh. (My backups go to disk1\Backups). Thank you again for all your work on this.
  13. I second the request for incrementals. My cache drive is 676GB in total, with the bulk of that being: 476 GB in "/mnt/user/.appdata/Plex/Library/Application Support/Plex Media Server/Media/" 106 GB in "/mnt/user/.appdata/Plex/Library/Application Support/Plex Media Server/Metadata/" Sure, I could exclude those during my regularly scheduled backup, dropping my backup to only 94GB but, since I have the space, I'd rather keep them backed up so that if I do lose the cache drive, Plex won't have to download/transcode/whatever all of that again. That's over half my monthly data cap on data that's pretty consistent, hence the v1 plug-in approach of renaming the oldest and then just updating the diff worked really well. Still took several hours to run, though, making me nervous about how long this new method is going to take. I did indeed have cache drive failure earlier this year and your v1 plug-n saved my bacon! Unfortunately, though, it's now been throwing errors so each backup has "-error" at the end and I can't figure out the reason. I saw this thread about v2, figured I was one of the ones affected and went ahead and upgraded. First backup scheduled to run tomorrow night, so fingers crossed! Overall, though, to be clear - *thank you* for providing this plug-in! It's a life saver!