• Posts

  • Joined

  • Last visited


  • Personal Text
    personal text here

Recent Profile Visitors

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

MrLinux's Achievements


Rookie (2/14)



  1. Were you able to get the GTX 1650 for a reasonable price? If so, mind sharing where? Thanks
  2. Following too. Has anyone gotten any Ryzen APU working?
  3. Just curious, what is the reason since this works in the official docker?
  4. Hi, I received this alert from Fix Common Problems When running mcelog, I get this error root@unraid:~# mcelog mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. CPU is unsupported From another thread, this may be expected behavior since it's just warning us it's not an Intel CPU. Is it safe to ignore these errors or is there an actual issue? Thanks
  5. Oh. So those of us with AMD can ignore this error? Sent from my iPhone using Tapatalk
  6. What are we supposed to do when we get this error message? I see that the module is included root@unraid:~# lsmod | grep mce edac_mce_amd 32768 0 Does this mean we don't need to manually run anything and just provide our diag file?
  7. What did you do to get your binhex-plex docker registered with your Plex account? Whenever I would login to plex by going directly to http://ip:32400/, it would tell me to download/install the Plex Server instead of showing/connecting to the docker's Plex Server. I've tried to Manually expose all the port (run command parameters: -p 32400:32400 -p 1900:1900/udp -p 3005:3005/udp -p 5353:535/udp -p 8324:8324 -p 32410:32410 -p 32412:32412/udp -p 32414:32414/udp -p 3246:3246) Restart the docker several times Checked NAT settings in my pfSense router Blow away the docker and appdata config and reinstall Troubleshooting the script and docker files None of it worked until I just tried to use another container distro of Plex. FWIW, it was also showing me serverUui errors when using bridge mode. Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign
  8. I ended up getting it working by moving over to another Plex Docker release (plexinc Plex Media Server). Assign the claim variable Set the bridge and static ip (br0.255 in my case) Troubleshooting Some extra steps may be needed before it works Logout of plex first Restarted the container a few times Double check the NAT rule (pfSense) After logging in again, it should show you the Plex Server setup screen instead of a client without a source (your Docker's Plex Server)
  9. Did you ever get this working? I'd like put Plex in a vlan as well. It's only working when set to host mode.
  10. Closing this as solved as I'm no longer having issues, although it would be interesting to know if there are actually any config issues which lead up to the corruption in the first place. Would like to avoid this from happening again. Thanks again for all the help @trurl
  11. Thanks, so I'm not crazy...or we're crazy together
  12. TL:DR I'm finding a hard time finding my config/mapping issues to show that a 20GB of used docker.img is unreasonable with 29 containers. BTW, it seems many of my syslog errors went away after disabling daily plugin checks and disable/re-enable ipmi. I've since re-enabled daily plugin checks and the errors have not come back. I read it could have been related to being unable to connect to github if it had an outage or some other routing issues. Checked what is using up the 5.88GB in the container, but see it's only using up 3.6GB instead. Where is the other ~2.2GB coming from? I see "Writable" is roughly this size of ~2.2GB. Where is this 2.2GB coming from? The only location that's big enough to be considered in the local filesystem is in /home, as there are no other directories large enough to account for the 2.2GB. sh-5.0# find / -maxdepth 1 -mindepth 1 -type d \! -exec mountpoint -q {} \; -exec du -xshc {} + | sort -h 0 /boot 0 /mnt 0 /opt 0 /run 0 /srv 4.0K /.gnupg 12K /root 24K /tmp 8.1M /etc 14M /var 1.5G /usr 2.2G /home # <---------------------- 3.6G total Inside home is just a user called nobody. The files in here do not appear to be user-created files from the application. sh-5.0# cd /home sh-5.0# ls -la total 0 drwxr-xr-x 1 root root 12 Sep 2 01:12 . drwxr-xr-x 1 root root 206 Nov 29 04:06 .. drwxrwxr-x 1 nobody users 130 Nov 29 04:08 nobody sh-5.0# cd nobody/ sh-5.0# ls -la total 8 drwxrwxr-x 1 nobody users 130 Nov 29 04:08 . drwxr-xr-x 1 root root 12 Sep 2 01:12 .. drwxrwxrwx 1 nobody users 38 Nov 29 04:06 .aspnet -rw------- 1 root root 581 Nov 29 04:23 .bash_history drwxrwxr-x 1 nobody users 34 Sep 5 11:32 .cache drwxrwxr-x 1 nobody users 6 Sep 5 11:29 .config drwxrwxr-x 1 nobody users 220 Sep 5 11:35 .dotnet drwxrwxr-x 1 nobody users 10 Sep 5 11:36 .local drwxrwxr-x 1 nobody users 26 Sep 5 11:36 .nuget -rwxrwxr-x 1 nobody users 467 Sep 5 11:28 drwxrwxr-x 1 nobody users 6 Sep 5 11:32 .yarn sh-5.0# find . -maxdepth 1 -mindepth 1 -type d \! -exec mountpoint -q {} \; -exec du -xshc {} + | sort -h 0 ./.yarn 4.0K ./.aspnet 4.0K ./.config 12K ./.dotnet 254M ./.local 639M ./.cache 1.3G ./.nuget 2.2G total Using mountpoint, I found that /config is actually a mountpoint, even though it doesn't appear as one using df. sh-5.0# mountpoint /config /config is a mountpoint sh-5.0# mountpoint /media /media is a mountpoint sh-5.0# mountpoint /home /home is not a mountpoint sh-5.0# mountpoint /usr /usr is not a mountpoint
  13. Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-jellyfin' --net='br0.255' --ip='' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'TCP_PORT_8096'='8096' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Media/':'/media':'rw' -v '/mnt/user/appdata/binhex-jellyfin/':'/config':'rw' 'binhex/arch-jellyfin' 52e486470c7c51a7f66090a6170f549a9e6b885ce943f28f32fe23cc43cd5358 The command finished successfully! I tested if the container's /config is really mapped to /mnt/user/appdata/binhex-jellyfin. The test below shows that it is mapped, even though /config is not seen as a mountpoint in the container (df -hP). Thanks for the help.
  14. The interesting part is that /media has its own mount point but /config doesn't. I'm trying to understand if I actually have any setup issues where more data is being stored in the docker image than in appdata.