Bug 674328

Summary: bootloader installed on extended partition even if booting from extended was disabled in first-stage
Product: [openSUSE] openSUSE 11.4 Reporter: Olaf Hering <ohering>
Component: BootloaderAssignee: Steffen Winterfeldt <snwint>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None    
Version: RC 1   
Target Milestone: ---   
Hardware: x86-64   
OS: Linux   
Whiteboard:
Found By: Outsourced Testing Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: bug674328.tar.bz2
bug674328-sles11sp1.tar.bz2
bug674328-sles11sp1.tar.bz2
bug674328-11.4rc1.tar.bz2
bug674328-sles11ga.tar.bz2

Description Olaf Hering 2011-02-23 13:55:25 UTC
11.4rc1, and also sles11 sp1.

I have added a new logical partition sda10 after shrinking the existing partition sda9. The intention is to boot from sda10 via chainloader which is already installed on sda1.

So I disabled the checkbox "booting from extended" and enabled "booting from root". But again I got an unbootable system because something marked the extended partition as bootable.

stein-schneider:~ # blkid
/dev/sda1: LABEL="BOOT" UUID="fba4702a-611d-401f-831e-25a9c06cd694" TYPE="ext2"
/dev/sda2: UUID="a63b115d-b0b9-43a7-99dd-e13c4ee6ec8c" TYPE="swap"
/dev/sda5: LABEL="SLES10" UUID="c74fb44c-7056-4227-bfb6-0ebc5e888fa2" TYPE="reiserfs"
/dev/sda6: LABEL="SLES11" UUID="0f396d50-29a3-4258-aa9a-677311a9d0a0" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda7: LABEL="sles11_backup" UUID="f8959fdd-e8c8-4c01-8e83-18ae2c2c6987" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda8: LABEL="sles11_clean" UUID="b9addce1-27ce-4100-896d-c4ec3ef851e3" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda9: LABEL="ABUILD" UUID="33863c7b-2ddf-4639-8e24-226ce8aa751b" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda10: LABEL="11.4" UUID="2cf353b0-ad5b-4de1-a69c-0630943882c8" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
stein-schneider:~ #
stein-schneider:~ # parted /dev/sda unit GiB print
Model: ATA GB0160EAFJE (scsi)
Disk /dev/sda: 149GiB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start    End      Size     Type      File system     Flags
 1      0.00GiB  0.18GiB  0.18GiB  primary   ext2            type=83
 2      0.18GiB  2.05GiB  1.87GiB  primary   linux-swap(v1)  type=82
 3      2.05GiB  149GiB   147GiB   extended                  boot, type=85
 5      2.05GiB  11.4GiB  9.33GiB  logical   reiserfs        type=83
 6      11.4GiB  20.7GiB  9.33GiB  logical   ext3            type=83
 7      20.7GiB  30.0GiB  9.33GiB  logical   ext3            type=83
 8      30.0GiB  39.4GiB  9.33GiB  logical   ext3            type=83
 9      39.4GiB  108GiB   69.0GiB  logical   ext3            type=83
10      108GiB   128GiB   20.0GiB  logical   ext4            type=83


Will attach logs once I get the system back...
Comment 1 Olaf Hering 2011-02-23 13:56:26 UTC
scrolling through the screen history shows this:

root@stein-schneider:~ # fdisk -l

Platte /dev/sda: 160.0 GByte, 160041885696 Byte
255 Köpfe, 63 Sektoren/Spuren, 19457 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Disk identifier: 0x00096c9c

   Gerät  boot.     Anfang        Ende     Blöcke   Id  System
/dev/sda1               1          23      184716   83  Linux
/dev/sda2              24         267     1959930   82  Linux Swap / Solaris
/dev/sda3   *         268       19457   154143675   85  Linux erweitert
/dev/sda5             268        1485     9783522   83  Linux
/dev/sda6            1486        2703     9783522   83  Linux
/dev/sda7            2703        3921     9783522   83  Linux
/dev/sda8            3921        5139     9783522   83  Linux
/dev/sda9            5139       19457   115009429+  83  Linux
root@stein-schneider:~ # parted /dev/sda unit GiB print
Modell: ATA GB0160EAFJE (scsi)
Festplatte  /dev/sda:  149GiB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: msdos

Nummer  Anfang   Ende     Größe    Typ       Dateisystem  Flags
 1      0,00GiB  0,18GiB  0,18GiB  primary   ext2         , , , , , , , , , type=83, ,
 2      0,18GiB  2,05GiB  1,87GiB  primary   linux-swap   , , , , , , , , , type=82, ,
 3      2,05GiB  149GiB   147GiB   extended               boot, , , , , , , , , type=85, ,
 5      2,05GiB  11,4GiB  9,33GiB  logical   reiserfs     , , , , , , , , , type=83, ,
 6      11,4GiB  20,7GiB  9,33GiB  logical   ext3         , , , , , , , , , type=83, ,
 7      20,7GiB  30,0GiB  9,33GiB  logical   ext3         , , , , , , , , , type=83, ,
 8      30,0GiB  39,4GiB  9,33GiB  logical   ext3         , , , , , , , , , type=83, ,
 9      39,4GiB  149GiB   110GiB   logical   ext3         , , , , , , , , , type=83, ,

root@stein-schneider:~ # blkid
/dev/sda1: LABEL="BOOT" UUID="fba4702a-611d-401f-831e-25a9c06cd694" TYPE="ext2"
/dev/sda2: UUID="a63b115d-b0b9-43a7-99dd-e13c4ee6ec8c" TYPE="swap"
/dev/sda5: LABEL="SLES10" UUID="c74fb44c-7056-4227-bfb6-0ebc5e888fa2" TYPE="reiserfs"
/dev/sda6: LABEL="SLES11" UUID="0f396d50-29a3-4258-aa9a-677311a9d0a0" TYPE="ext3"
/dev/sda7: LABEL="sles11_backup" UUID="f8959fdd-e8c8-4c01-8e83-18ae2c2c6987" TYPE="ext3"
/dev/sda8: LABEL="sles11_clean" UUID="b9addce1-27ce-4100-896d-c4ec3ef851e3" TYPE="ext3"
/dev/sda9: LABEL="ABUILD" UUID="33863c7b-2ddf-4639-8e24-226ce8aa751b" TYPE="ext3"


So for some reason the system did boot from sda3 already.
Comment 2 Jiri Srain 2011-02-23 14:02:13 UTC
Olaf, are you sure you un-checked the check box for partition activation and for replacement of MBR with generic code?
Comment 3 Olaf Hering 2011-02-23 14:35:23 UTC
Created attachment 415767 [details]
bug674328.tar.bz2

logfiles from the system
Comment 4 Olaf Hering 2011-02-23 14:41:04 UTC
I did not touch the MBR part.
Booting from extended partition was the only active option, I changed it to boot from root partition.


It seems the intention of such an *.arch.suse.de autosetup is to boot from sda1, which has a chainloader into the individual logical partitions. How the extended partition got activated, no idea.

The other SP1 system I installed yesterday did also not boot, maybe because sda3 was active before I changed the partition layout manually. 

Now I activated sda1, rerun the grub.conf on sda1 and the system boots sda1 -> sda10 now.
Comment 5 Olaf Hering 2011-02-23 15:03:26 UTC
I wiped the drive on bach.arch.suse.de and run an SLES11-SP1-install-auto-vnc install now, to see what the resulting disk layout is.
Comment 6 Olaf Hering 2011-02-23 15:44:42 UTC
After a fresh install, running setup and SLES11-SP1-install-auto, sda1 remains the active partition on bach.

I did a manual SP1 install on stein-schneider on another partition, maybe that broke the layout. I will try to reproduce it on bach now.
Comment 7 Olaf Hering 2011-02-23 16:31:00 UTC
The root cause was maybe my manual SLES11 SP1 install on stein-schneider.

On bach.arch.suse.de I had this before and after SP1 install:

inst-sys:/ # fdisk -l

Disk /dev/sda: 72.7 GB, 72729231360 bytes
255 heads, 63 sectors/track, 8842 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00085eda

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          23      184716   83  Linux
/dev/sda2              24         267     1959930   82  Linux swap / Solaris
/dev/sda3             268        8842    68878687+  85  Linux extended
/dev/sda5             268        1485     9783522   83  Linux
/dev/sda6            1486        2703     9783522   83  Linux
/dev/sda7            2703        3921     9783522   83  Linux
/dev/sda8            3921        5139     9783522   83  Linux
/dev/sda9            5139        8842    29744442   83  Linux
inst-sys:/ # exit
starting slpd to announce VNC...
starting yast...
Probing connected terminal...

Initializing virtual console...

Found an xterm terminal on /dev/console (210 columns x 55 lines).
Please supply a config file

starting VNC server...
A log file will be written to: /var/log/YaST2/vncserver.log ...

***
***           You can connect to 10.11.0.16, display :1 now with vncviewer
***           Or use a Java capable browser on  http://10.11.0.16:5801/
***

(When YaST2 is finished, close your VNC viewer and return to this window.)

*** Starting YaST2 ***

ATTENTION: Starting shell... (use 'exit' to proceed)
Welcome to the inst-sys on bach.arch.suse.de 2.6.32.12-0.7-default x86_64
inst-sys:/ # fdisk -l

Disk /dev/sda: 72.7 GB, 72729231360 bytes
255 heads, 63 sectors/track, 8842 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00085eda

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1          23      184716   83  Linux
/dev/sda2              24         267     1959930   82  Linux swap / Solaris
/dev/sda3   *         268        8842    68878687+  85  Linux extended
/dev/sda5             268        1485     9783522   83  Linux
/dev/sda6            1486        2703     9783522   83  Linux
/dev/sda7            2703        3921     9783522   83  Linux
/dev/sda8            3921        5139     9783522   83  Linux
/dev/sda9            5139        8842    29744442   83  Linux
inst-sys:/ #
Comment 8 Olaf Hering 2011-02-23 16:54:13 UTC
Created attachment 415801 [details]
bug674328-sles11sp1.tar.bz2
Comment 9 Olaf Hering 2011-02-23 17:14:22 UTC
Created attachment 415811 [details]
bug674328-sles11sp1.tar.bz2

ignore previous attachment, log was from autoyast on sda6.
The correct one from sda5 is now attached.
Comment 10 Olaf Hering 2011-02-23 18:06:16 UTC
Created attachment 415824 [details]
bug674328-11.4rc1.tar.bz2

happens also with 11.4rc1
Comment 11 Olaf Hering 2011-02-24 12:51:24 UTC
Created attachment 415983 [details]
bug674328-sles11ga.tar.bz2

It even happens with SLES11 GA!?
Comment 13 Steffen Winterfeldt 2014-12-11 11:00:15 UTC
I think that has been resolved in sle12/oS 13.2.