v130.1 - All images go to trash every 2nd external library scan
All images are in external lib - via read-only NFS mount from a NAS.
Prior to upgrading I restarted Immich (docker) on v129.1, and ran a rescan. All images still fine.
No changes to compose file.
Upgrade to 130.1 and all images fine. No errors in the log.
Ran a scan, and all images are dumped into 'trash'
In the log:
See first code section below (yeah, I don't know how to embed the file here)
That last line....😑
Validated the import paths - both fine.
Checked my scan settings, and there are NO exclusions present at all (no pattern added).
Logged into the immich_server docker shell and the mounted images were fine/accessible where they should/normally be.
Re-checked my scan settings - made no changes but clicked 'save' again anyway for shits and gigles
Re-ran the scan, and lo-and-behold:
See 2nd code block below.
Re-ran the scan - got the same/first error and all my images are 'trashed' again.
Re-ran the scan - all images are back.
Rinse-and-repeat. Clicking 'save' is unnecessary, just every 2nd scan they are trashed/resurrected.
There's a bug there somewhere.
17 Replies
:wave: Hey @xenmoose,
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. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: 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.What are your exclusion patterns?
I said in the post - I don't have any.
Oh sorry I overlooked that
What are your inclusion patterns? 😅
Don't think I have any of those either....where do you specify them?
Well the import path(s)
/usr/src/app/external/Photos_SSD_NAS
and
/usr/src/app/external/Photos_NAS
Like I said....they show up fine in the docker container - can see all the files just fine.
Also, if I downgrade back to v1.129.1 the problem goes away again.
Can you try escaping the
_, so replace every _ with \_?The path fails validation if I do that.
Hm fair enough
Pretty sure the underscore is the issue though; FYI @etnoy
There'll be another patch release soon-ish anyways; there are some issues with library import and exclusion paths. Apologies!
This is fixed, new release coming soon, stay patient 😎
All good...
Just odd that it's fine again once I rescan, and the breaks on the next one. Never seen that behaviour before.
Also, had this (underscore) setup for many many versions now.
We rewrote library scans this release, they are 10x to 100xv faster
But there was a bug
Yeah, it's definitely like greased lightning compared to before!
Hi, it's fix into 1.130.2 ?
And how do I get all my images out of the garbage can?
Ok fix when I re-run the library scan
Yep, this should be fixed now upon rescan
All fixed. Nice work, guys. 👍