System integrity feature

Hi. I was wondering if the return of a "repair" page for system integrity checking (i.e., an integrity check between database pages and files on the file system) is planned before the stable release of immich. I'm wondering because I saw it mentioned a while ago, but it's not listed as a milestone on the roadmap. I'm attaching some links to clarify the feature I'm referring to: https://github.com/immich-app/immich/issues/12293 and https://v1.120.2.archive.immich.app/docs/administration/repair-page/
4 Replies
Immich
Immich3d ago
:wave: Hey @Protenix, 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. :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. [Issue] System integrity feature (immich-app/immich#12293)
bo0tzz
bo0tzz3d ago
nope
Protenix
ProtenixOP3d ago
So even when the stable version of immich arrives, there won't be any certainty of database and filesystem integrity? For servers that have been running for a long time, with updates spanning multiple releases and many assets, there could be accumulated errors for various reasons (bugs, hardware problems, etc.), and users might not be aware that their library isn't fully intact. Is there a roadmap for this critical feature?
Zeus
Zeus3d ago
Any updates would be in the linked issue above. There is not set ETA In general if you don’t do “weird” stuff to your instance it shouldn’t be just accumulating corruption, but we do want a better tool down the line

Did you find this page helpful?