Jump to content

hovee

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

1 Neutral

About hovee

  • Rank
    Member

Recent Profile Visitors

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

  1. I followed @S1dney post that is a work around. It DRASTICALLY reduced my writes. I would recommend you check it out. I can now sleep easily as night. One thing that confused me was that after I rebooted I didn't have any docker containers listed. I then had to select Add Container and then choose the template from the drop down. It was quick and only took about 10 minutes to re-add about 20 containers that I had set up previously.
  2. Thank you for your help, and you're right, I don't want to derail this thread from the issue at hand. If anyone is curious, I was able to get it working after @S1dneys insight. To get it to work, I had to take the original rc.docker file from 6.8.3 and modified only the start_docker() with the updates. That restored the proper networking after a reboot.
  3. This is great! I implemented your work around and re-added the containers from the templates like you suggested and the writes are drastically reduced! One thing I did notice and wanted to see if I'm crazy. Making the change to not use the docker.img blocks network access from the host to the macvlan containers even though I have it set to enabled. For example, my Unraid is 10.0.0.2 and my Plex container 10.0.0.5 is on the custom macvlan adapter (br0). While not using the docker.img pinging from unraid to plex, it never replies and get destination host not reachable. If I remove your work around and docker uses docker.img. Unraid can ping the Plex container. It isn't the worst thing, but I do have some reverse proxies that aren't working until I get this figured out. Any thoughts?
  4. Thank you for the explanation. That makes sense. I will give that a try!
  5. I tried following your tutorial, but after reboot it tells me I don't have any docker containers installed. It shows me the docker service is running. Checking the logs I can see it created the softlinks. If I remove that entry to copy the rc.docker file in the /boot/config/go directory everything works again after a reboot. However, then it puts it back to original and uses loop2.
  6. yep.. I was just doing some math from my post above and came to the conclusion it made no difference and I'm still screwed...
  7. EDIT: Nevermind... still screwed. I posted earlier that I'm affected by this issue as well. I am using a btrfs unencrypted cache pool with 2x 1TB Samsung 860 EVO SSDs. One thought occurred to me that I wanted to run by everyone. For your containers that you have running do you have them set to /mnt/cache/appdata or /mnt/user/appdata? I had all of mine set to /mnt/cache/appdata. Every time I would install a new container I would change the variable path to use cache. I just went through all of my containers that I have running and switched them to /mnt/user/appdata. Right now I'm at 2gb writes for loop2 writes after 10 minutes. I need to do more testing and see if this is any better. I'm grasping at straws as my SSDs are trashed now. I currently have 25 containers running: 1activegeek/airconnect grafana/grafana homeassistant/home-assistant influxdb:latest jlesage/filebot jlesage/filezilla jlesage/firefox jlesage/handbrake linuxserver/ddclient linuxserver/duckdns linuxserver/letsencrypt linuxserver/mariadb linuxserver/nextcloud linuxserver/plex linuxserver/unifi-controller modenaf360/youtube-dl-nas oznu/homebridge portainer/portainer saspus/duplicacy-web spants/mqtt telegraf:alpine
  8. I'm having this issue as well with tons of writes to my Cache Pool from loop. Unfortunately, the warranty on my SSDs are now shot with just over a year of run time. Power on hours: 10373 Total LBAs Written: 1972163391415 - 918 TB unraid-diagnostics-20200416-1127.zip
  9. Thank you! I figured it out... My CRL on my Openvpn VM expired today. Nothing to do with 6.6.7.
  10. I upgraded successfully but am now having an issue connecting to a VM that is running my openvpn server. Were there any changes to iptables that would now be blocking access to it? Probably something on my end, but was curious if anyone else noticed anything.
  11. Good point. Next time this happens I’ll wait longer after I hit cancel to see if that stops the operation. I’ll check out the MakeMKV forums. Thanks for your help!
  12. I’m using the UI through Web and VNC.
  13. I checked my docker image and I have plenty of space. I have a 100gb file. I've been able to re-produce this a few times now. When I have a disc that has a scratch on it and it is unable to copy successfully, MakeMKV keeps ticking up in time till completion. I then try and stop the copy in MakeMKV and then try and stop the container and am unable to. I can then go into htop and search for the container id and kill it. After that is killed, I can remove the container and re-add it, however there is still a process that has a signal D and is waiting for the drive. I am unable to kill that process regardless of Sigterm/Sigkill. You can see in the screenshot process 20667 that can not be killed which is hanging up the system from stopping the array/rebooting/shutting down/etc... Any thoughts on how to make sure this doesn't happen if a disc doesn't copy successfully?
  14. I’ve been having issues stopping the container. I will click the stop button for the container and it will hang and never fully stop. I’ve tried to kill it from the Cali, but haven’t had any luck either. I’ve tried docker kill MakeMkV, docker rm MakeMKV and neither work. I will have to force shut down my system to get it back. I’ve deleted my MakeMKv folder in app data and reinstalled. Still the same scenario. I am using an external USB Blu-ray drive, if that makes any difference. It works great and is able to read the disk when I am able to VNC into MakeMKV. Any thoughts? here are my logs when I try to stop the container. 15/02/2019 20:56:24 Statistics events Transmit/ RawEquiv ( saved) 15/02/2019 20:56:24 FramebufferUpdate : 107 | 0/ 0 ( 0.0%) 15/02/2019 20:56:24 ZRLE : 272 | 182954/ 5909520 ( 96.9%) 15/02/2019 20:56:24 RichCursor : 2 | 1776/ 1776 ( 0.0%) 15/02/2019 20:56:24 TOTALS : 381 | 184730/ 5911296 ( 96.9%) 15/02/2019 20:56:24 Statistics events Received/ RawEquiv ( saved) 15/02/2019 20:56:24 PointerEvent : 216 | 1296/ 1296 ( 0.0%) 15/02/2019 20:56:24 FramebufferUpdate : 107 | 1070/ 1070 ( 0.0%) 15/02/2019 20:56:24 SetPixelFormat : 2 | 40/ 40 ( 0.0%) 15/02/2019 20:56:24 SetEncodings : 2 | 112/ 112 ( 0.0%) 15/02/2019 20:56:24 TOTALS : 327 | 2518/ 2518 ( 0.0%) 15/02/2019 20:56:24 destroyed xdamage object: 0x200034 [services.d] stopping services [services.d] stopping app... [services.d] stopping openbox... [services.d] stopping statusmonitor... [services.d] stopping logmonitor... [services.d] stopping x11vnc... caught signal: 15 16/02/2019 07:26:03 deleted 40 tile_row polling images. [services.d] stopping xvfb... [services.d] stopping nginx... [services.d] stopping certsmonitor... [services.d] stopping s6-fdholderd... [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.