https://bugs.kde.org/show_bug.cgi?id=500445
--- Comment #12 from David <ticedo...@hotmail.com> --- [SOLVED] The issue is resolved. It was caused by the disk being full, and the solution was to move the database to the RAID5 (with 10TB free). Details: By default, when the "Network Database" is enabled on the WD PR4100, it will use a small partition of one drive that is left over after a larger 4-drive RAID5 is created. The "solution" was to stop the MariaDB service (using the PR4100 AdminGUI and turning off the "Network Database"), then SSH into the PR4100 and look for the folder .@database@ on one of the 4 drives (/mnt/HD_(a,b,c,d)4). Then use mv (move) command to move that folder to the protected RAID5 mount (/mnt/HD/HD_a2). After that, make a link in the original location (EG: /mnt/HD_b4) to the new location (/mnt/HD/HD_a2/.@database@) and re-enable the "Network Database" option in the AdminGUI. digiKam now starts with no warnings. However, while the entire list of Albums is displayed, not all of them have picture previews. phpMyAdmin Status shows network traffic and what appears to be reads. And on digiKam it looks like it is rescanning the Collections (maybe to fill in the missing entries that got skipped when the database ran out of space the 1st time). -- You are receiving this mail because: You are watching all bug changes.
