MaximusFSU

Yep. Works perfectly when stopping the docker from the dashboard.

Hey there, I recently upgraded to unraid 6.12.4 and ever since I upgraded to app backup from the older deprecated version, it crashes itself and the plex docker when it tries to back up. All other dockers seem unaffected, since it completes fine when I skip plex. Ran a test this morning to grab fresh logs. Cancelled after it had hung for a couple hours. debug log: 288826d3-020b-4e8c-9806-d0a448f14be1 [15.12.2023 09:57:28][ℹ️][Plex-Media-Server] Stopping Plex-Media-Server... Error while stopping container! Code: Server error - trying 'docker stop' method [15.12.2023 09:58:41][❌][Plex-Media-Server] docker stop variant was unsuccessful as well! Docker said: [15.12.2023 09:58:41][ℹ️][Plex-Media-Server] Should NOT backup external volumes, sanitizing them... [15.12.2023 09:58:41][ℹ️][Plex-Media-Server] Calculated volumes to back up: /mnt/user/appdata/Plex-Media-Server [15.12.2023 09:58:41][ℹ️][Plex-Media-Server] Backing up Plex-Media-Server... [15.12.2023 11:46:27][❌][Plex-Media-Server] tar creation failed! Tar said: [15.12.2023 11:46:27][⚠️][Main] Backup cancelled! Executing final things. You will be left behind with the current state! [15.12.2023 11:46:27][ℹ️][Main] DONE! Thanks for using this plugin and have a safe day

Hello you beautiful geniuses. Hopefully this is an easy solve. Since I updated to 6.12.4 and the latest Plex version, I've been waking up to the docker being stopped. Not sure if this might have something to do with the migration to new appbackup/restore... that maybe it's not properly restarting the docker after it's nightly backup... or maybe plex is having some crash due to scheduled tasks. Normally I would do more troubleshooting myself, but since it takes a full day to test every thesis, I thought I'd see if you all saw anything in the logs that could give me head start and save a ton of time. Thanks so much in advance!! Diagnostics attached below. normandy-diagnostics-20231212-0759.zip

Hey guys. I'm using a i5 13500/unraid 6.12.4 and am on the official pms/plex docker (v 1.32.8.7639). Apparently the plex team shit in their own hands and smeared it all over the walls recently... and by that I mean, they broke hardware transcoding in ways that even they have failed to easily explain without going through a series of crazy technical support threads. Apparently only tonemapping via hw transcoding was affected but my GPU is still spiking 90% plus with one 4k transcode and downloads cause a crash... all withwith tonemapping turned off. I used to be able do download shows super quick and support multiple 4k transcodes... So who knows how bad they borked things. But I digress... Here's my question. Is there anyone out there that's solved this issue by rolling back to a previous version? And if so, could you kindly walk me through how I'd go about that? I've never rolled back a plex version since I've been on unraid. Thanks in advance for any help. Normally I'd spend hours googling before posting a thread, but I have to get on a plane tonight and am trying to load the kids ipads up with stuff for the flight. So I'm kinda under the gun. Thanks again!

Thanks! Just looking into this now. Looks like this program is focused on phone photo syncing. Do you have it send the photos from your phone to the server? Or from your computer to your server? Just trying to see if it's right for me since I already use iCloud photos and am looking for an extra layer of redundancy.

Hey gang! I'm still relatively new 'round here. Had an unraid server up and running strong for about a year now. Love it. Love the community. Y'all rock. Quick question that I couldn't find an answer for in my forum searches. I already back my household macs up via time machine to my array, but is it possible to separately back up my apple photo library but as a traditional folder heirarchy. Say... by year. Mostly I just worry about my apple photo library getting corrupted somehow and not having a traditional folder heirarchy fallback in case the vague and proprietary apple version goes kaput. I hope that makes sense. Thanks for any tips or advice in advance!

Hey there. Ran a correcting parity check which finished in a normal amount of time but those 3 errors are still there. New diagnostics attached. Any help or guidance on next steps / best practices is appreciated. normandy-diagnostics-20230921-2102.zip

Thanks Jorge. Can't recall any unclean shutdowns. Will do and report back. You rock!

Ah... It is possible that the problem is that I'm an idiot. I may have set it up that way early on in my setup and forgot about it. So I guess the "6 days" is a bit misleading then. it's really only been running for 6 hours per day. So in reality it's only been really conducting the parity check for about a day and a half or so (~36 hrs)? So it's not really taking longer than it should. But the 3 errors should still be concerning, yes?

Hey all. Built my first unraid server about 3 months ago using a mix of some new, and some older (4 years) drives. Been LOVING it so far. First parity check after I transferred everything went off without a hitch. Took a day or two I think. After that I set it up to run parity checks every 3 months. But just yesterday I home from a vacation to THIS... The errors were concerning enough, but the time also seemed VERY long for a single 16TB parity drive. Note: I did not pause it myself... but I have since resumed the operation and it's showing this now: I've been searching for troubleshooting best practices for long parity checks / errors and have only been finding a lot of specific use cases. And not any standardized "start here, then check this..." type of best practices. So I'm coming to all of you brilliant geniuses for help. Clearly something is wrong, and I want to sort it before it becomes a bigger problem. Logs attached. Let me know if you need any other info. Server is mostly used for Plex, the arrs, time machine backup for 3 macs, light nextcloud use, and a Blue Iris camera server, running in a Win 10 VM (on cache drive) writing video files to an unassigned surveillance drive. Thanks in advance!! normandy-diagnostics-20230911-1029.zip

Ah. Gotcha. Thanks you again for the help. You def. saved me a chunk of my saturday! 👍

Yes! Thank you so much. That did it. I really appreciate it. Chalk it up to me being stupid and not realizing xfs couldn't do raid. I'll look into the procedure for changing my cache drive to btrs before I try that again.

Hey guys. Relative noob here. I'd been happily running my server for a month or so with 1 nvme cache drive formatted xfs. I was lead to believe that I could just add a 2nd nvme for redundancy by shutting down, adding drive, assigning the new nvme to a 2nd slot in cache pool and restarting the array... things did not go as planned. Now the cache pool seems to think it's in btfs and says "unmountable no pool uuid" and is basically unusable. fwiw, I do have my cache drive backed up to the array w/ ca-backup and restore. Thank you all so much in advance for your help. One of the main reasons I built an unraid server is how much everyone raves about the community. <3 normandy-diagnostics-20230513-0923.zip