dmrichards26

Interesting… doing the same thing did NOT resolve the issue for me, even after a reboot.

Tried digging for an existing thread on this, but couldn’t find anything. Ever since iOS 18, my Files app has been connecting to my unRAID shares as read-only. I found an Apple forums thread about this issue where other users have been successful in resolving this issue by editing their smb.conf files to include streams_xattr. I tried enabling enhanced macOS interoperability in unRAID, but no success. Then I added… [global] vfs objects = streams_xattr … to my Samba extra configuration, but still no dice. Has anyone else encountered this and figured out how to fix it on unRAID? I imagine this is a common issue.

Out of curiosity, is there a general availability release of the patched drivers yet? Or still beta only?

@JorgeB- That worked perfectly, thank you so much! I'm not sure who maintains the docs, but it would be great to update them to reflect these issues with 6.12+

I'm currently working on shrinking my array, and have been following the instructions in the docs (here) and also shown on Youtube here. I got to the point of running the clear script, and unfortunately ran into the same issue as this user (wherein the script is not compatible with 6.12+, but the docs have not yet been updated to indicate that). I then tried to stop the array, so I could re-start it in maintenance mode and follow the instructions shared by this user. Unfortunately, the array will not stop, because the clear drive script was run improperly (and created /dev/md2, in addition to /dev/md2p1). It's stuck on "Retry unmounting disk share(s)" Does anyone have advice on how I should proceed? Any help would certainly be appreciated!

@Djoss I did make sure to start with a fresh appdata directory, knowing that would likely cause issues. After taking a quick peak at engine_output, and seeing hundreds of the following error: Error occurred during initialization of VM Initial heap size set to a larger value than the maximum heap size I realized that the error was with my configuration of the "Maximum Memory" setting. I entered 4096, forgetting to add "M". It appears leaving out the unit caused this error. Changing to 4096M (or 4G) solved the problem. Thanks for helping me realize the issue. Cheers!

@Djoss - I've tried a couple of restarts, but with no luck. Find the log attached. Thanks for the help. CP Log.txt

@Djoss - To my knowledge, yes. I installed via the community applications "Apps" tab, and have since checked for updates through the "Docker" tab.

Just spun up this container after uninstalling gfjardim's home container and migrating over to CP for SB. I had a couple hiccups with ports at first (the same issues as @meoge), but uninstalling/reinstalling seemed to have fixed that. Unfortunately, I am now getting the error message "Code42 cannot connect to it's background service". I tried a couple of restarts, but no luck. Any ideas?

Awesome, thanks man.

Alright, someone explain what I'm missing here. Totally new to Docker, and can't figure out for the life of me how to add the PlexPy docker to my unraid setup (already running Plex as a container). I can't even figure out the first step (I'm assuming that I add another link to my docker repo list on http://tower.local/Docker but I truthfully don't know. My typically good google-fu is failing me here. And it doesn't help I don't know a lick of Linux. Anyone generous enough to help? Cheers!