Luc1fer

Members
  • Posts

    41
  • Joined

  • Last visited

Recent Profile Visitors

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

Luc1fer's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. 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.
  2. Thanks for that. It appears I am definitely not alone with this issue!
  3. 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.
  4. 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?
  5. 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.
  6. 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.
  7. 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
  8. 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
  9. 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!
  10. Thanks for your advice, is it sufficient to just manually copy all data to a temporary location then copy it back once the cache pool has been reformatted?
  11. Thanks for that. Here is a new set of diagnostics after running mover again. chenbro-svr-diagnostics-20200224-2135.zip
  12. It's still running but I am seeing alot of these: Feb 24 21:30:01 chenbro-svr move: move: file /mnt/cache/system/docker/docker.img Feb 24 21:30:01 chenbro-svr move: move: create_parent: /mnt/cache/system/docker error: Read-only file system Feb 24 21:30:01 chenbro-svr move: move: create_parent: /mnt/cache/system error: Read-only file system Feb 24 21:30:01 chenbro-svr move: move: file /mnt/cache/system/libvirt/libvirt.img Feb 24 21:30:01 chenbro-svr move: move: create_parent: /mnt/cache/system/libvirt error: Read-only file system Feb 24 21:30:01 chenbro-svr move: move: create_parent: /mnt/cache/system error: Read-only file system Feb 24 21:30:01 chenbro-svr move: move_object: /mnt/cache/system: Read-only file system Feb 24 21:30:01 chenbro-svr root: mover: finished I'll attach a new syslog once it has stopped.
  13. If i'm going to recreate the docker.img when I select delete in the docker settings will it delete both copies or should I delete one copy using MC?
  14. Thanks for the reply. I forgot to say that I stopped both the docker and VM services before invoking the mover, but those files still seem to have not moved, or for some of them they have been copied, but not deleted from the cache. Running: btrfs dev stats /mnt/cache gives: Linux 4.19.98-Unraid. root@chenbro-svr:~# btrfs dev stats /mnt/cache [/dev/sdr1].write_io_errs 0 [/dev/sdr1].read_io_errs 0 [/dev/sdr1].flush_io_errs 0 [/dev/sdr1].corruption_errs 0 [/dev/sdr1].generation_errs 0 [/dev/sds1].write_io_errs 3714141 [/dev/sds1].read_io_errs 2077762 [/dev/sds1].flush_io_errs 152140 [/dev/sds1].corruption_errs 0 [/dev/sds1].generation_errs 0 sds1 is a replacement SSD when I had an issue with a previous one in that slot dropping out and eventually failing. I changed the cable and put it back in and let unraid restore the cache pool. Obviously there is something about either that bay or SATA connector that is causing issues to the SSD? Should I power down and remove cache2 (sds1)?
  15. Hi, I have upgraded to 6.8.2 from 6.6.7 I have noticed that my cache pool was giving these errors: kernel: BTRFS info (device sdr1): relocating block group 1055678005248 flags data|raid1 I tried to balance my pool but that didn't do anything, but started giving these errors: kernel: BTRFS critical (device sdr1): corrupt leaf: root=5 block=286758944768 slot=2, bad key order, prev (11529215046071388418 254 281472965546548) current (2918659 1 0) So I thought that I would move everything off the cache pool and then recreate the pool again. I set all of the shares that were on cache only and cache preferred to YES and invoked the mover. The mover has finished, but there is still about 100gb of data on the cache pool that wont move to the array. Data, RAID1: total=66.00GiB, used=34.74GiB Data, single: total=53.00GiB, used=24.62GiB System, RAID1: total=32.00MiB, used=48.00KiB Metadata, RAID1: total=2.00GiB, used=68.08MiB Metadata, single: total=1.00GiB, used=704.00KiB GlobalReserve, single: total=36.80MiB, used=0.00B No balance found on '/mnt/cache' Mainly this seems to be the docker and libvirt folders and files. It also appears that there are 2 copies of docker.img, one on the cache drive and then what appears to be an older dated file on disk11. Also my domains and isos folder has not been moved to the array (i have copied all the data to a local drive on my pc as a backup). I'm not sure how to proceed from here. I have attached my diagnostics zip. Thanks for your help. chenbro-svr-diagnostics-20200224-2023.zip