#Migrating from old datasets to new

1 messages · Page 1 of 1 (latest)

primal wedge
vague hemlockBOT
#

:wave: Hey @primal wedge,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :ballot_box_with_check: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

primal wedge
#

Recently upgraded my truenas from 24.04 to electric eel and followed all the steps to rsync over all my immich to the new dataset however nothing is showing on launch

primal wedge
#

when trying to use the old storage configuration or keep the existing datasets instead of new ones, I get the 2025-09-14 03:57:14.693100+00:00microservices worker error: PostgresError: password authentication failed for user "immich", stack: PostgresError: password authentication failed for user "immich"
2025-09-14 03:57:14.693149+00:00at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/[email protected]/node_modules/postgres/cjs/src/connection.js:794:26)
2025-09-14 03:57:14.693157+00:00at handle (/usr/src/app/server/node_modules/.pnpm/[email protected]/node_modules/postgres/cjs/src/connection.js:480:6)
2025-09-14 03:57:14.693169+00:00at Socket.data (/usr/src/app/server/node_modules/.pnpm/[email protected]/node_modules/postgres/cjs/src/connection.js:315:9)
2025-09-14 03:57:14.693175+00:00at Socket.emit (node:events:519:28)
2025-09-14 03:57:14.693180+00:00at addChunk (node:internal/streams/readable:561:12)
2025-09-14 03:57:14.693190+00:00at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
2025-09-14 03:57:14.693196+00:00at Readable.push (node:internal/streams/readable:392:5)
2025-09-14 03:57:14.693201+00:00at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-09-14 03:57:14.704892+00:00microservices worker exited with code 1
2025-09-14 03:57:14.704944+00:00Killing api process

primal wedge
#

I tried running the rsync fresh and now gtting: failed to set times

#

operation not permitted

lone hound