I have a laptop with windows 10.
I went into the Windows disk manager and shrunk the volume
to make room for C7. That worked.
I also changed the BIOS from secure boot to "both" (secure/legacy)
I installed C7, went fine. About the time it was done I realized I never
saw anything about "other" boot options (seems I saw that in the
past).
Anyway sure enough, got done and C7 boots fine - no option there for
Windows. I did searching and found I needed to add to the
/etc/grub.d/40_custom the following:
menuentry "Windows 10" {
set root='(hd0,1)'
chainloader +1
}
then re-run the grub2-mkconfig -o /boot/grub2/grub.cfg
I then rebooted and sure enough I got the menu item for "Windows 10"
however when I select it it does not boot.
How do I get Windows 10 to boot again ?
Thanks,
Jerry
> Date: Tuesday, April 19, 2016 07:42:44 -0400 > From: Jerry Geis <geisj at pagestation.com> > > I have a laptop with windows 10. > I went into the Windows disk manager and shrunk the volume > to make room for C7. That worked. > > I also changed the BIOS from secure boot to "both" (secure/legacy) > > I installed C7, went fine. About the time it was done I realized I > never saw anything about "other" boot options (seems I saw that in > the past). > > Anyway sure enough, got done and C7 boots fine - no option there for > Windows. I did searching and found I needed to add to the > /etc/grub.d/40_custom the following: > menuentry "Windows 10" { > set root='(hd0,1)' > chainloader +1 > } > > then re-run the grub2-mkconfig -o /boot/grub2/grub.cfg > > I then rebooted and sure enough I got the menu item for "Windows 10" > however when I select it it does not boot. > > How do I get Windows 10 to boot again ? > > Thanks, > > JerryOn my laptop, with windows-7, I have two differences. set root=(hd0,2) not ... "(hd0,1)". I also don't have quotes, as you show, around that. insmod ntfs between the "menuentry" and "set root" lines. Exactly where your windows partition lives may vary, so you may need to play with that a little.
Thanks... I added the "insmod ntfs" re-ran config no boot... I change the hd1 to hd3 re-ran config no boot... This is what my partition table looks like. # Start End Size Type Name 1 2048 534527 260M EFI System EFI system partition 2 534528 567295 16M Microsoft reser Microsoft reserved partition 3 567296 525326335 250.2G Microsoft basic Basic data partition 4 998166528 1000214527 1000M Windows recover Basic data partition 5 525326336 525330431 2M BIOS boot parti 6 525330432 965732351 210G Microsoft basic 7 965732352 982509567 8G Linux swap Thoughts? jerry
On Tue, Apr 19, 2016 at 08:34:51AM -0400, Jerry Geis wrote:> Thanks... > > I added the "insmod ntfs" re-ran config no boot... > I change the hd1 to hd3 re-ran config no boot... > > This is what my partition table looks like. > > # Start End Size Type Name > 1 2048 534527 260M EFI System EFI system partition > 2 534528 567295 16M Microsoft reser Microsoft reserved > partition > 3 567296 525326335 250.2G Microsoft basic Basic data partition > 4 998166528 1000214527 1000M Windows recover Basic data partition > 5 525326336 525330431 2M BIOS boot parti > 6 525330432 965732351 210G Microsoft basic > 7 965732352 982509567 8G Linux swap > > Thoughts?On Centos 7, the NTFS filesystem is not installed by default. Make sure you have ntfs-3g and ntfsprogs both installed. You'll need to configure the epel repo before you can install them. Fred -- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us ----------------------------- But God demonstrates his own love for us in this: While we were still sinners, Christ died for us. ------------------------------- Romans 5:8 (niv) ------------------------------
Hi All, Partition 5 is what the linux partitioning add... Partition 6 is LINUX - Why it shows up as Microsoft Basic I dont know. Partition 7 is the normal swap I have tried booting partition 1 and it says. "an operating system wasnt found." When booting partion 3 I get a screen "WINDOWS BOOT MANAGER" windows failed to start. A recent hardware change might the cause it wants a wnidwos install disk and says FILE: \Boot\BCD status 0xc0000225 Thoughts? Jerry Jerry
On Tue, Apr 19, 2016 at 5:42 AM, Jerry Geis <geisj at pagestation.com> wrote:> I have a laptop with windows 10. > I went into the Windows disk manager and shrunk the volume > to make room for C7. That worked. > > I also changed the BIOS from secure boot to "both" (secure/legacy)Both is a problem. There's no practical way for an installer to support both. Basically it makes the computer UEFI for Windows and BIOS for CentOS 7 instead of UEFI for both.> > I installed C7, went fine. About the time it was done I realized I never > saw anything about "other" boot options (seems I saw that in the past). > > Anyway sure enough, got done and C7 boots fine - no option there for > Windows. I did searching and found I needed to add to the > /etc/grub.d/40_custom the following: > menuentry "Windows 10" { > set root='(hd0,1)' > chainloader +1 > } > > then re-run the grub2-mkconfig -o /boot/grub2/grub.cfg > > I then rebooted and sure enough I got the menu item for "Windows 10" > however when I select it it does not boot. > > How do I get Windows 10 to boot again ?You'll have to use the firmware's boot manager. The legacy mode enables a compatibility support module (CSM) so that UEFI presents a faux-BIOS to the operating system, Cent OS in this case. So Cent OS thinks it's on a BIOS system, and installs a BIOS based bootloader. A BIOS bootloader cannot chainload a UEFI bootloader. What you should revert back to UEFI only, with Secure Boot enabled, and reinstall CentOS, deleting the previous partition/mount points including the BIOS Boot partition that was created for CentOS's bootloader. The gotcha is that with Secure Boot enabled, the CentOS GRUB-efi package doesn't support chainloading the Windows bootloader. This is getting fixed in Fedora 24 but I have no idea how long it'll take to get to CentOS 7. You could either disable Secure Boot (which I don't recommend) or you switch between CentOS and Windows using the firmware's boot manager. You'll have to figure out which F key brings up the boot manager. On my Intel NUC it's F10, *shrug*. -- Chris Murphy
Chris Murphy wrote:> What you should revert back to UEFI only, with Secure Boot enabled, > and reinstall CentOS, deleting the previous partition/mount points > including the BIOS Boot partition that was created for CentOS's > bootloader.> The gotcha is that with Secure Boot enabled, the CentOS GRUB-efi > package doesn't support chainloading the Windows bootloader. This is > getting fixed in Fedora 24 but I have no idea how long it'll take to > get to CentOS 7. You could either disable Secure Boot (which I don't > recommend) or you switch between CentOS and Windows using the > firmware's boot manager. You'll have to figure out which F key brings > up the boot manager. On my Intel NUC it's F10, *shrug*.May I ask a couple of questions which I'm afraid betray my ignorance. 1. Why is it advisable to "revert back to UEFI"? Is this just a safety measure? I would have thought that if an intruder had got in this far, enabling him to install unsigned modules, he would have you at his mercy anyway? 2. I installed CentOS-7.2.1511 from a Live USB stick, and I have a Windows 10 partition that I can boot into. So I assume that UEFI is not used by default? Will it become so at some point? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin