#Trouble upgrading from v1.131.3 to v1.132.3

1 messages · Page 1 of 1 (latest)

restive plinth
#

I am running into issues with the upgrade. I have a working env on v1.131.3 including facial recognition (using an NVIDIA card). However as soon as I go to pull the latest container and start it I have the following error:

immich-db                | 2025-05-13 17:46:28.811 AMERICA [83] STATEMENT:  DROP TABLE IF EXISTS "geodata_places_tmp"
immich-server            | Migration "GeodataCleanup1743611339000" failed, error: could not read block 83 in file "base/16384/2608": read only 0 of 8192 bytes
immich-server            | QueryFailedError: could not read block 83 in file "base/16384/2608": read only 0 of 8192 bytes

Here is a link to more: https://gist.github.com/ravensorb/8ede48139aa50d1fdbae73f43f33cb44

For context, I am using the base compose file with the only changes being the specific image versions (ex: nvidia for ML)

Gist
immich-server error going from v1.131.3 to v1.132.3

immich-server error going from v1.131.3 to v1.132.3 - gist:8ede48139aa50d1fdbae73f43f33cb44

twin ploverBOT
#

:wave: Hey @restive plinth,

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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :blue_square: 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.

versed wyvern
#

looks like your dataabse is corrupted. what storage is it on?

restive plinth
#

that what I though however I have zero issues running v1.131.3 -- can add/remove images, rescan, tag, etc

#

its running against a physical drive

versed wyvern
#

Mounted how? What filesystem pathv

#

It just means those queries don’t touch the broken part

restive plinth
#

/mnt/storage:/upload:rw

versed wyvern
#

OK so that’s not the base compose file

#

So please share everything the bot asked for

restive plinth
#

fair -- forgot I changed the env for the data path

#

update the link above with the compose file

#

also if it helps, can connect with pgadmin and I can run an ANALYZE and it comes back with no errors

#

i'll keep playing

#

thx

versed wyvern
#

please share your .env

restive plinth
#

it looks like in the older version only the thumbnails were still working. So even though the postgress anaylize comes back clean it does look like the database is corrupt. Interestingly, I am not able to restore any backup at all (they all error out with "stream truncated due to process crash". I am going to try starting over clean. Question -- if I do an import via the CLI do I do that from the existing asset folder in uploads? Or do I move everything to a temp folder and then do the upload?