sorry for the late reply, the command ‘lsblk’ can output it:
“sudo lsblk -o +uuid,name”
check “man lsblk” to see all possible combinations if needed.
there is also ‘blkid’ but I’m unsure whether that package is installed by default on all Linux releases, so that’s why I chose ‘lsblk’
if ‘blkid’ is installed, the syntax would be:
“sudo blkid /dev/sda1 -s UUID -o value”
glad you got it fixe, and hope this answers your question
(edit pga big thumbs and autocorrect… )
probably the disk UUID has changed because of the path to the NVMe vs SSD. If you use partition UUID, they will be exactly the same, but the UUID of the physical disk is not cloned, as it is a identifier of the physical device and not it’s content.
change it to partition UUID and it will boot.
or you might be unable to decrypt them at all
or, if it was a LG phone, could they be encrypted?
if so, perhaps this will help https://github.com/kamicater/LG-Gallery-Decryptor
if you have access to a windows computer, or perhaps wine can work?, there might be a solution in the bottom of this thread where someone had a similar problem
https://superuser.com/questions/972013/how-to-repair-corrupt-jpeg-files
haven’t tested it, so do some antivirus checks on the tool before you decide to test it just to be sure.
good luck, hope you get it sorted
one way that works for some is to trick your mind by schedule your worrying to a time and date in the future and tell yourself you will handle it then. this gives you a “solution” for your mind to stop worrying about it now, as you have a plan to do it later…
worked for me quite a few times actually…
good luck, and hope you get it sorted eventually either way.
also, remember that the old drive now share the UUID with the NVMe drive (which is why I recommended using partition UUID and not disk UUID), so you will have to create a new GPT signature on the old drive to avoid boot issues if both drives are connected at the same time during boot, otherwise you might run into boot issues or booting from the wrong drive.