On 1/10/19 11:10 AM, Richard Shaw wrote:
I was able to tie in the Windows created EFI partition and just reinstalled the packages that install all the files instead of moving the files back over... Windows created a "Boot" folder under EFI and Fedora created a "BOOT" folder and I wasn't sure which one to use (or if it mattered).
You have two folders, one named Boot and one named BOOT? That shouldn't be possible because the EFI partition is FAT32 which is not case-sensitive.
On a side note, one problem I had is that grub2-mkconfig produced NO output when running under a chroot. I probably spent a good two hours on that alone which is partially why I gave up and decided to reinstall. After running "ps auf" while it was hung I figured out that it's the vgs call that was hanging. vgs couldn't talk to lvmeatd or whatever it's called. I never really found a direct solution but caught a reference about it not being able to find the runfile in /run so on a whim I added "mount --rbind /run /mnt/fedora/run" and voila, it worked! I've never needed to do that before...
If you just chroot, you won't have access to /dev, /proc, /run, etc. The easiest option is to use a netinstall image and boot into the rescue mode. That will automatically mount all the extra filesystems for you in the chroot. (If you do use that option, you will probably want to remove the /.autorelabel file when you're done, just make sure you have messed up any labels.)
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
