Hi,

 

I'm on Unraid version 6.12.6 and lately I'm experiencing lock-ups every two days or so. My server just freezes and I have to completely power it off and back on manually. I'm finding this is the system log:

BTRFS error (device loop2): incorrect extent count for 2446327808; counted 2846, expected 2841

I hope I can find some help. I will happily provide additional info, just let me know 🙂

Edited December 13, 20232 yr by TomySLO
Grammar

Please post the diagnostics.

3 minutes ago, JorgeB said:

Please post the diagnostics.

 

titan-diagnostics-20231213-1900.zip

Dec 13 17:31:05 Titan kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 32, gen 0

 

Loop2 is the docker image, it's showing some corruption detected, you should recreate it, if it happens again run memtest.

4 hours ago, JorgeB said:

Dec 13 17:31:05 Titan kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 32, gen 0

 

Loop2 is the docker image, it's showing some corruption detected, you should recreate it, if it happens again run memtest.

Alright, will try that tomorrow, thank you.

I already finished 2 Memtest passes without errors prior to this post so I hope the RAM’s fine.

On 12/13/2023 at 7:13 PM, JorgeB said:

Dec 13 17:31:05 Titan kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 32, gen 0

 

Loop2 is the docker image, it's showing some corruption detected, you should recreate it, if it happens again run memtest.

I managed to successfully recreate the Docker image and also moved it to my cache as I noticed it was on the array. For now it's running great, so thank you again. I will update this in a few days and then mark it as solved if it's still alive.

On 12/13/2023 at 7:13 PM, JorgeB said:

Dec 13 17:31:05 Titan kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 32, gen 0

 

Loop2 is the docker image, it's showing some corruption detected, you should recreate it, if it happens again run memtest.

Hi, I'm back a few days later. Yesterday I marked this as solution because it was running fine for 3-4 days, but around 10 minutes ago it froze/crashed again. I can't see any errors in the system log so I'm attaching new diagnostics in hopes you can help me again. 🙂

titan-diagnostics-20231218-2118.zip

The syslog starts over after a reboot, if it's crashing enable the mirror to flash drive option in the syslog server.

On 12/19/2023 at 9:57 AM, JorgeB said:

The syslog starts over after a reboot, if it's crashing enable the mirror to flash drive option in the syslog server.

Alright, thank you, I set that up yesterday, and today it crashed/froze again. I'm attaching two syslogs - I'm not sure which one is the correct one, that's why.

syslog syslog-previous

There's nothing relevant logged, but there's a container that appears to be constantly re-startiing, try finding out which one by looking at the up time.

8 minutes ago, JorgeB said:

There's nothing relevant logged, but there's a container that appears to be constantly re-startiing, try finding out which one by looking at the up time.

You're right, I found that Immich was restarting, or more specifically - immich_microservices. I have Immich installed through docker-compose since it wasn't yet available in the APPS tab when I first set it up. Here is the docker-compose script if it's at all relavant:

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: [ "start.sh", "immich" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    ports:
      - 2283:3001
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.yml
    #   service: hwaccel
    command: [ "start.sh", "microservices" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always

  typesense:
    container_name: immich_typesense
    image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd
    environment:
      - TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
      - TYPESENSE_DATA_DIR=/data
      # remove this to get debug messages
      - GLOG_minloglevel=1
    volumes:
      - tsdata:/data
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3
    restart: always

  database:
    container_name: immich_postgres
    image: postgres:14-alpine@sha256:28407a9961e76f2d285dc6991e8e48893503cc3836a4755bbc2d40bcc272a441
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
    volumes:
      - pgdata:/var/lib/postgresql/data
    restart: always

volumes:
  pgdata:
  model-cache:
  tsdata:

Maybe some update changed the behaviour of it and is now constantly restarting.

 

Should I try to set it up from the APPS tab and remove the docker-compose one? What is the "better" solution when it comes to running Docker containers on Unraid?

Edited December 20, 20232 yr by TomySLO

12 minutes ago, TomySLO said:

Should I try to set it up from the APPS tab and remove the docker-compose one? What is the "better" solution when it comes to running Docker containers on Unraid?

Sorry, can't really help with that, maybe someone else can.

3 minutes ago, JorgeB said:

Sorry, can't really help with that, maybe someone else can.

No worries, you've done a lot already 🙂 Thank you again for all the help, you've been amazing.