Hello Michael, On Tue, 12 Dec 2017 17:12:04 +0000 (GMT) Michael Young <m.a.young@xxxxxxxxxxxx> wrote: > On Tue, 12 Dec 2017, Ted Roche wrote: > > > Booted into Windows 10 to start the annual TurboTax stuff, and it > > asked to do an update, as usual. It turned out the "Features Update" > > was an entirely new version of Windows 10, Fall Creator's Update > > update, or something. > > > > Rebooting to go back into Fedora 25, and the boot menu is gone, replaced with: > > > > grub> > > > > The fedoraproject page above suggests: > > > > grub2-mkconfig -o /boot/grub2/grub.cfg > > > > and > > > > grub2-install --boot-directory=/boot /dev/sda > > > > Finally, my question: are these last two commands correct with all the > > variations of EFI, GPT, LVM, LUKS etc that is my configration? After > > all this, I'd really hate to write to the wrong place! > > For EFI booting the location of grub.cfg is /boot/efi/EFI/fedora/grub.cfg which I am guessing has been corrupted by your Windows 10 update. As your boot gets as far as the grub2 prompt this is probably all you have to fix, eg. > > grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg > > You could write the output of grub2-mkconfig somewhere else first so you can check what it will do before you overwrite anything. eg. > grub2-mkconfig -o /tmp/grub.cfg > > A good place to look for instructions is https://fedoraproject.org/wiki/GRUB_2#Updating_GRUB_2_configuration_on_UEFI_systems > which includes the line > grub2-install shouldn't be used on EFI systems > so I don't suggest you use it. [snip] I've experienced the same here, since then I'm no longer booting into Windows on my (dual-boot) laptop, but fixing it afterwards doesn't seem very satisfying, isn't it possible to prevent Windows from killing other systems from the EFI? How come such situation where Windows can do that? Regards, -- wwp
Attachment:
pgpZxM122dx5e.pgp
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx