Luc1fer

It's funny you should say that, because I posted this message and went to bed while I waited for guidance. By the morning it had "fixed" itself. It would be nice to know what it is doing. Maybe a warning that it will take a while and to wait, as I rebooted the docker a few times and force updated it which probably only served to slow things down.

I updated my docker and it didn't come back up properly. I restarted it. The log now just shows: [migrations] started [migrations] no migrations found ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- **** Server already claimed **** No update required [custom-init] No custom files found, skipping... Starting Plex Media Server. . . (you can ignore the libusb_init error) [ls.io-init] done. When I go to https://ipadress:32400/web/index.html I just get: This XML file does not appear to have any style information associated with it. The document tree is shown below. <Response code="503" title="Maintenance" status="Plex Media Server is currently running database migrations."/> Any ideas where to go from here?

I had this as well. Ended up being my web browser. I cleared browser data and it worked again.

That would make sense and was what I would expect it to do. How do I go about checking the flash drive? I can see that the system is able to write to the flash drive as there are upto date parity-check logs.

Thanks for that. I do click the thumb down and select acknowledge. It then turns green for a few weeks and will then have the orange thumbs down again. When I hover over it it will tell me that the drive has 3 UDMA CRC errors, but these are not additional errors, its still the same 3 errors that I have acknowledged quite a few times. I was hoping there was a way to only get the drive flagged if there are additional errors.

I have 2 cache drives in a pool. Quite a few months ago I got a small number of UDMA CRC errors on one of the drives (UDMA CRC error count = 3). I changed the SATA cable, acknowledged the error in the dashboard and it all looked good. The pool functions normally. I have no issues with it, but every few weeks that drive will come up with failed and a UDMA CRC error count of 3. When I look at SMART data the count is not increasing, it still has a total error count of 3. So my question is how do I acknowledge the UDMA CRC error count of 3 permanently for this drive and only have unraid notify me if this increases?

You can add me to the list of people having kernel panics with macvlan call traces. I only have 1 docker on custom:br0 (unifi controller). I was stable on 6.8.3 for ages, then updated to 6.9.0 and had an kernel panic, downgraded to to 6.8.3 and was stable until 6.9.2 came out - updated and got kernel panics again. I have disabled my unifi docker and am stable again for almost 2 weeks on 6.9.2. I do not have host access enabled. Motherboard is a Supermicro X9DRi-LN4+. It would be great to have a solution to this issue.

Thanks for that. It appears I am definitely not alone with this issue!

I have had my unraid system running for a few years and it has been very stable. When 6.9.0 was release I updated to it and within a few days I had the system become non responsive and had a kernel panic. At that time I wasn't sure what caused it so I rolled back and the system was stable once again for quite a few months until I updated to 6.9.2. After updating to 6.9.2 I had a kernel panic within the first week. This happened again about a week later, but before hand there were macvlan call traces which led me to suspect my docker setup. I had my unifi controller docker on custom:br0 as I couldn't get it to run on host or bridge in the past and it had been stable on 6.8.x I disabled the unifi docker and rebooted and it seems to have resolved my issue (fingers crossed - it's only been about 2 weeks), but my question is what changed in the new update that has caused the issue, since it was running for years before hand without any issues using custom:br0? Thanks, L.

Hi, I've managed to get all my dockers working through VPN eg sonarr etc except for couchpotato. I can't seem to find any way in couchpotato to ignore the proxy for local addresses or specific addresses. Has anyone found a solution for couchpotato?

I've started to get this in my plex docker log that seems to repeat about once a day. How do I go about finding out what files are missing? __code__:181: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead. ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Not enough audio data ERROR: Could not open the input file (No such file or directory) ERROR: The argument for -length must be a positive number ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) ERROR: Could not open the input file (No such file or directory) __code__:181: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.

Just an update. Not sure why, but I stopped using the ram drive (/dev/shm) for the transcoding directory and plex started again. It's been working with this setting for a long time, so i'm not sure if it was just a coincidence and something else changed at the same time.

Thanks trurl. Here is the docker run command, sorry I didn't include it the first time. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'VERSION'='latest' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'TCP_PORT_32400'='32400' -e 'TCP_PORT_3005'='3005' -e 'TCP_PORT_8324'='8324' -e 'TCP_PORT_32469'='32469' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_32410'='32410' -e 'UDP_PORT_32412'='32412' -e 'UDP_PORT_32413'='32413' -e 'UDP_PORT_32414'='32414' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Videos/Movies/':'/movies':'rw' -v '/mnt/user/Videos/TV/':'/tv':'rw' -v '/mnt/user/Music/':'/music':'rw' -v '/dev/shm':'/transcode':'rw' -v '/mnt/user/appdata/plex':'/config':'rw' 'linuxserver/plex' 3ab0960e33f1ee3786b6e95ca797280eff3305861359548b67246229fa658307

Hi, I updated my plex docker today, but now plex wont start. Any ideas where I can start to troubleshoot this? The docker log says its starting plex media server but the server remains unavailable. User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 45-plex-claim: executing... [cont-init.d] 45-plex-claim: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... Atempting to upgrade to: 1.20.0.3133-fede5bdc7 2020-07-25 07:09:29 URL:https://downloads.plex.tv/plex-media-server-new/1.20.0.3133-fede5bdc7/debian/plexmediaserver_1.20.0.3133-fede5bdc7_amd64.deb [80097730/80097730] -> "/tmp/plexmediaserver_1.20.0.3133-fede5bdc7_amd64.deb" [1] (Reading database ... 10450 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.20.0.3133-fede5bdc7_amd64.deb ... PlexMediaServer install: Pre-installation Validation. PlexMediaServer install: Docker detected. Preinstallation validation not required. Unpacking plexmediaserver (1.20.0.3133-fede5bdc7) over (1.19.5.3112-b23ab3896) ... Setting up plexmediaserver (1.20.0.3133-fede5bdc7) ... PlexMediaServer install: Docker detected. Postinstallation tasks not required. Continuing. Processing triggers for libc-bin (2.27-3ubuntu1.2) ... [cont-init.d] 60-plex-update: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Starting Plex Media Server. Edit to add docker run command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'VERSION'='latest' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'TCP_PORT_32400'='32400' -e 'TCP_PORT_3005'='3005' -e 'TCP_PORT_8324'='8324' -e 'TCP_PORT_32469'='32469' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_32410'='32410' -e 'UDP_PORT_32412'='32412' -e 'UDP_PORT_32413'='32413' -e 'UDP_PORT_32414'='32414' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Videos/Movies/':'/movies':'rw' -v '/mnt/user/Videos/TV/':'/tv':'rw' -v '/mnt/user/Music/':'/music':'rw' -v '/dev/shm':'/transcode':'rw' -v '/mnt/user/appdata/plex':'/config':'rw' 'linuxserver/plex' 3ab0960e33f1ee3786b6e95ca797280eff3305861359548b67246229fa658307

Thanks for your help. I've now got everything back up and running again. It took over 6 hours to copy stuff back to the cache drive mainly because of plex, I never realised that the plex appdata was so large!