What is the exact error you are getting? With the hard disk only does it find grub and does it display a menu or drop you to the grub> prompt? If it displays a menu and you select one of them what does it then do? The uuid will also be on the kernelopts line, but if that was the error you would have failure to mounted root after the kernel tried to boot. all of the commands would need to be run in the chroot setup (after the chroot . and before exiting chroot-mainly the grub2-mkconfig that updates grub.cfg and the grub2-install for /dev/sda. I would stay away from the centos boot, nothing it can do will be good since you are running a newer grub setup. It is better to use newer livecds than older ones (ie I f27 all of the time to rescue el5/6/7 version and chroot into the actual machine to be fixed environ after mounted it all). On Fri, Apr 23, 2021 at 4:35 PM Michael Hennebry <hennebry@xxxxxxxxxxxxxxxxxxxxx> wrote: > > The grub rescue mode finds only (hd0), no paritions at all. > > On Fri, 23 Apr 2021, Roger Heflin wrote: > > > 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). > > I did stuff in the chroot, but apparently not well. > > > 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? > > I do not understand grub2 configuration files. > sda3/boot/grub2/grub.cfg contains references both to > sda3 and to the Anaconda file system from the F33 live DVD. > I'm running a live Centos 7 right now. > > > 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. > > -- > 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
