Hashing on iOS loops [beta timeline]
Dear Immich devs,
I am on iOS and Immich 1.139.2 on truenas using the beta timeline, but this problem first appeared on v1.138.
Problem:
Immich is bouncing back and forth between a completed hash-job and a few thousand assets remaining to be hashed. This causes unnecessary power consumption.
Background:
I’ve had previously had problems with hashing taking weeks, which I could overcome by setting the screen lock to „never“ and keeping Immich in the foreground for the day.
During that initial hash run, Immich crashed, as it saturated my phone’s storage. After a restart of the phone and freeing up space. Immich was able to complete the hash job.
Thank you for your work on the beta timeline. It’s a big gem!
9 Replies
:wave: Hey @kxv,
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. :blue_square: 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.Screenshots
Crash screenshot .
How it looks after it’s completed the hash job.
How it looks after it’s forgotten the last few thousand hashes.
We have identified a possible case where the hash data might be lost for already hashed assets. We are discussing internally on how efficiently to handle this. This is definitely on our radar
Thank you for getting back so quickly.
Do you need my logs or other data?
Not at the moment, thanks 🙂 If you still face the issue after we fix the existing bug, we can troubleshoot it further
I think that this is happening to me too. I’ve been running Immich for a year now probably but now it has only hashed 16000 out of 37000 images and it doesn’t seem like it will ever finish as it only goes up a few every time I open the app
Is there a git issue for this that I can track?