Thierry de Coulon via tde-users composed on 2025-05-02 17:02 (UTC+0200):
I know this is not a TDE problem, but as some here know much more than I do:
I am trying to clone a 256GB SSD to a 512Gb one. I did clone the disk, but O can't bott directly (I get a grub prompt).
So I boot to my system fom a USB install thumbdrive, and try to reintsall grub. This is (I think) a grub-efi system (it has a win11 partition that I unfortunately have to keep and is GPT formatted).
The error message I get is: grub-install error: cannot copy '/usr/share/locale/fr.gmo' to '/boot/grub/locale/fr.mo': Is a directory
And all my searches return nothing about this error message.
When I have time (this summer), I can do a complete reinstall but maybe someone here understands more about it and can give a clue?
Your error message is not a familiar one, but cloning I am quite familiar with, though less so with GPT, and none at all with Windows as part of a UEFI system (which should not matter).
A UEFI BIOS follow-up is normally required after a disk switch resulting from cloning, though conceivably it could work OK if after the cloning, both source and target were never in the system at the same time again. Kernels are not designed to handle duplicated UUIDs or LABELs.
Linux has tool efibootmgr for managing boot entries in UEFI. Obsolete ones need to be removed, and new ones created for best results. Grub's job is significantly different in UEFI. Re-installing it doesn't apply. Attempting to re-install it can make trouble worse. Reconfiguring it may, and probably should, apply, to enable both source and target in same system in same boot after cloning has been completed; *along with* re-uniquing UUIDs and volume LABELs everywhere used, e.g. UEFI BIOS, fstab, grub.cfg, /etc/default/grub/ and if applicable /etc/grub.d/.
At least once after a clone/disk replacement here, booting didn't succeed until I added one or two additional parameters to the linu line(s) in grub:
rd.hostonly=0 rd.auto=1
Their discovery as possible solution is recorded in: https://bugzilla.opensuse.org/show_bug.cgi?id=1205261 Reading this bug could be helpful in general for this situation.