shinta148

Members
 View Profile  See their activity

  • Posts

    17

  • Joined

  • Last visited

 Content Type 

Posts posted by shinta148

    Major Docker Issues since 6.12 RC4

    in General Support

    Posted · Edited by shinta148

    Ever since upgrading to 6.12 RC4 I've been having major docker issues. Dockers failing to start and stop with execution errors, dockers failing to upgrade and orphaning images, causing me to have to re-install them, and extremely poor docker performance that wasn't happening prior to 6.12 RC4. An example of what Docker updates are doing is here:

      

    Pulling image: lscr.io/linuxserver/calibre:latest
IMAGE ID [470182561]: Pulling from linuxserver/calibre.
IMAGE ID [a0a42e1e46b9]: Already exists.
IMAGE ID [a55b6a7607b3]: Already exists.
IMAGE ID [a323e3c11ed4]: Already exists.
IMAGE ID [5bb61648b0b7]: Already exists.
IMAGE ID [68a3079ee85a]: Already exists.
IMAGE ID [88cf2429a52f]: Already exists.
IMAGE ID [887b3ce1e536]: Pulling fs layer.Downloading 100% of 3 MB.Download complete.Extracting.Pull complete.
IMAGE ID [c479adae11df]: Pulling fs layer.Downloading 100% of 19 MB.Verifying Checksum.Download complete.Extracting.Pull complete.
IMAGE ID [fdeaaaae2c65]: Pulling fs layer.Downloading 100% of 412 MB.Verifying Checksum.Download complete.Extracting.Pull complete.
IMAGE ID [8c4bbb9db0f1]: Pulling fs layer.Downloading 100% of 9 KB.Verifying Checksum.Download complete.Extracting.Pull complete.
IMAGE ID [226071cbcef3]: Pulling fs layer.Downloading 100% of 239 MB.Verifying Checksum.Extracting.
IMAGE ID [a7304da4b7d1]: Pulling fs layer.Downloading 100% of 951 B.Verifying Checksum.Download complete.

TOTAL DATA PULLED: 673 MB


Stopping container: calibre
Error:


Removing container: calibre
Error:


Command execution
docker run
  -d
  --name='calibre'
  --net='bridge'
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="asc-unraid01"
  -e HOST_CONTAINERNAME="calibre"
  -e 'PASSWORD'=''
  -e 'CLI_ARGS'=''
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/calibre-logo.png'
  -p '8085:8080/tcp'
  -p '8182:8181/tcp'
  -p '8081:8081/tcp'
  -v '/mnt/user/Media/books/':'/books':'rw'
  -v '/mnt/cache/appdata/calibre':'/config':'rw' 'lscr.io/linuxserver/calibre'
docker: Error response from daemon: Conflict. The container name "/calibre" is already in use by container "77e7761ab64e73e77cb580b89c3f3066a740a2f664bc085d64acfadda83c22bd". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

The command failed.

     

    I've been looking through logs trying to find something but I'm honestly beating my head against a wall at the moment. I could really use some support.

    asc-unraid01-diagnostics-20230524-2159.zip

    [SOLVED] Crashing every few days

    in General Support

    Posted

    @JorgeB Hey man, Thanks for taking the time to look. I've removed the server from the rack and tossed it on my desk and have it hooked up now with all but 2 of the sticks of RAM removed. So far going on 18 hours with 0 error. I'm going to let it sit until Wednesday when some new RAM I ordered comes in, but so far it looks like a hardware issue. 

     

    If I don't see any crashes until I'm ready to swap the RAM out I'll mark the topic resolved. 

    • Like 1

    [SOLVED] Crashing every few days

    in General Support

    Posted · Edited by shinta148

    So the crashes are back. I've been mirroring the syslog to my flash drive and this is what it's collected (see attached). I've run memtest86 on it multiple times hoping it was a simple memory issue, but it isn't reporting anything. I've been researching everything in the log I don't recognize but I'm coming up blank :(

     

    Edit: Added a diag too

     

    syslog

    asc-unraid01-diagnostics-20210430-1408.zip

    [SOLVED] Crashing every few days

    in General Support

    Posted

    Hey @JorgeB, Thanks for your help again. I went ahead and ran XFS_Repair on MD6 and it seems to have resolved that issue. I did find that in that latest set of panics I saw and in some more today that it kept referencing the qbittorrent-nox process from the qbittorrent docker. I stopped that docker and I'm going to let the server run for a few days and see if the crashes stop. 

    • Like 1

    Sata controller missing after 6.7 upgrade

    in General Support

    Posted

    On 5/13/2019 at 3:57 AM, Squiggley said:

    thanks for the response. Its working now, the issue was with the Marvell 88SE9230 SATA Chipset, appending "iommu=pt" in my syslinux fixed it. 

     

    @Squiggley Would you mind sharing what the modified syslinux.cfg looked like? I've never done this in practice and want to see if this resolves my issue with the same controller.

    Unraid OS version 6.7 available

    in Announcements

    Posted

    I'm also having the upgrade issue I think is related to the Marvel controller. Disabling Intel VT-D did not work.

     

    This is what I have :

    00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05)
    00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05)
    81:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11)

     

    Also attached diagnostics. I can't seem to make this work. I can't really afford to replace the controller either yet =/

     

    Anyone have any other ideas?

    asc-unraid01-diagnostics-20190514-2332.zip