if you are doing the grub-install/grub2-mkconfig from inside the chroot then it should find the correct uuid (if it works like it should). any of the test commands for grub need to be in the chroot otherwise they will think they are the livecd and not do the right thing or show the right thing as they will attempt to setup/look at install for current booted image. Did you check to see if the uuid listed in /boot/grub2/grub.cfg root uuids (sda3 that contains the /boot directory) matches what tune2fs -l /dev/sda3 's uuid? Since you are booting from a partition that uuid may also be on the kernel boot line(s) similar to root=<XXXX> and that will also need to be sda3's uuid. It may also be in grubenv rather than directly on the boot lines. The biggest change you seem to have made is changing the boot/rootfs'es uuid and grub seems to stick that in multiple places in its config files and on the kernel boot lines (in addition to the the fstab you knew about). And it does not appear that grub expects the uuid to ever change and so nothing outside of the grub2-mkconfig command redoes that, it it still may not rewrite to root= line on the kernelopts line. On Fri, Apr 23, 2021 at 3:51 PM Michael Hennebry <hennebry@xxxxxxxxxxxxxxxxxxxxx> wrote: > > On Fri, 23 Apr 2021, Roger Heflin wrote: > > > I assume it is still not bootable. > > > > But if the windows system is gone and you don't care about it, then I > > would set sda3 to be bootable. > > Did that. Forgot to mention it. > > > rescue it and then grub-install /dev/sda3 but make sure the newuuid is > > I've read that I need --force to grub2-install onto a partition. > IIRC grub rescue did not find any partitions. > Live F33 has no trouble. > > > in both fstab (you have done that I think) and matches what is in the > > /boot/grub2/grub.cfg. if a different value is in the grub.cfg file > > then you can either make the actual fs uuid match that and update > > fstab to match, or edit the grub.cfg file that it says do not edit (I > > would think the grub2-install would fix that but it appears another > > command might be required for that--see below). > > The UUID not found is used by the F33 live DVD. > Changing sda3's UUID to that seems a bad idea. > > > I did a test and it looks like this will update the grub.cfg file and > > it should use the new uuid, try it and see if it uses the correct uuid > > and verify the old file did not have the correct uuid. > > > > grub2-mkconfig -o /boot/grub2/grub.cfg <save a copy of it first> > > -- > Michael hennebry@xxxxxxxxxxxxxxxxxxxxx > "Sorry but your password must contain an uppercase letter, a number, > a haiku, a gang sign, a heiroglyph, and the blood of a virgin." > -- someeecards > _______________________________________________ > 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 on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
