> Well the good news is that if it is booting to a grub prompt, it is most > likely not a > problem with the EFI volume, because it is booting into grub. You just need > to regenerate > the contents of the /boot volume, which most importantly needs a kernel, an > initrd and > some grub configuration files.
Thankyou for having one of the more helpful replies. I understand at least this paragraph, however I'm still quite unsure of the specifics > When booting off rescue media, make sure you boot it as an EFI device. Some > hardware will > default to booting legacy firmware when choosing external media, for some > reason. I believe it is, my BIOS was set to EFI mode, or so I am told. > Check if there is a /sys/firmware/efi/ directory when you’re booted into the > rescue media, > otherwise you won’t be able to update the EFI settings for any new bootloader > you > install. There is, with a collection of files and folders in it. > Most likely the OS didn’t use fedora_crypt as the luks device, so it got hung > up there. > > I wonder if you could check the /etc/fstab for the device name? I could try this, with some more specific instruction on how to do it? I don't recall having a 'device name' so I dont know really how to find it. Is this also done in 'chroot?' > As others have said, it’s missing kernels, so making an initrd is impossible. > > dnf reinstall ‘kernel-*’ > > … should get you back to having all the kernel related packages installed. Starting to have difficulty followiing. I partially recognise this command, but i have no idea where/when to use it, or what the correct result should look like. > It sounds like you only wiped the /boot partition, which should be fairly > easy to get > back. Reinstalling the kernel and grub2 packages will get you the packaged > bits, and > running dracut like you ran should get you the initrd, although only after > you’ve got the > kernel. I dont follow this at all I'm afraid. I understand some of the jargon but I haven't a clue how to practically execute these as working steps. Could you at all possibly boil this down into clear commands and instruction on when to use them, in what order? Otherwise it all just feels like "the solution is to fix the problem, you know how to do that right?' > After everything is reinstalled, then run the grub2-mkconfig command to > create the grub > config file in your new /boot partition. I do recall this! So I should be able to do that last part myself. But I need help with the other steps leading up to it Thankyou for actually helping _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
