CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
remove all drives but the one can't get to boot
make sure legacy is disable in bios
boot from the rescue usb
run the following commands
Code:
vgchange -a y
mount /dev/mapper/centos-root /sysimage
mount /dev/sda2 /sysimage/boot
mount /dev/sda1 /sysimage/boot/efi
mount --bind /dev /sysimage/dev
mount --bind /proc /sysimage/proc
mount --bind /sys /sysimage/sys
mount -o bind /run /sysimage/run
chroot /sysimage
grub2-install /dev/sda
grub2-mkconfig -o /boot/grub2/grub.cfg
with whatever console text editor you want to use
put a # in front of every line in /etc/fstab except for the following
remove all drives but the one can't get to boot
make sure legacy is disable in bios
boot from the rescue usb
run the following commands
Code:
vgchange -a y
mount /dev/mapper/centos-root /sysimage
mount /dev/sda2 /sysimage/boot
mount /dev/sda1 /sysimage/boot/efi
mount --bind -o /dev /sysimage/dev
mount --bind -o /proc /sysimage/proc
mount --bind -o /sys /sysimage/sys
chroot /sysimage
grub2-install /dev/sda
grub2-mkconfig -o /boot/grub2/grub.cfg
with whatever console text editor you want to use
put a # in front of every line in /etc/fstab except for the following
As for the bios, I'm not sure what you mean by legacy. The UEFI setup is a bit strange. Here is the manual, and I think what you're looking for is on page 87:
Legacy usually is the non-uefi boot option. It's the old way.
Ya that is/was confusing because there's reference in the UEFI boot menu (F2). I don't think I've seen any legacy BIOS boot window. Only setting the UEFI back to defaults is what brought back other drives, which was the Legacy Only option in the drive options. .
on your system it is called csm under the boot screen. Leave as is for now, will change later if needed.
I edited the mount commands in post #16, I add a mount command and removed some of the -o
OK, progressing with this:
Everything worked up until...
Code:
grub2-install /dev/sda
Installing for i386-pc platform
grub2-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding wont' be possible.
grub2-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
grub2-install: error: will not proceed with blocklists.
Note: this is a 64-bit machine. Previously I had to open up DHCP on the ethernet nic and install some grub package when chrooted.
You booted the usb in csm mode and not efi mode. Disabling csm in bios will prevent this. Page 86 in your manual
you may be able to just run the grub2-mkconfig after editing the /etc/fstab
Last edited by colorpurple21859; 10-06-2019 at 04:33 PM.
OK, everything seems fantastic so far. Everything mounted, and I shoved in two other volumes previously formatted. So far so good. Now to see if the backup crons work and I'm golden.
I'll be monitoring, but again, thank you for all the help.
I suspect it was a combination of your fstab and your grub.cfg causing the problem
Yeah the movement of partitions and reassignment meant a new grub.cfg build, I'm guessing. My fstab was from the previous setup. Then the whole confusion about legacy bios in the UEFI...what a mess. 4 layers of confusion. But it's all documented now and apparently good to go, with a much better understanding.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.