Repository navigation
Replies: 1 comment 1 reply
|
Logs are missing, and you have a circular loop in your libraries (internal library is nested within external) |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
The bug
Version
Immich v3.0.3
Platform
Description
I think I have found an issue with External Library recovery.
At some point my external storage became temporarily unavailable.
After that, almost all External Library assets were moved to Trash.
The storage is now fully available again.
I verified all of the following:
The scan result is:
174,576 unchanged
0 updated
0 offlined
However, all of those assets still appear in the Trash in the web UI.
Restore does not work
If I select assets in Trash and click Restore:
0 assets restored
No error is displayed.
If I click Restore All:
0 assets restored
Again, no error.
However, Permanently Delete works normally.
Database status
I checked the PostgreSQL database.
Almost every asset in Trash is an External Library asset.
deletedAt IS NOT NULL
isExternal = true
isOffline = true
status = active
The
originalPathvalues are correct and point to the current External Library location.What I've already tried
Expected behavior
After the storage becomes available again and Library Scan completes successfully,
I expect the External Library assets to automatically leave the Trash.
Actual behavior
Is this a known issue in v3.0.3?
SELECT COUNT(*)
FROM asset
WHERE "deletedAt" IS NOT NULL
AND "isExternal" = true;
349119
SELECT COUNT(*)
FROM asset
WHERE "deletedAt" IS NOT NULL;
349132
If necessary, I can provide database queries, logs, or Docker configuration for further investigation.
The OS that Immich Server is running on
Rasobyrry PI OS
Version of Immich Server
v3.0.3
Version of Immich Mobile App
v3.0.3
Platform with the issue
Device make and model
iPhone 16 pro
Your docker-compose.yml content
Your .env content
Reproduction steps
...
Relevant log output
Additional information
No response
All reactions