Mailinglist Archive: opensuse-bugs (13069 mails)

< Previous Next >
[Bug 445900] Setting Windows first entry in Dual Boot system, messes the boot entries and machine fails to boot
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 7 Jan 2009 14:13:33 -0700 (MST)
  • Message-id: <20090107211333.3EF04CC7D3@xxxxxxxxxxxxxxxxxxxxxx>

User cheskis@xxxxxxxxxxxxxx added comment

Sergey Cheskis <cheskis@xxxxxxxxxxxxxx> changed:

What |Removed |Added

--- Comment #20 from Sergey Cheskis <cheskis@xxxxxxxxxxxxxx> 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
partition where grub lives. I changed the boot flag with fdisk manually and
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,

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:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >