Created attachment 188495 [details] A picture of the albums tree cleared SUMMARY No more pictures are listed in my library. This is the second time. The first time *everything* was lost. Whis time, root albums are still listed. When I look inside the database, everything is still there (was the same thing last time). STEPS TO REPRODUCE 1. Unknown OBSERVED RESULT Files are missing EXPECTED RESULT Files be there SOFTWARE/OS VERSIONS digiKam: 8.8.0 KDE Frameworks: 6.17.0 Qt: Using 6.9.1 and built against 6.9.1 Windows 11 Version 25H2 Build ABI: x86_64-little_endian-llp64 Kernel: winnt 10.0.26200 ADDITIONAL INFORMATION My database is local but my pictures are on a remote NAS through SMB share path.
Well, the collection can no longer be found. We identify a network collection using a UUID file located in the collection root directory, specifically in the ".dtrash" folder. If this file is missing, digiKam can no longer identify the collection. To fix this, run the "Update" function in the digiKam settings under Collections. Next to the relevant collection, you'll find a tool button with a circular icon. You can confirm all dialog boxes without making any changes, but make sure the path to your image collection is correct. After that, the collection will be back online. It is recommended to back up the digikam4.db database beforehand by making a copy. Maik
The file was still in there, the network path is available. I did what you said but I still have 0 everywhere. What could make the collection not be found if the file is there and the path is accessible?
After digging a bit more into the database, it is weirder than I thought... In the Albums table, only the root albums are present. In the Images table, all images have there album column set to null except for a couple in the 1 album (/). What could have flushed all this data?
database is sqlite or mariadb/mysql ?
The database is SqlLite but I'm considering moving to MariaDB on my Synology NAS (DS1819+) it it could help in the future.
Please create a DebugView log so we can see if the collection is available for digiKam. The log should start from the beginning of digiKam's startup. A few NULL albums in the database are not an error. https://www.digikam.org/contribute/#windows-host Maik
Created attachment 188647 [details] DebugView log from start of DigiKam process Here is the log. I hope you could see something interesting in there... As for the images with a null album, though I may understand a few, I doubt 1.2M is a few ;) Talking about the DB, when are the .wal files supposed to merge?
Everything looks good; the collection should be available and marked without a red X. Please create such a log in case of an error. SQLite manages the *.wal files itself. A forced merge would only be possible using a vacuum command. Maik