ninjaneer68

Members
  • Posts

    42
  • Joined

  • Last visited

Everything posted by ninjaneer68

  1. This post is a follow-up to the previous issue. The original post in this thread, was corrupt cache drive that needed reformatted but as we went through the journey, there was other things that needed fixed. During the resolution process, I realized that I hadn't set up some settings optimally for my use cases, as highlight by help from others in this post and discord. Issue: Docker wouldn't start, cache free space was below threshold ( put cache in read-only mode ) Why: my cache drive was full, all downloads went to the cache drive and I did not have array as secondary storage set up Resolution: I did a series of changes over time based off of learning and feedback from the mods in this forum. The list of changes is listed below Reformatted the corrupt cache drive. Updated the share where the Sab downloads go to the following settings ( see figure 2 ) Primary storage: cache secondary storage: arrary mover action: cache >> array I set the above the way I did so the new downloads will hit the cache drive and the drive speed will not be the bottleneck for downloading, I don't need the files to live there long term though, hence the mover action to the array. The share that has appdata, I did the same as the above, except for mover action. I want the app data to live on the cache, but if it accidently fills up I don't want to see all the containers crash ( see figure 3 ) same as above except mover action is different mover action: arary >> cache One of the other mistake adding to the issue, for the sabnzb container, I hard coded the path for the cache vs user. ( see figure 1 ) what I had was /mnt/cache vs having /mnt/user at the time, I had it this way, because I did not have the shares configured correctly to handle this for me. when the cache drive went into read only mode, everything started having issues. Figure 1 - Figure 2 - Figure 3
  2. I spent time working on this over the weekend I will post setting tomorrow evening after work and get some opinionss
  3. I also have the sab completed / incomplete on cache , I am wondering if I should move that.
  4. I will look at this again , I thought I got them all. Yes , after I posted diag I noticed I was under the threshold and fixed that. Is the way I am putting cache in the drive path vs saying /user. Is that correct ?
  5. currently I do see that the cache is locking out because it was below its minimal thresh hold
  6. Here is the new Diag, I am getting errors that /config is not writable. Am I working out of the cache incorrectly ? tower-diagnostics-20231223-1723.zip
  7. if I am happy with the internally docker IP's 172.*, how can I static assign them, vs them changing ?
  8. if I change the path from user to cahce, it works. why is that ? Does it have anything to do with don't split he directory settings ?
  9. I just finished setting up CF Tunnel for ZT, and decommissioned traefik
  10. here is how its mapped That usenet folder, is where the completed and incomplete folders are. You can see from the container terminal window, its mapped, but when I try and make a test directory, it says no space left. It should be able to write to the location
  11. how can i see if the cache drive went to read only mode again ? I have temp download folders located on cache, and my containers are telling me the drive is full that they can't write to the locations that I mapped to the container
  12. tower-diagnostics-20231217-1851.zip Updated Diag
  13. I have everything up and running except Traefik
  14. Is this bad ? I am moving things over to the new cache drive now, about to turn everything back on. should I switch to ipvlan, and move all the containers over to the docker DHCP pool ?
  15. I just replaced the cache drive with a 2 TB SSD. a long time ago, I don' know know, I think i was struggling with docker, I have been setting each container to a static IP from my DHCP pool and instead of using the internal pool, but I am open to switching it back
  16. Where did you see corrupt cache pool at ?
  17. Here is the only thing I have on the cache. I believe the only thing I need to move is the plexmediaserver folder under appdata, the rest doesn't need moved ? ( maybe stuff under system ) Plex-cache/ - plex/ temp/ appdata/ - PlexMediaServer/ data/ - usenet/ ( Folder is empty) system/ - docker/ libvirt/ So far I have moved appdata folder and system folder off the cache. But to memtest the RAM, and going to replace the m.2 drives
  18. I haven't had a chance to work on it yet, I might get to it today or later this week, depending on the WAF .. LOL
  19. Not yet didn't realize bad cache till now. Would love to know the best way to search through this diag files to find the issues like you did.
  20. I did it in the past when I couldn't figure out why my image kept getting full, just never shrank it back down.
  21. My cache drive are two pooled m.2 drives. I recently bought bigger m.2 to replace the current ones. I will work on getting the files off and replace the drives. I moved everything off of cache cause I was running my Plex and sabnzd in cache. Do I went the option that moves things in and out of cache ? What are domains ? I am assuming miss using the cache like you mentioned I am writing to my spinning disk to much ?
  22. I have already deleted the docker.img file and started over and about 2 hours into setting up containers, I started having issues and when I tried to stop docker, I couldn't start it up again. Not sure what is going on. tower-diagnostics-20231216-2129.zip
  23. just curious, why would want to do this, switch to folders vs an image ?
  24. soon as i stopped docker, set the static IP addresses to the following 1.1.1.1 8.8.8.8 I get the following now "Docker Service failed to start."