| |||||||||||||
GRUB 2.00 releasedGRUB 2.00 releasedPosted Jun 29, 2012 6:53 UTC (Fri) by steveriley (subscriber, #83540)Parent article: GRUB 2.00 released
For any GRUB experts checking in here, one of our members at Kubuntu Forums has a vexing problem: GRUB appears convinced that two of the hard drives in his machine contain the Windows 7 bootloader, even though Windows is not present on his computer at all.
http://www.kubuntuforums.net/showthread.php?59333
He's resorted to disabling the OS prober, which at least cleans up his menu. If there's a better solution, it eludes us. So...any ideas?
(Log in to post comments)
GRUB 2.00 released Posted Jun 29, 2012 12:39 UTC (Fri) by slashdot (guest, #22014) [Link]
Read the source code of the OS prober.
I guess it's most likely finding the NTFS partition boot code for Windows 7, not sure if you can easily erase it or disable the check.
Probably the fix is to expand the check to also check that a file called "bootmgr" is present in the NTFS root directory (or "ntldr" in the pre-Vista case).
GRUB 2.00 released Posted Jun 30, 2012 8:53 UTC (Sat) by steveriley (subscriber, #83540) [Link]
Yup, that was the problem -- Bootmgr was present. Earlier I had suggested looking for NTLDR, which of course wasn't there. Completely forgot about Bootmgr!
GRUB 2.00 released Posted Jun 29, 2012 13:02 UTC (Fri) by cortana (subscriber, #24596) [Link]
Please file a bug against grub or os-prober too. I just had a look at the source code and the current version (1.53) seems to only detect Windows 7 if there's a file 'BOOT\BCD' on the filesystem, but it's possible that you have an older version that behaves as slashdot says.
|
|||||||||||||