Trying to 'restore' my lxc immich container after a superblock got corrupted on my proxmox
Hi all,
My Proxmox server went down last week due to corrupted superblocks.
I was only able to file-copy the CTs and VMs, not clean backups. Proxmox is freshly reinstalled now and several VMs are working, but my Immich LXC is not.
For Immich, I still have the original rootfs copied from the old LXC, and the Immich data (uploads assets) is on a separate disk — so nothing is lost.
I tried using the community script to recreate the LXC, but it installs Immich 2.2.3, while my old installation was 2.2.0.
I then tried to manually resync the old rootfs into the new LXC, but Immich doesn’t start (no Docker daemon, no services, database not detected, etc.).
At this point I’m unsure what I’m missing — I’m not an expert in LXC internals or Immich’s dependencies — so any guidance on how to properly restore the old LXC rootfs + data, or how to safely migrate everything into a fresh 2.2.3 install, would be really appreciated.
I do have:
The full old /var/lib/lxc/<id>/rootfs file tree.
The Immich data directory (uploads).
In the Immich data directory i do see raw files in a subfolder which contain db backup files. Maybe this can be used ?
But I don’t know the correct way to put everything back together.
Thanks in advance for any help!
3 Replies
:wave: Hey @mretch,
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:
https://immich.app/docs/administration/backup-and-restoreFYI we explicitly do not support the community script as it doesn’t use docker
So you might need to ask them for some help as well
ok thank you. i'm trying there also..