Request for Recovery Plan – Immich Server After External Drive Failure
OS: Ubuntu 24.04.3 LTS
Docker version: 28.4.0, build d8eb465
Immich version: 1.142.0
I am running Immich on an Ubuntu server using the unmodified Docker Compose configuration from the official documentation. My media library, located at UPLOAD_LOCATION/library, was stored on an external drive that has recently failed.
I have a backup of this library, but it is approximately one month old. All folders except UPLOAD_LOCATION/library, including my database, encoded-video/, backups/, profile/, thumbs/ and upload/ directories are stored on an internal drive and remain intact.
It has been two days since the drive failure. I can still browse and use Immich without issues, but I am unable to download original files or view videos. (transcoding is disabled)
I have backups of UPLOAD_LOCATION/library but it is about 1 month old.
I have originals of all media uploaded in this time.
I'm using storage template, and can try to update UPLOAD_LOCATION/library with new media after restoring backup. But I have witnessed earlier that some assets end up outside album dir even while they are in an album. So a manual sort will not be 1:1
Here is my storage template:
{{y}}/{{#if album}}{{album}}/{{MM}}{{else}}{{MM}}{{/if}}/{{filename}}
Could anyone please provide me with a recovery plan to restore my Immich server to its original state, ensuring that it is fully functional?
Thank you
5 Replies
:wave: Hey @AR,
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. :blue_square: 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. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: 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.docker compose ps -a
I have not restarted server, nor immich since the incident
you should probably restore the library/ folder from backup and the matching database backup, and then re upload the missing assets in the last month
it's expected that your backup will have copies of everything, we do not have a set process for resolving discrepancies between the database and filesystem
^ this is the way to go
After that, your #1 priority should be setting up regular automated backups
Thanks to both of you
I realized my backup did not have database backed up 😥