System integrity folder checks not passing after restoring from backup
Hi, I moved my Immich server from a dedicated server onto my Synology NAS using it's Docker / Container manager.
Restoring the database from a backup worked well and all files where moved from the old host to the NAS, too.
However the immich_server container is stuck in a loop because folder checks are not passing. Specifically currently it logs that <UPLOAD_LOCATION>/encoded-video is not passing (so it says the .immich file is missing).
The file itself however is there:
I also tried adding
user: 0:0 to immich_server so it starts with root, but this doesn't change anything.
I then did id -u brayd which is 1026 and id -g brayd which is 100 and changed the user attribute in the docker file to: user: 1026:100 but I still get the error.
My current docker file is: (Pastebin because it's too long for Discord) https://bin.disroot.org/?f6503601167eea57#53Pij6TRqeUg21CVDLaEYESK1kfhayQWvJnPnV6MYmA
Any ideas why the integrity check fails?
I also attached a screenshot with the log itself.Disroot Bin - Encrypted pastebin by PrivateBin
Encrypted note on Disroot Bin - Encrypted pastebin by PrivateBin
Visit this link to see the note. Giving the URL to anyone allows them to access the note, too.
5 Replies
:wave: Hey @Noryb 🤓,
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:Interestingly it seems like the Immich container is only mounting the upload directory but not the rest. But not sure if that is connected to the integrity checks.
how is UPLOAD_LOCATION defined?
looks to me is mounting your library folder
Yes just saw it because on my previous host it was using ./library and the host path was
Just changed it on the new host to /volume1/Immich so the absolute path...currently restarting
Yes, that fixed it 😄 Thank you!
This thread has been closed. To re-open, use the button below.