dRuEFFECT

this was very helpful and works for my use case, thanks!

Sounds like this can make Emby play the same content across multiple devices, is that right? I'd like to try, installed it with unraid, but no instructions on how to use once set up.. Any pointers?

this is the first i'm hearing of memtest86. my motherboard doesn't support ECC ram, so i'm limited to non-ECC. could that be a factor here? to me it just seems the raid1 cache drives were not balanced and just threw a ton of errors without a way for me to rebalance. i wound up swapping the older SSD with the other older SSD and let unraid rebalance, and i've been fine ever since so i guess this wasnt a filesystem corruption. i'm still not 100% sure what happened.

woops, ok. here it is. unraid-diagnostics-20220716-1447.zip

This is now the third time I have to backup, reformat, and restore my cache pool due to BTFRS filesystem issues. Logs attached. Any idea what's causing this? I thought it was a bad cables as I would have ECC error count on the SSDs move from 0 to 1 and back regularly, so I replaced my SATA cables. Then one in particular still kept throwing that error a lot so I bought a new SSD to replace it in the pool, but it's now my understanding that's just some kind of bug with MX500 SSDs and I'm still having this issue. I really like the idea of having SSD drive fault tolerance with a pool, so I really don't want to go to a single drive XFS. Plus my OCD kicks in when I see that exclamation point on the shares tab telling me my cache shares aren't protected. syslog.2

I posted here the other day thinking I got it working with nested folder mappings, but like can0n says, that doesn't work. I deleted my last post since i was completely wrong. but I'm happy to say that i believe i actually got it working with symbolic links, specifically relative symbolic links, AND i needed to map the path of the symbolic link destination to the docker as well. so like lotetreemedia said, copy/move the directories, create RELATIVE symbolic links (-rs not -s), and add a new mapped path to the destination. when plex is inside the docker and sees the symbolic link, it tries to follow that path. so a standard symbolic link won't work because the /mnt/user/newshare directory doesnt exist within the context of the docker, you need to also map that share to a location within the docker. maybe you could do a standard symlink too and just map the full host path to be the same in the container path, but whatever i used a relative symlink and just mapped the share to the container's root. i got it to work on all 3 folders, Cache, Media, and Metadata stop the docker, move the folders, and create the links cd /mnt/user/appdata/plex/config/Library/'Application Support'/'Plex Media Server' mv Cache /mnt/user/metadata/Plex-Cache mv Media /mnt/user/metadata/Plex-Media mv Metadata /mnt/user/metadata/Plex-Metadata ln -rs /mnt/user/metadata/Plex-Cache Cache ln -rs /mnt/user/metadata/Plex-Media Media ln -rs /mnt/user/metadata/Plex-Metadata Metadata now your folders are linked like this then add a mapped path to the new metadata share and BOOM, bobs your uncle

Woop Woop! Thank you!

not sure how i got stuck with my email address as my username here on the forum, but this isn't ideal and i can't seem to change it. can an admin update my username to: dRuEFFECT please and thank you

edit: i re-ran it and yea it appears to skip existing files pretty quickly btrfs restore ran for a while but hit a not enough memory error.. not sure what to do next would re-running skip over what's already restored?

roger that. thanks for your help. i almost had an anxiety attack

for my new cache pool, would it make sense to run a single drive primary cache and schedule rsync on the entire drive to a secondary SSD pool, this way both drives are XFS, both drives have independent filesystems, and i could stop the array and hot swap the backup cache in case of failure. is this plausible or am i missing something?

THANK YOU!!! btrfs restore is doing the trick for me

Attachedandrews-unraid-diagnostics-20220228-1258.zip

I have 2 500gb crucial ssd's mirrored in a raid 1 cache pool. I keep everything updated, on the latest 6.9.2. Everything was swimming along nicely until this morning when I updated Fix Common Problems, then went to CA and showed me that docker was disabled. I check things out and see that my cache drive is in read only mode, and one of the 2 SSDs was showing BTRFS errors to trigger this. I was confused why I would have any issues, if one drive had a problem, wouldn't the second be able to keep things afloat? So I tried stopping the array, this way i can add a spare SSD to pool devices and copy the cache drive contents, then possibly drop BTRFS for XFS and run a single cache drive with scheduled backups. Stopping the array was getting hung up on unmounting the cache drive. i tried manually unmounting, but no joy. So I rebooted into safe mode and now both SSDs are showing as unmountable with no file system. For the love of god, please tell me there's a way to recover the cache drive contents. I've been running a mirrored cache pool solely for the peace of mind that i have redundancy, how could this be happening? What can i do?