Migrating from 1.125.1 to latest -- nightmare
Hello. I am at a loss right now, as after I attempted to migrate to a newer version of Immich, all hell broke loose and I cannot get my old instance back up and running anymore either. Currently, I stored all my data (in truenas scale) on a dataset called echo2/immich. When looking in this dataset, there is a folder with some form of UUID and a few DB backups in tar.gz files.
This file structure is completely different from the one that is shown in the documentation as well as the new version itself. I created a new container with the latest release and attempted to migrate the subfolders in the "UUID folder" over to the library folder, however this didn't yield any results.
I didn't do a GREAT job explaining this, but if anyone can help that would be tremendous. At this point, I just need to get the old files imported into a new instance.
18 Replies
:wave: Hey @Sam Taber,
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
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
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. :ballot_box_with_check: 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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:Here is a screenshot of the echo2/immich dataset. I know that the container / app was set to use the legacy file structure, however this layout does not match anything else i've seen.
That file structure doesn't make any sense. You must have had multiple folders mounted to the same point
It looks like you have both the
backups and upload folder mounted to this folderThat would be correct...
Unfortunate
It looks like I have everything mapped to that one dataset
All the data is "there", but it's a matter of trying to get it into the new Immich dataset correctly. https://cdn.thetabergroup.com/9vani1hfh.png I've checked and verified that going through this migration didn't mess up any of the data (and it did not) however I am unsure as to how to proceed from this point.
Obviously I am going to separate out the mountpoints on the TrueNAS side of things for the new container, but there must be an easier way to migrate this data over to a new instance
It looks like your thumbs, encoded video, and uploads folder are all mixed together
I don't think this is recoverable
Oh man...
It will also not be possible using the TrueNAS app. They only allow the newest version to be installed. Your database is before they 132 migration and it can't be migrated on the current release anymore. So you'd need to use a custom install using docker compose directly.
At this point it's better if I just start over and reload my google photo takeout into immich once more
yep
and then sync my phone back up to it. OK
That's the bad part about TrueNAS, they kinda force you to keep up to date constantly or you get issues
Would you recommend moving it onto a separate management solution e.g. portainer?
I have a portainer environment configured already but figured it was worth the ask.
I switched to portainer at some point, never regret it. It adds control over the version you deploy.
Yeah, I'm not a fan of how TrueNAS handles that. I've never been a big proponent of using the built-in "apps" or running VMs on my NAS for that matter (that's why I have separate compute nodes). I was in a rush and figured "oh good! I can just run it on TrueNAS!"
whoopsie.
Thanks for the help guys. Appreciate it.
This thread has been closed. To re-open, use the button below.