Dear Tim,
Although yours advice seems good unfortunately firstly the keyboard becoming English from a keyboard azerty and secondly a lot of line of command don't work as nano too pwd in addition blkid and locate however I understand how to press another
button because the keyboard is become English also I can't use the touch dot and the touch slash finally I think wait when the setup will become more smart for the repair by myself,
Thanks you Tim,
I wish a good week at the team fedora,
Regards.
Dorian Rosse.
From: Tom Horsley <horsley1953@xxxxxxxxx>
Sent: Monday, April 17, 2023 3:47:43 PM
To: users@xxxxxxxxxxxxxxxxxxxxxxx <users@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Broken by the grub startup after have move whole the system from one SSHDD more small to a SSD more big by a software acronis
Sent: Monday, April 17, 2023 3:47:43 PM
To: users@xxxxxxxxxxxxxxxxxxxxxxx <users@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Broken by the grub startup after have move whole the system from one SSHDD more small to a SSD more big by a software acronis
There are disk UUID values scattered around in all sorts of grub files
as well as (probably) the /etc/fstab file. You need to find and fix
all of those to use the new disk uuid.
Boot off a live image to get a working system, run blkid to get the
uuid values for the new disk then mount the new drive and edit the uuid
values in (at least) these file on the new disk:
boot/grub2/grub.cfg
bool/loader/*.conf
etc/fstab
If you have a UEFI system, the files to edit may be different than
just the ones I listed.
If you have selinux enabled, you may need to force a complete relable
(which I don't know how to do, but I know there is some way)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
as well as (probably) the /etc/fstab file. You need to find and fix
all of those to use the new disk uuid.
Boot off a live image to get a working system, run blkid to get the
uuid values for the new disk then mount the new drive and edit the uuid
values in (at least) these file on the new disk:
boot/grub2/grub.cfg
bool/loader/*.conf
etc/fstab
If you have a UEFI system, the files to edit may be different than
just the ones I listed.
If you have selinux enabled, you may need to force a complete relable
(which I don't know how to do, but I know there is some way)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
