@synthgal looks fine to me assuming you're using redhat or equivalent

@synthgal hm, you can probably ignore those, grub only looks for files with a number in front of them IIRC

Probably best to keep to the guide, the one who wrote that knows more than I do about it

@troubleMoney christ, I think this guide assumes I have a network connection because I have to yum stuff :D

@troubleMoney okay hopefully last question

since I'm using centos and not redhat, would I change /boot/efi/EFI/redhat/grub.cfg to /boot/efi/EFI/centos/grub.cfg?

Other grub guides explicity for centos do it this way but it's a deviation from the repair guide

@troubleMoney well that seemed to do nothing at all.

the rescue mode had me chroot to mount my partition, that woun't change anything?

@synthgal hang on, rescue mode? I thought you were just doing a reinstall

Okay that changes things substantially, sorry, should have realised that was what was going on

What's the current situation when you boot?

@troubleMoney the CentOS installation disk emergency shell is where I'm trying to do this from

@synthgal okay, cool, so you're chrooted in to your centos install? If you're not, then do so

then you'll want to do "/sbin/grub-install /dev/[your hard disk]", your hard disk will be in the form of hda or sda or something similar

After that check that there isn't anything obviously wrong in the /boot/grub/grub.conf file and reboot, that should fix it

@troubleMoney grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory

Follow

@synthgal cool, if you try /sbin/grub-install /dev/[whatev] again it should hopefully find that file

Β· Β· 0 Β· 0 Β· 0

@troubleMoney just to be clear, I want /dev/sda, not /dev/sdaX? isnt GRUB supposed to be in that boot partition with EFI?

@synthgal yeah, /dev/sda rather than /dev/sdaX

You want it in the master boot record of the disk you're booting from

@synthgal Sorry, that's probably GPT rather than MBR these days

You want the bootloader on the drive you're using rather than in a partition is the long and short of it

@troubleMoney ugh my brain always mixed up GPT and UEFI for some annoyign reason, running now

@synthgal It's been a while since I mucked around with bootloaders and stuff, I keep remembering the older commands for things

@troubleMoney wait hang on new grub uses gruf.cfg, but thats the one with a bunch of code I dont understand

@synthgal oh yeah, course, that's me remembering old stuff

I think it should be fine with the defaults so try rebooting to see if it's fixed, if not it won't do any damage and we can go from there

@troubleMoney lol I typed a thank you from my desktop but forgot to hit send and went to dinner whoops

Anyway I'm back in action! Thank you so much!!!!

@synthgal heh, hey, no problem at all, my brain needed a bit of working today anyway

@troubleMoney I did everything I was supposed to in rescue/emergency/whatever mode before EXCEPT grub2-efi-modules because nobody ever mentioned I would need that for EFI in any guides!

I think I might email the guide author I found (which was for CentOS 7 so it should be current!) and tell them the extra steps they should add for EFI users.

@synthgal yeah, that bit is not at all well documented

I found it in a 2015 bug report in redhat's bugzilla and it doesn't seem to be written down anywhere else

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!