Die_piggy

Hi everyone! My plex container seems to have borked itself since last night. Looks like an update occured last night, however installing a pervious version doesnt seem to fix it. This is the logs from starting the docker 2024-12-18 13:57:09.763109 [info] Host is running unRAID 2024-12-18 13:57:09.778787 [info] System information: Linux WotBox 6.6.62-Unraid #1 SMP PREEMPT_DYNAMIC Wed Nov 20 09:15:52 PST 2024 x86_64 GNU/Linux 2024-12-18 13:57:09.791803 [info] Image tags: BASE_RELEASE_TAG=2024110703,IMAGE_RELEASE_TAG=1.41.3.9292-1-01 2024-12-18 13:57:09.809083 [info] PUID defined as '99' 2024-12-18 13:57:09.830398 [info] PGID defined as '100' 2024-12-18 13:57:09.872209 [info] UMASK defined as '000' 2024-12-18 13:57:09.886956 [info] Permissions already set for '/config' 2024-12-18 13:57:09.903625 [info] Deleting files in /tmp (non recursive)... 2024-12-18 13:57:09.923072 [info] TRANS_DIR defined as '/tmp' 2024-12-18 13:57:09.940728 [info] SHARED_NETWORK defined as 'no' 2024-12-18 13:57:09.955731 [info] Starting Supervisor... 2024-12-18 13:57:10,086 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2024-12-18 13:57:10,086 INFO Set uid to user 0 succeeded 2024-12-18 13:57:10,088 INFO supervisord started with pid 7 2024-12-18 13:57:11,089 INFO spawned: 'plexmediaserver' with pid 65 2024-12-18 13:57:11,090 INFO reaped unknown pid 8 (exit status 0) 2024-12-18 13:57:11,842 DEBG 'plexmediaserver' stdout output: Error: Unable to set up server: std::exception (N2DB9ExceptionE) 2024-12-18 13:57:11,916 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23096890944800 for <Subprocess at 23096900773280 with name plexmediaserver in state STARTING> (stdout)> 2024-12-18 13:57:11,916 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23096891832176 for <Subprocess at 23096900773280 with name plexmediaserver in state STARTING> (stderr)> 2024-12-18 13:57:11,916 WARN exited: plexmediaserver (exit status 255; not expected) 2024-12-18 13:57:11,916 DEBG received SIGCHLD indicating a child quit 2024-12-18 13:57:12,918 INFO spawned: 'plexmediaserver' with pid 81 2024-12-18 13:57:13,667 DEBG 'plexmediaserver' stdout output: Error: Unable to set up server: std::exception (N2DB9ExceptionE) 2024-12-18 13:57:13,742 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23096903555488 for <Subprocess at 23096900773280 with name plexmediaserver in state STARTING> (stdout)> 2024-12-18 13:57:13,742 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23096890976176 for <Subprocess at 23096900773280 with name plexmediaserver in state STARTING> (stderr)> 2024-12-18 13:57:13,742 WARN exited: plexmediaserver (exit status 255; not expected) 2024-12-18 13:57:13,742 DEBG received SIGCHLD indicating a child quit 2024-12-18 13:57:15,745 INFO spawned: 'plexmediaserver' with pid 97 2024-12-18 13:57:16,465 DEBG 'plexmediaserver' stdout output: Error: Unable to set up server: std::exception (N2DB9ExceptionE) 2024-12-18 13:57:16,540 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23096891832176 for <Subprocess at 23096900773280 with name plexmediaserver in state STARTING> (stdout)> 2024-12-18 13:57:16,541 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23096891230160 for <Subprocess at 23096900773280 with name plexmediaserver in state STARTING> (stderr)> 2024-12-18 13:57:16,541 WARN exited: plexmediaserver (exit status 255; not expected) 2024-12-18 13:57:16,541 DEBG received SIGCHLD indicating a child quit 2024-12-18 13:57:19,544 INFO spawned: 'plexmediaserver' with pid 113 2024-12-18 13:57:20,294 DEBG 'plexmediaserver' stdout output: Error: Unable to set up server: std::exception (N2DB9ExceptionE) 2024-12-18 13:57:20,380 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23096890976176 for <Subprocess at 23096900773280 with name plexmediaserver in state STARTING> (stdout)> 2024-12-18 13:57:20,380 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23096893202480 for <Subprocess at 23096900773280 with name plexmediaserver in state STARTING> (stderr)> 2024-12-18 13:57:20,380 WARN exited: plexmediaserver (exit status 255; not expected) 2024-12-18 13:57:20,380 DEBG received SIGCHLD indicating a child quit 2024-12-18 13:57:21,381 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly Is anyone able to assist?

Also, can someone confirm that standard sata drives would work in this?

Has anyone used something like this? AU$70.69 | 12 bay 3.5-inch 6Gb hard drive cage 12Gb storage NAS Black Qunhui CDN https://a.aliexpress.com/_mrdrawga If so, how do you find it? And how would you go about cooling it?

all good, I figure I have a higher chance of the disk failing while building parity seeing as it would read 100% of the drive. Thanks, ill give it a try

So, long story short, I have spent the last week or so moving data off array disks, reformating some old drives from Reiserfs to XFS and moving the data back. Because I had 16 array drives and a buttload of data to move around, I disabled my 2 parity drives and used them in unassigned devices to store data while doing this. While in this process, I have noticed that one of my array drives is VERY slow (maybe 10-15MB/s) while every other drive gets copied to at about 183MB/s (with parity disabled). Usually, if I wanted to swap a drive out I would replace it and let parity rebuild it, however with them currently disabled I wanted to know if I can install a new drive, use new config to swap it in the array, and mount the old drive using unassigned devices to copy the data back. I have tried, and the drive is slowing parity rebuild times so I thought this might be a more efficient way to go about this. Obviously I have all VMs and dockers disabled while doing this to ensure nothing else is writing to the array. So, is this something I can do?

👍

👍

got it. So this should be the proceedure: 1. Move data off emulated drive, 2. Bring Array offline 3. Replace Parity drive 4. Shrink array 5. Rebuild parity 6. Add old parity drive into array Sound right?

Noone?

I should mention I would rather not have the array unavailable for a couple of days if I can avoid it (ie don't want to do the parity swap procedure outlined here if possible https://wiki.unraid.net/The_parity_swap_procedure)

Long story short, I just moved home and found an old 8TB drive which had been in a pc on extremely light duties. I ran a 2 pass check and everything looked good so I added it to my array. A couple of days later, I came back to hear the dredded clicking and the array being downgraded and the 'new' drive emulated. This was about 4 days ago, I have been away from home since, so only getting around to sorting something out now. My parity drive is currently 12TB, and the replacement drive I have ordered is 16. The emulated drive only has 50 odd GB of data stored on it, mostly Linux files. Worst case I can redownload what's on it. What's my best course of action? Can I move the data off the emulated disk and shrink the array before replacing my parity drive? Or is there a better idea which I haven't thought of? How would I go about emptying the emulated drive, can unbalance achieve this? Thanks in advance for the help

Thanks. I just reseated everything and it seems to be doing the read check without errors now.

I currently have the system up, but have disabled any downloading to try and keep the data as static as possible until I hear back from the gurus here

Last night/this morning my server popped up an error and disabled one of my disks as it couldnt be writen to. I disabled the drive, ran an extended SMART test which suggested the drive was OK, and went to re-enable the drive in the array. This evening when I went to add it back to the array the system went into a "read check" and spat out thousands (over 2 million in a few mionutes) of errors on 'disk0' I have since canceled the read check as it seemed to have stalled the system. Am i correct that the most likely problem is a cable/set of cables, or possibly the sas controller or port multiplier? I have been rejigging the server for a few days now, and am not sure which drive is where physically or on the controllers wotbox-diagnostics-20220303-1927.zip

for anyone randomly searching, enabling 8x/8x bifeyrcation did the trick, everything is working perfectly now