y0din

you’re welcome :)

or since you probably are from Denmark since you mentioned Danish in your other comments:

🇩🇰 bare hyggelig, og håper du fikk løst problemet ditt 🇳🇴

thank you :)

not to be that guy . but have you tried to search for an answer?

https://github.com/flatpak/flatpak/issues/4435

first hit on “flatpak question marks”… it’s due to the font you use in the terminal does not support or not fully support Unicode characters or your locale settings are not correct.

hope this helps and answers your question :)

(edit, lost part of a sentence)

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.

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.