https://bugzilla.novell.com/show_bug.cgi?id=445900 User cheskis@post.tau.ac.il added comment https://bugzilla.novell.com/show_bug.cgi?id=445900#c20 Sergey Cheskis <cheskis@post.tau.ac.il> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cheskis@post.tau.ac.il --- Comment #20 from Sergey Cheskis <cheskis@post.tau.ac.il> 2009-01-07 14:13:31 MST --- (In reply to comment #17 from Frerk Meyer)
I got it working by hand. The bug is YAST2 or the perl-bootloader script activates the /dev/sda3 extended partition, but not the /dev/sda5 linux logical partition where grub lives. I changed the boot flag with fdisk manually and now dual-boot works again. The bug happens even if windows is second place in the boot menu. Here are the partitions (from memory): /dev/sda1 windows ntfs /dev/sda2 linux swap /dev/sda3 extended partition win95/lba /dev/sda5 linux ext2/3 filling 100% of /dev/sda3
Hope it helps, Frerk.meyer@gmx.de
I also have the same problem when I tried to make the windows partition to be default. It is nor first in menu. However when I try to change manually by fdisk boot flag from the extended partition (in my case it is /dev/sda4 to /dev/sda/sda6 logical partition where grub located I receive after reboot the message: "no active partition". If I make a boot flag to /dev/sda3 where windows vista is located I can boot vista. But even with with suse 11.1 repair installation I cannot boot into Linux. Any workaround solution is appreciated. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.