Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Nothing left to boot after F12 deactivated Windows partition|
|Product:||[Fedora] Fedora||Reporter:||Alexei Podtelezhnikov <apodtele>|
|Component:||anaconda||Assignee:||Anaconda Maintenance Team <anaconda-maint-list>|
|Status:||CLOSED DUPLICATE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||12||CC:||anaconda-maint-list, clumens, hdegoede, vanmeeuwen+fedora|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2009-11-18 09:24:07 EST||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Alexei Podtelezhnikov 2009-11-17 23:19:42 EST
This is god damn fucking lovely! I specifically selected NOT to install bootloader into MBR, which I wanted to keep for NTLDR. Apparently, F12-LiveCD-KDE installer just erased it anyhow. I did put GRUB on the /boot partition. How the fuck am I supposed to boot now? How can I recover NTLDR?
Comment 1 Chris Lumens 2009-11-18 09:24:07 EST
That kind of language will get you nowhere with us. *** This bug has been marked as a duplicate of bug 504570 ***
Comment 2 Alexei Podtelezhnikov 2009-11-21 20:21:08 EST
I apologize, but it took me a while to figure out what happened and frustration was overwhelming. So this is what actually transpired: sda(MBR) contains Dell loader which passes to *sda2* boot sector was *active* originally, and used by NTLDR, and configured to load GRUB and Fedora if selected sda5 boot sector is where I put GRUB bootloader After installation Anaconda *deactivated* sda2 and I could not reach any bootable OS. Proposed solution: Leave active partitions alone if user puts bootloader on a partition, but warn that it's his responsibility to configure ALL bootloaders if he wants to reach /boot.