loyalsnoopdoge

@JorgeB Hi there, Thanks for your help. I gave up on the USB drives in the NUC. I returned it and built a new system in the Fractal Design Define 7 XL. I got an LSI 9400 16i and some SAS to SATA breakout cables for my drives. Everything works great!

UPDATE: Looks like the DB is corrupted, but it's odd this has happened multiple times on multiple separate computers with multiple different Docker containers. any ideas what could be causing this? My Plex app data lives on Cache only. I have 2 980 Pro's in BTRFS in RAID1

I’m having a really infuriating issue with my PMS. I just moved over to unRAID with Docker and rebuilt my entire server from scratch multiple times. I have tried Binhex Plex, the official PMS docker, and am now using LinuxServers. This issue has now happened on every single one of them It will work fine for a couple of days and then it will always revert to the same behavior. First, any newly added media will not be detected, and then I completely lose the ability to edit any of my libraries. I cannot modify the folders for the library, the agent, or any of the metadata for any of my library items. I can’t even delete the specific libraries to read them. To me it’s really odd how it will work flawlessly and then randomly decide to cut out I have read all of the other threads about this and none of the suggestions work. I cannot keep rebuilding my entire library and Docker container every few days to remedy this. I need to reliably know that my media will show up when it is added and that I can modify the libraries. If anyone has any insight I would really appreciate it! Plex Media Server Logs_2023-07-31_21-00-19.zip

Hello @phea. Where did you get those SATA power cable extensions? those look amazing but I havent been able to find them anywhere on Amazon or Newegg. The ones I got are way too long in between the connectors

@JorgeB I'm trying a different enclosure, Thunderbolt this time but a similar but slightly different issue is happening this time Could you please look over my log file for this and let me know what you think the issue is? unicornbarfnuc-diagnostics-20230722-1852.zip

So this to you looks like a problem with either my USB cable or my enclosure. For right now I'm locked into doing this over USB, although I could change that in the future What about drivers? How do I go about updating the drivers on unRAID? What about settings in the BIOS on my NUC? are there any settings I could / should change? One other thing that is really weird is that I never get any disk errors when I am scanning / analyzing my Plex library. it only happens during parity sync. It also doesn't happen during read checks

Hello, I’m new to unRAID as of a week ago. I had been running Plex on my gaming PC, but switched over to an Intel NUC with unRAID to take advantage of Docker and ease of use for multiple disks. My Plex media was originally stored on the Seagate drive which used to live inside my gaming PC. My disk setup is as follows: 1x 16TB Seagate Iron Wolf Pro (age 6 months) PARITY 2x 16TB WD Red Pro (age 1 week) STORAGE These drives are in a 5 bay Sabrent USB C enclosure My cache setup is as follows: 2x 2TB Samsung 980 Pro in RAID1 These drives are directly attached to the motherboard Now on to the main issue: I copied my Plex library into my drives and have set up my Docker containers. However when I initiate my parity check it returns with a ton of errors. After it returns the errors, the parity check stops and changes to a read check. Then it tells me that my parity drive is disabled and I am unable to manually initiate another parity sync, it only shows read check. To attempt to remedy this I have tried the unRAID dance where I shut down the array, remove the parity drive, start the array, stop the array, re add the parity drive, and start again. However one of two things will happen when I do this. Either the parity check will start again and return a ton of errors and disable the drives again, or it will flat out just not see my drives at all until I restart unRAID again. I’ve also tried formatting the parity drive before re adding it to the array. I’m also having an issue where sometimes when I try to stop the array it takes a very long time to stop and sometimes it doesn’t stop at all until I reboot. I have attached diagnostics and am hoping someone can tell me how to resolve these errors and what is going wrong. Do I need to nuke my array and start over? I find it very improbable that all 3 drives are damaged, since the Seagate is a known working drive and the WD Red’s are brand new. diagnostics-20230720-0910.zip