dRuEFFECT

Members
  • Posts

    21
  • Joined

  • Last visited

Recent Profile Visitors

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

dRuEFFECT's Achievements

Noob

Noob (1/14)

1

Reputation

  1. this was very helpful and works for my use case, thanks!
  2. 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?
  3. nevermind, looks like the raid1 btrfs file system corrupted as is read only YET AGAIN. i hate this shit, this is like the 5th time now. what's the point of raid 1 backup when the whole filesystem gets corrupted so frequently
  4. Since updating to 6.11 I have been unable to update most docker containers. Some containers are orphaned and trying to remove them manually I get a vague "Server Error". When trying to update a single container or update all containers, the output shows that the removal of the existing image fails, and can't create the new image because an image with that name already exists. I'm stuck with some permanently orphaned images, and some dockers that fail to start with "Server Error" i have docker directory enabled and tried scrubbing the filesystem but it just shows status: aborted screenshots and diagnostics attached unraid-diagnostics-20221006-1626.zip
  5. 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.
  6. woops, ok. here it is. unraid-diagnostics-20220716-1447.zip
  7. 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
  8. 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
  9. 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
  10. 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?
  11. 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?