New subject: [Bug 748988] perl-bootloader or related messes up menu.lst - no boot any more (swraid)

25 Feb 2012

      https://bugzilla.novell.com/show_bug.cgi?id=748988

https://bugzilla.novell.com/show_bug.cgi?id=748988#c0

           Summary: perl-bootloader or related messes up menu.lst - no
                    boot any more (swraid)
    Classification: openSUSE
           Product: openSUSE 12.1
           Version: Final
          Platform: i686
        OS/Version: openSUSE 12.1
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Installation
        AssignedTo: bnc-team-screening@forge.provo.novell.com
        ReportedBy: abittner@stud.fh-heilbronn.de
         QAContact: jsrain@suse.com
          Found By: ---
           Blocker: ---

User-Agent:       Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.11 (KHTML, like
Gecko) Chrome/17.0.963.56 Safari/535.11

I have had a tiresome experience with opensuse 12.1/x86. had an older
softwareraid opensuse system, two physical identical sized disks (sata), two
partitions each, md0 and md1. 

sda1/sdb1 was md0
sda2/sb2 was md1

md0 was swap (might not make sense this way, anyways)
md1 was / (root)

previous opensuse system was working very fine.

upgraded to 12.1/x86 via booting from downloaded iso image on dvd rom.
upgrading packages went fine, towards the end, some grub or perl-bootloader or
such gave some errors as following:

(retrieved this later from logs)
GRUB::GrubDev2UnixDev: No partition found for
/dev/disk/by-id/ata-SAMSUNG_HD753LJ_S13UJ1NQB00972 with 2.

the upgraded system wanted to reboot, and never managed to boot again, grub
bootscreen (graphical) fell back to textmode and said error17 couldnt mount
partition or so.

after quite a lot of research and reading other peoplse complaints about
opensuse 12.1 problems after upgrading older systems and especially with mdraid
(is that the proper name for it? i get confused about swraid, mdraid, dmraid(?
was there such thing?))

so i fired up the install-media of 12.1 again and went to rescue mode and took
a look at my harddisk, and odd enough, that rescue media already displayed
things like /dev/md126 and /dev/md127 !

later i came across bugreports about md126 and md127 only happening when
physical harddisk and their GUID couldnt be identified properly and all sorts
of things. eventually i also found some other people speaking about needing to
fall back to sysvinit instead of systemdinit so i re-upgraded the 12.1 system
again and selected sysvinit and sysvinit-init packages in the boot-time yast2,
but that didnt help either. also while in graphical grub pressing F5 for
sysinit V (is that the same as sysvinit?) didnt help to boot the system.

somewhere else I found discussions about this perl-bootloader script being
faulty or adding wrong (hdX,Y) entries and that gave me first hints that my
menu.lst file was messed.

so i figured that the upgrade process of 12.1 and also at a later time (when i
got that 12.1 booting up rather normally) the zypper up for the 12.1 kernel
update rpm to 3.1.9-1.4-desktop messed up my manually fixed menu.lst once
again.

so this is what i figure: currently there are some problems with kernel
upgrades and grub/bootloader related scripts and areas within opensuse 12.1

everything boils down to that a formerly (hd0,1) became a mere (hd0), and that
was a main part of the problem that grub couldnt start the boot process. the
md126 and md127 problem is further down the road though.....

my old menu.lst entry for example said:
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.2 - 2.6.31.14-0.8
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.31.14-0.8-desktop root=/dev/md1 resume=/dev/md0
splash=silent showopts
    initrd /boot/initrd-2.6.31.14-0.8-desktop

-------------

modified menu.lst after 12.1 upgrade or after zypper up kernel packages:

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 12.1 - 3.1.9-1.4
    root (hd0)
    kernel /boot/vmlinuz-3.1.9-1.4-desktop root=/dev/md1 resume=/dev/md0
splash=silent  showopts
    initrd /boot/initrd-3.1.9-1.4-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 12.1 - 3.1.9-1.4
    root (hd0)
    kernel /boot/vmlinuz-3.1.9-1.4-desktop root=/dev/md1 showopts ide=nodma
apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off
processor.max_cstate=1 x11failsafe
    initrd /boot/initrd-3.1.9-1.4-desktop

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 12.1 - 3.1.0-1.2
    kernel (hd0,1)/boot/vmlinuz-3.1.0-1.2-desktop root=/dev/md1 resume=/dev/md0
splash=silent  showopts
    initrd (hd0,1)/boot/initrd-3.1.0-1.2-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 12.1 - 3.1.0-1.2
    kernel (hd0,1)/boot/vmlinuz-3.1.0-1.2-desktop root=/dev/md1 showopts
ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off
highres=off processor.max_cstate=1 x11failsafe
    initrd (hd0,1)/boot/initrd-3.1.0-1.2-desktop

----------------

the lower two entries are my manually fixed vanilla state 12.1 right after the
fixed menu.lst from the first boot into the upgraded 12.1 system. i fixed the
(hd0) to (hd0,1)

hd0 is the whole disk or rather the first partition i suppose but my first
paritions on the physical disk sda1 and sdb1 are the md0=swap paritions. grub
cant find stuff there and cant boot ofcourse.

--------------

will attach my logs i have saved and also the md0/md1 and md126/md127 stuff.
after all this hassle i ended up that my swap actually does come from md0, that
somehow works (rescue system shows md12x though), but my root / comes from a
weird md126.

i have verified the mdstat file and all those GUIDs for the disks and mdadm
tool and mdadm.conf and fstab and so forth.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

collected infos from the old system (mount, mdadm.conf, mdadm, device.map)

/dev/md1 on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
/proc on /var/lib/named/proc type none (ro,nosuid,nodev,bind)
/proc on /var/lib/ntp/proc type none (ro,bind)
/dev/md0             swap                 swap       defaults              0 0
/dev/md1             /                    ext3       acl,user_xattr        1 1
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
DEVICE partitions
ARRAY /dev/md0 level=raid1 UUID=e96ccf2b:524aca18:2e95c44d:d9d29d31
ARRAY /dev/md1 level=raid1 UUID=e721b659:7e0d4ccf:72ddd7b4:f470c146
/dev/md0:
        Version : 1.00
  Creation Time : Thu Feb 19 15:56:03 2009
     Raid Level : raid1
     Array Size : 2096468 (2047.68 MiB 2146.78 MB)
  Used Dev Size : 2096468 (2047.68 MiB 2146.78 MB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Tue Nov  8 19:09:23 2011
          State : active
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           Name : linux:0
           UUID : e96ccf2b:524aca18:2e95c44d:d9d29d31
         Events : 6

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1
/dev/md1:
        Version : 1.00
  Creation Time : Thu Feb 19 15:56:04 2009
     Raid Level : raid1
     Array Size : 730467380 (696.63 GiB 748.00 GB)
  Used Dev Size : 730467380 (696.63 GiB 748.00 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Fri Feb 24 12:28:01 2012
          State : active
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           Name : linux:1
           UUID : e721b659:7e0d4ccf:72ddd7b4:f470c146
         Events : 2990

    Number   Major   Minor   RaidDevice State
       0       8        2        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2

(fd0)   /dev/fd0
(hd0)   /dev/disk/by-id/ata-SAMSUNG_HD753LJ_S13UJ1NQB00972
(hd1)   /dev/disk/by-id/ata-SAMSUNG_HD753LJ_S13UJ1NQB00974

-- 
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.

[Bug 748988] New: perl-bootloader or related messes up menu.lst - no boot any more (swraid)

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

tags

participants (1)