Migration Failed from 2.4.1 to 2.5.5

[rickythewoof]

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

• Yes

The bug

I'm having big issues regarding migration from 2.4.1 to 2.5.5. I'm using portainer as my docker manager, and when I do re-pull image and redeploy I get weird issues regarding page verification issues. I used a prior backup of my server to get back and redo the process (maybe something got shutdown wrong?) but I still get the same issue again

I've also updated the docker-compose.yml to the latest one (especially updating the references to the latest images)

The OS that Immich Server is running on

Ubuntu Server LTS

Version of Immich Server

2.5.5

Version of Immich Mobile App

2.5.5

Platform with the issue

• Server
• Web
• Mobile

Device make and model

No response

Your docker-compose.yml content

#
# WARNING: Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.
#

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.transcoding.yml
    #   service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
    volumes:
      # Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - stack.env
    ports:
      - '2283:2283'
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false
    deploy:
      resources:
        limits:
          cpus: "1.5"

  immich-machine-learning:
    container_name: immich_machine_learning
    # For hardware acceleration, add one of -[armnn, cuda, openvino] to the image tag.
    # Example tag: ${IMMICH_VERSION:-release}-cuda
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration
    #   file: hwaccel.ml.yml
    #   service: cpu # set to one of [armnn, cuda, openvino, openvino-wsl] for accelerated inference - use the `-wsl` version for WSL2 where applicable
    volumes:
      - model-cache:/cache
    env_file:
      - stack.env
    restart: always
    healthcheck:
      disable: false
    deploy:
      resources:
        limits:
          cpus: "1.5"

  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:9@sha256:546304417feac0874c3dd576e0952c6bb8f06bb4093ea0c9ca303c73cf458f63


    healthcheck:
      test: redis-cli ping || exit 1
    restart: always

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191b76a916ae5eb93464d65c07511da41e3bf7a8416db519b40b1c23
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data
    shm_size: 128mb
    healthcheck:
      disable: false
    restart: always

volumes:
  model-cache:

Your .env content

UPLOAD_LOCATION=/mnt/immich
DB_DATA_LOCATION=/home/ricky/immich-app/postgres
IMMICH_VERSION=release
DB_PASSWORD=[REDACTED]
DB_USERNAME=[REDACTED]
DB_DATABASE_NAME=immich

Reproduction steps

1. Have Immich version 2.4.1 successfully running as always
2. Close

...

Relevant log output

Initializing Immich v2.5.5

Detected CPU Cores: 1

(node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time

(Use `node --trace-warnings ...` to show where the warning was created)

Starting api worker

Starting microservices worker

(node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time

(Use `node --trace-warnings ...` to show where the warning was created)

[Nest] 7  - 02/07/2026, 11:36:04 AM     LOG [Microservices:WebsocketRepository] Initialized websocket server

(node:22) ExperimentalWarning: WASI is an experimental feature and might change at any time

(Use `node --trace-warnings ...` to show where the warning was created)

[Nest] 7  - 02/07/2026, 11:36:05 AM     LOG [Microservices:DatabaseRepository] Creating VectorChord extension

[Nest] 7  - 02/07/2026, 11:36:05 AM     LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for clip_index of 33469 rows

[Nest] 7  - 02/07/2026, 11:36:05 AM     LOG [Microservices:DatabaseRepository] Reindexing clip_index (This may take a while, do not restart)

[Nest] 7  - 02/07/2026, 11:36:05 AM     LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for face_index of 23036 rows

[Nest] 7  - 02/07/2026, 11:36:05 AM     LOG [Microservices:DatabaseRepository] Reindexing face_index (This may take a while, do not restart)

[Nest] 22  - 02/07/2026, 11:36:06 AM     LOG [Api:WebsocketRepository] Initialized websocket server

[Nest] 7  - 02/07/2026, 11:36:36 AM     LOG [Microservices:DatabaseRepository] Reindexed face_index

[Nest] 7  - 02/07/2026, 11:36:45 AM     LOG [Microservices:DatabaseRepository] Reindexed clip_index

[Nest] 7  - 02/07/2026, 11:36:45 AM     LOG [Microservices:DatabaseRepository] Dropping pgvecto.rs extension

[Nest] 7  - 02/07/2026, 11:36:45 AM     LOG [Microservices:DatabaseRepository] Running migrations

Postgres notice: {

  severity_local: 'WARNING',

  severity: 'WARNING',

  code: 'XX001',

  message: 'page verification failed, calculated checksum 58098 but expected 53575',

  file: 'bufpage.c',

  line: '150',

  routine: 'PageIsVerifiedExtended'

}

Query failed : {

  durationMs: 199.0186160000012,

  error: PostgresError: invalid page in block 602 of relation base/16384/17483

      at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:815:30)

      at handle (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:489:6)

      at Socket.data (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:324:9)

      at Socket.emit (node:events:508:28)

      at addChunk (node:internal/streams/readable:559:12)

      at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)

      at Readable.push (node:internal/streams/readable:390:5)

      at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {

    severity_local: 'ERROR',

    severity: 'ERROR',

    code: 'XX001',

    file: 'bufmgr.c',

    line: '1037',

    routine: 'ReadBuffer_common'

  },

  sql: '\n' +

    '    UPDATE "asset"\n' +

    '    SET \n' +

    '      "width" = CASE\n' +

    `        WHEN "asset_exif"."orientation" IN ('5', '6', '7', '8', '-90', '90') THEN "asset_exif"."exifImageHeight"\n` +

    '        ELSE "asset_exif"."exifImageWidth"\n' +

    '      END,\n' +

    '      "height" = CASE\n' +

    `        WHEN "asset_exif"."orientation" IN ('5', '6', '7', '8', '-90', '90') THEN "asset_exif"."exifImageWidth"\n` +

    '        ELSE "asset_exif"."exifImageHeight"\n' +

    '      END\n' +

    '    FROM "asset_exif"\n' +

    '    WHERE "asset"."id" = "asset_exif"."assetId"\n' +

    '      AND ("asset_exif"."exifImageWidth" IS NOT NULL OR "asset_exif"."exifImageHeight" IS NOT NULL)\n' +

�

,

�
  params: []

}

[Nest] 7  - 02/07/2026, 11:36:45 AM    WARN [Microservices:DatabaseRepository] Migration "1768336661963-AddAssetWidthHeight" failed

[Nest] 7  - 02/07/2026, 11:36:45 AM   ERROR [Microservices:DatabaseRepository] Migrations failed: PostgresError: invalid page in block 602 of relation base/16384/17483

PostgresError: invalid page in block 602 of relation base/16384/17483

    at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:815:30)

    at handle (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:489:6)

    at Socket.data (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:324:9)

    at Socket.emit (node:events:508:28)

    at addChunk (node:internal/streams/readable:559:12)

    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)

    at Readable.push (node:internal/streams/readable:390:5)

    at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {

  severity_local: 'ERROR',

  severity: 'ERROR',

  code: 'XX001',

  file: 'bufmgr.c',

  line: '1037',

  routine: 'ReadBuffer_common'

}

microservices worker error: PostgresError: invalid page in block 602 of relation base/16384/17483, stack: PostgresError: invalid page in block 602 of relation base/16384/17483

    at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:815:30)

    at handle (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:489:6)

    at Socket.data (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:324:9)

    at Socket.emit (node:events:508:28)

    at addChunk (node:internal/streams/readable:559:12)

    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)

    at Readable.push (node:internal/streams/readable:390:5)

    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)

microservices worker exited with code 1

Killing api process

Initializing Immich v2.5.5

Detected CPU Cores: 1

(node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time

(Use `node --trace-warnings ...` to show where the warning was created)

Starting api worker

Starting microservices worker

[ RETIRES]

Additional information

No response

[github-actions[bot]]

This issue has automatically been closed as it is likely a duplicate. We get a lot of duplicate threads each day, which is why we ask you in the template to confirm that you searched for duplicates before opening one. If you're sure this is not a duplicate, please leave a comment and we will reopen the thread if necessary.

[bo0tzz]

Your database is corrupted, you'll want to restore a backup.

[rickythewoof]

I thought that, and in fact I did try and restore an old backup. Right now I am on 2.4.1 and it works correctly, but if I update I get that issue.

[alextran1502]

Which hardware are you hosting Immich on?

[rickythewoof]

Not a particularly beefy one, but does the job! I3-4th gen that hosts proxmox. On top of that I have a Ubuntu LTS VM which has proxmox. The specific containers have been limited so that I don't have any overcommitment

[mmomjian]

You are running proxmox in a VM?

[rickythewoof]

Nope, my config is Proxmox > Ubuntu > Proxmox > Immich stack
Sorry for not being clear

[mmomjian]

Proxmox > Ubuntu > Proxmox > Immich stack

So... yes? Proxmox is running inside a VM (Ubuntu) which is running on Proxmox... this is not a good idea.

[rickythewoof]

Damn so sorry for that
I meant proxmox > ubuntu > portainer > immich.

I just had a severe brain fog