[Bug 496002] New: During install the 'boot' flag set is set /dev/sda2' despite the fact that "Boot from Master Boot Record" was SELECTED
http://bugzilla.novell.com/show_bug.cgi?id=496002 Summary: During install the 'boot' flag set is set /dev/sda2' despite the fact that "Boot from Master Boot Record" was SELECTED Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: pearson44j@wanadoo.fr QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.9 (like Gecko) SUSE # During Net install, I selected the following options: # In the "Boot Loader Settings" window, under the "Boot Loader Location" "Boot from Master Boot Record" was flagged / SELECTED In the "Boot Loader Options" window Set active Flag in Partion Table for Boot Partion <= SELECTED Write generic Boot Code to MBR <= SELECTED # POST install fdisk results (see below) show that the 'boot' flag was set to the Extended Partition # Fdisk results Disk /dev/sda: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000ca2c6 Device Boot Start End Blocks Id System /dev/sda1 1 1958 15727603+ 7 HPFS/NTFS /dev/sda2 * 1959 24321 179630797+ 5 Extended /dev/sda5 1959 4569 20972826 83 Linux /dev/sda6 4570 22845 146801938+ 83 Linux /dev/sda7 22846 22976 1052226 82 Linux swap / Solaris /dev/sda8 22977 24321 10803681 83 Linux Reproducible: Always Steps to Reproduce: 1.I do a Net install - I would tend to believe that it happens all the time on v 11.2 Actual Results: # fdisk -l # Device Boot Start End Blocks Id System /dev/sda1 1 1958 15727603+ 7 HPFS/NTFS /dev/sda2 * 1959 24321 179630797+ 5 Extended .. Expected Results: # fdisk -l # Device Boot Start End Blocks Id System /dev/sda1 * 1 1958 15727603+ 7 HPFS/NTFS /dev/sda2 1959 24321 179630797+ 5 Extended .. - YaST has had problems like this in the past (As I recall - there was similar problem when the partitionner was redone not too long ago.) - Yes Grub dones work OK but I think that it is embarrassing that the setup is ***not*** not what was specified. IMHO, this (inaccurately placed boot flags) woud definitely make one think twice about using opensuse is for mission critical data.... What do you think ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=496002 Zheng Chen <zchen@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zchen@novell.com AssignedTo|bnc-team-screening@forge.pr |nld10-bugs-qa@forge.provo.n |ovo.novell.com |ovell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=496002 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Bootloader AssignedTo|nld10-bugs-qa@forge.provo.n |jsrain@novell.com |ovell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=496002 User rw@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=496002#c1 Raymund Will <rw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com, | |rw@novell.com Version|Alpha 0 |Milestone 8 Severity|Normal |Critical --- Comment #1 from Raymund Will <rw@novell.com> 2009-10-05 09:28:35 MDT --- This seems to be broken still... :-( The real issue is IMHO, that settings on the "Boot Loader Installation" tab do in no way impact check-boxes concealed behind that "Boot Loader Options" button. This leads to nonsensical, contradictory settings: you can't possible eat the cake and keep it! In other words: you can easily write a generic loader *and* grub to the MBR, but you can only read the last thing written! The same is true for "Set active Flag for Boot Partition" without having one. And it's IMHO a blocker bug to activate an 'Extendend Partition", if nothing is to be installed there, only because the initial proposal of YaST had such a setup! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=496002 User pearson44j@wanadoo.fr added comment http://bugzilla.novell.com/show_bug.cgi?id=496002#c2 --- Comment #2 from James PEARSON <pearson44j@wanadoo.fr> 2009-10-05 23:57:36 CEST --- As shown before his problem still exists in M8 # What I did In the "Boot Loader Settings" window, under the "Boot Loader Location" "Boot from Master Boot Record" was flagged / SELECTED In the "Boot Loader Options" window Set active Flag in Partion Table for Boot Partion <= SELECTED Write generic Boot Code to MBR <= SELECTED linux-p1ep:~ # fdisk -l Disk /dev/sda: 300.1 GB, 300069052416 bytes 255 heads, 63 sectors/track, 36481 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00093231 Device Boot Start End Blocks Id System /dev/sda1 1 2611 20972826 7 HPFS/NTFS /dev/sda2 * 2612 36481 272060775 f W95 Ext'd (LBA) /dev/sda5 2612 5221 20964793+ 83 Linux /dev/sda6 5222 7831 20964793+ b W95 FAT32 /dev/sda7 7832 36159 227544628+ 83 Linux /dev/sda8 36160 36481 2586433+ 82 Linux swap / Solaris # M8 media used openSUSE-DVD-Build0307-i586.iso # oS details Linux 2.6.31-10-desktop i686 System: openSUSE 11.2 Milestone 8 (i586) KDE: 4.3.1 (KDE 4.3.1) "release 3" -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=496002 User jsrain@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=496002#c3 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #3 from Jiri Srain <jsrain@novell.com> 2009-10-08 02:23:51 MDT --- The described behavior is correct. You cannot set the Active flag to volume inside a logical partition or MBR. If bootloader is installed into MBR (as it was), YaST sets the flag to the partition where the /boot directory is located. However, it is inside the Extended partition, therefore the flag was set to the Extended partition. In general: If you install bootloader into MBR, there is no reason to change the boot flag if it is set to any existing partition. On the other hand, there are some (especially older) BIOSes which need the active flag to be set, otherwise they will not boot. Since BIOS correctness cannot be detected, YaST suggests to set the flag by default. It is strongly recommended to have a primary partition for bootloader (the /boot directory), we do not support scenario as you described (although in general it works). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=496002 User pearson44j@wanadoo.fr added comment http://bugzilla.novell.com/show_bug.cgi?id=496002#c4 --- Comment #4 from James PEARSON <pearson44j@wanadoo.fr> 2009-10-08 19:18:21 CEST --- Jiri Srain said In general: If you install bootloader into MBR, there is no reason to change the boot flag if it is set to any existing partition. My experience is that I can not install WinXP onto sda1 (i.e. my C drive) using the installation C - if the active flag is not set to sda1. And as I have to reinstall Windows more often than oS - that is reason enough for me. Thanks just the same -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com