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.
I installed Windows 10 first, then installed CentOS 7. I don't think CentOS overwrote the windows partition. But there is no option to boot windows. I have the option of booting centos, or centos.
I found no option to configure a bootloader during the centos installation.
That looks like a MBR (aka MS-DOS) partition table. So non-UEFI, non-gpt - I didn't think retail versions of Win10 allowed that.
Check your firmware (i.e. BIOS) screens and make sure EFI mode is selected - not CSM (legacy) mode. Then erase the disk and re-install every thing again from scratch.
That looks like a MBR (aka MS-DOS) partition table. So non-UEFI, non-gpt - I didn't think retail versions of Win10 allowed that.
Check your firmware (i.e. BIOS) screens and make sure EFI mode is selected - not CSM (legacy) mode. Then erase the disk and re-install every thing again from scratch.
OP already installed windows that way (I think). So it worked first. But OP will explain it.
would be nice to see the detailed info about those partitions (like size). Windows needs an efi partition, probably that's why it cannot be booted. What is sda4?
# grub2-mkconfig -o / boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.10.0-1160.el7.x86_64
Found initrd image: /boot/initramfs-3.10.0-1160.el7.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-1495fd8baa4e4037ace10e1effc2d33a
Found initrd image: /boot/initramfs-0-rescue-1495fd8baa4e4037ace10e1effc2d33a.img
Found linux image: /boot/vmlinuz-0-rescue-f88f9bcae7074473912b27834c137add
Found initrd image: /boot/initramfs-0-rescue-f88f9bcae7074473912b27834c137add.img
/usr/sbin/grub2-mkconfig: line 290: /: Is a directory
Line 290: cat ${grub_cfg}.new > ${grub_cfg}
In context: (lines 279 to 293 of /usr/sbin/grub2-mkconfig):
Code:
if test "x${grub_cfg}" != "x" ; then
if ! ${grub_script_check} ${grub_cfg}.new; then
# TRANSLATORS: %s is replaced by filename
gettext_printf "Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
%s file attached." "${grub_cfg}.new" >&2
echo >&2
exit 1
else
# none of the children aborted with error, install the new grub.cfg
cat ${grub_cfg}.new > ${grub_cfg}
rm -f ${grub_cfg}.new
fi
fi
Last edited by walterbyrd; 02-15-2022 at 11:22 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.