ninjaneer68

Members
 View Profile  See their activity

  • Posts

    43

  • Joined

  • Last visited

 Content Type 

Posts posted by ninjaneer68

    Docker will not start

    in General Support

    Posted · Edited by ninjaneer68

    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 - image.thumb.png.733b99a90c0af0e1362a4478b2a0f686.png
    • Figure 2 - image.thumb.png.643f606670eefc8f5c03225144f5435f.png
    • Figure 3image.thumb.png.6904c05e95fcf0693baf0ce16a51e570.png

    Docker will not start

    in General Support

    Posted

    7 hours ago, JorgeB said:

    appadata on disks 4 and 5

     

    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 ? 

    Docker will not start

    in General Support

    Posted

    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

    image.thumb.png.90045dfd0c5d105006e434386517389d.png

    image.thumb.png.63f247edf596413ef07049f5f84c3ef2.png

    image.thumb.png.7f003864bb5a22e6dff084e4201d808a.png

    image.thumb.png.58af2c1c5c5a3acab0eb9ae1df940224.png

    image.png.d5d024a4afcdcb74ecc9b60c73017c64.png

    image.thumb.png.ee9eec39323261c3c40c700813e5f024.png

    Docker will not start

    in General Support

    Posted

    18 hours ago, trurl said:

    Why do you think you want 60G docker.img?


    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 ?

    Docker will not start

    in General Support

    Posted

    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

    Docker will not start

    in General Support

    Posted · Edited by ninjaneer68

    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

    Docker will not start

    in General Support

    Posted · Edited by sstretchh

    18 minutes ago, trurl said:

    Have you done memtest?

    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. 

    Docker will not start

    in General Support

    Posted

    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. 

     

    14 minutes ago, trurl said:

    Ideally, appdata, domains, system shares would have all files on fast pool such as cache with nothing on the array for Docker/VM performance, and so array disks can spin down since these files are always open

     

    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 ?