Digikam can't find my photo images

[Bill Allen]

Why does the uuid of the driver matter? If you've got a unix style file system, then /a/b is the same irrespective of what uuid the underlying drive is, right? If I go out and buy a new hard drive and laboriously recreate the file system on it, shouldn't that just work? Or, am I missing some dependency that isn't obvious?

On Thursday, September 7, 2023 12:34:19 (-04:00), Gilles Caulier wrote:

> Hi,
> 
> I also experienced this kind of problem under MAcOS after a major update.
> 
> I identified a file system update and a change of the disk UUID. This
> is Apple, the user do not know the low level operations done in the
> background.
> 
> Gilles Caulier
> 
> Le jeu. 7 sept. 2023 à 17:57, Bill Allen <dk at ballen.fastmail.fm> a écrit :
> >
> > I answered my own question.
> >
> > The following fixed it:
> >  <back up digikam.db>
> > sqlite3 digikam.db
> > > update AlbumRoots set identifier = 'volumeid:?uuid=4FA9....' where id = 1;
> > I suspect that a recent macos update force the encryption of local volumes. I further suspect the drives were relabeled at that point. At any rate, all appears well.
> >
> > On Thursday, September 7, 2023 11:22:57 (-04:00), Bill Allen wrote:
> >
> > > System is macos, digikam installed with homebrew. Everything normally works great, but at times which I believe are associated with system updates, digikam can no longer find my album. This has happened in the past, and I've been able to correct it, but it's been a while and either I can't remember how I did it (it seems like it was as simple as telling digikam where the files are at the startup dialog, but this time that didn't help) or something else is wrong. The files are there, I can look at them using normal file utilities.
> > >
> > > Using sqlite3, I looked at the table AlbumRoots and everything looks correct except the identifier field which has "volumeid:?uuid=5908...", where when I look at the macos disk utility, I see that my local hard drive has a uuid "4FA9......". Is this the problem? If so, how can I fix it without triggering a full rescan of my photos? If that isn't the problem, where can I look to fix it?
> > > Best regards,
> > > Bill
> > >
> > >
> > >
> >
>