I have BIOS, not UEFI.
On Fri, 23 Apr 2021, Roger Heflin wrote:
I am not sure which it needs. If it did not stop windows from
booting then it may have updated the wrong thing.
Windows will not boot either.
Try /dev/sda3 it will either work or give you an error in my experience.
From what I have read,
it will refuse or not depending on whether
it gets a --force argument or some such.
What OS does the main boot loader come from and/or is the machine EFI?
Something in the main boot loader will be pointing to sda5 still I
would guess. I have not had any dual boot machines so I don't know
much about how that works.
I believe that before I fiddled with it,
the bootloader had come from the F33 install/live disk.
If it is dropping to the grub shell that is a sign that it did not
find the /boot partition or nothing is on the /boot partition and/or
the config files and such. So it is finding grub but not /boot, but
it is not clear if this is the sda3 grub or the sda5 grub.
It complains about not finding UUID 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a .
At the moment blklid tells me
/dev/loop1: LABEL="Anaconda" UUID="2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a" BLOCK_SIZE="4096" TYPE="ext4"
I'm running the F33 live/install disk.
ot@localhost-live liveuser]# mount /dev/sda3 /mnt
[root@localhost-live liveuser]# cd /mnt
[root@localhost-live mnt]# ls
bin etc lib lost+found mnt2 root srv usr
boot home lib64 media opt run sys var
dev label.txt local3slash.mt mnt proc sbin tmp
[root@localhost-live mnt]# grep -n -r -F 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a boot
boot/grub2/grub.cfg:67: search --no-floppy --fs-uuid --set=root 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
boot/grub2/grub.cfg:69: search --no-floppy --fs-uuid --set=root 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
boot/grub2/grub.cfg:124: search --no-floppy --fs-uuid --set=root 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
boot/grub2/grub.cfg:126: search --no-floppy --fs-uuid --set=root 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
boot/grub2/grub.cfg:130: search --no-floppy --fs-uuid --set=boot 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
boot/grub2/grub.cfg:132: search --no-floppy --fs-uuid --set=boot 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
boot/grub2/grub.cfg:151: set kernelopts="root=UUID=2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a ro "
[root@localhost-live mnt]#
A similar search on sda5 turns up empty.
The first six are all part of the following construct:
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
else
search --no-floppy --fs-uuid --set=root 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
fi
Except for a blank, the two lines are identical.
I suspect this is a result of automation.
--
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
