[opensuse] new hardware, system won't boot up in 2nd partion with RAID1 setup

Hi all,

I just upgraded my hardware and I have RAID 1 set up and working on the first 2 partitions after swap of both my hard drives.It boots ok into the first RAID partition, /dev/md0, with openSUSE12.1.

However, I am now unable to get my backup partition started on /dev/md2, where I have openSUSE 11.4 installed. When I try and boot into /dev/md2, my system gets past grub, but then as it is booting up, udev sets up device /dev/md126 on 2 drives (I don't know which RAID this is or where it gets the number 126), and then it cannot find the root drive. (It does not do that when I boot into /dev/md0, where I have openSUSE 12.1 installed.)

When I select the 3rd option I set up on grub, to boot into openSUSE 11.4 on my degraded RAID, this is what shows up on the boot sequence:

doing fast boot
Creating device nodes with udev
mdadm: /dev/md126 has been started with 2 drives.
Trying manual resume from /dev/disk/by-label/swap2
Invoking userspace resume from /dev/disk/by-label/swap2
resume: libgcrypt version 1.4.6
Trying manual resume from /dev/disk/by-label/swap2
Invoking in-kernel resume from /dev/disk/by-label/swap2
Waiting for device /dev/disk/by-label/AltOldLinuxRoot to appear: .^[................................ Could not find /dev/disk/by-label/AltOldLinuxRoot.
Want me to fall back to /dev/disk/by-label/root? (Y/n)

So it never finds the RAID partition to boot into it, even though grub found it no problem (I had to set up the degraded RAID specifying metadata 1.0, because when I tried it with the default 1.2, the superblock is stored 4k from the start, so grub couldn't find the boot directory).

Ok, here is some background. My partitions are set up as follows:

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes

Device Boot Blocks Id System LABEL
/dev/sda1 2095104 82 Linux swap / Solaris swap2
/dev/sda2 * 20973568 fd Linux raid autodetect linux-aw90:0
/dev/sda3 465306624 fd Linux raid autodetect linux-aw90:1
/dev/sda4 488385536 f W95 Ext'd (LBA)
/dev/sda5 20971520 83 Linux root2
/dev/sda6 20971520 83 Linux
/dev/sda7 446429184 83 Linux xtradata


Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes

Device Boot Blocks Id System LABEL
/dev/sdb1 2095104 82 Linux swap / Solaris swap1
/dev/sdb2 20973568 fd Linux raid autodetect linux-aw90:0
/dev/sdb3 465306624 fd Linux raid autodetect linux-aw90:1
/dev/sdb4 488385536 5 Extended
/dev/sdb5 20971520 fd Linux raid autodetect linux-aw90:2
/dev/sdb6 20971520 83 Linux roottemp
/dev/sdb7 446429184 83 Linux newkde

These are my RAID1 partitions
Device Device RAID device LABEL
/dev/sda2 /dev/sdb2 /dev/md0 root
/dev/sda3 /dev/sdb3 /dev/md1 home
/dev/sdb5 missing /dev/md2 AltOldLinuxRoot

I have no problem being able to boot into /dev/md0, as this is my normal OS.

What I am trying to do is also be able to boot into /dev/md2 while it is still a degraded RAID. Grub reads my menu.lst file just fine. This is the 3rd option I have setup in menu.lst, and I have copied just that section here:

###George's option on /dev/md2###
title extended partition openSUSE 11.4 on /dev/md2
kernel (hd1,4)/boot/vmlinuz-2.6.37.6-0.9-desktop root=/dev/disk/by-label/AltOldLinuxRoot resume=/dev/disk/by-label/swap2 splash=silent quiet showopts vga=0x317
initrd (hd1,4)/boot/initrd-2.6.37.6-0.9-desktop

Here is what my /etc/mdadm.conf looks like on the openSUSE 11.4 partition

DEVICE containers partitions
ARRAY /dev/md0 UUID=e96a14ed:bc7c8d5a:9b0c114a:9e208631 name=linux-aw90:0
ARRAY /dev/md1 UUID=cdfe9dc0:73d6f7cb:7dda2c20:e3758f4f name=linux-aw90:1
ARRAY /dev/md2 UUID=9e211746:31896532:b4f86782:184e93f7 name=linux-aw90:2

So, any help getting my system to boot in my 11.4 degraded RAID partition?

--
G.O.
Box #1: 12.1 | KDE 4.8.4 | AMD Phenom IIX4 | 64 | ATI Radeon HD 3300 | 16GB
Box #2: 12.1 | KDE 4.8.4 | AMD Athlon X3 | 64 | nVidia C61 GeForce 7025 | 4GB
Laptop: 12.1 | KDE 4.8.3 | Core2 Duo T8100 | 64 | Intel 965GM | 4GB RAM
learning openSUSE and loving it

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

Relevant Pages

  • Re: [Fwd: Re: [opensuse] Boot magic]
    ... Since I installed some milestones I can no longer boot the partition I want. ... I wanted to the view the progression in OpenSuse and I had a free partition so ... I installed on part3 milestone 6 with its own boot directory in the rootdir. ...
    (SuSE)
  • [Fwd: Re: [opensuse] Boot magic]
    ... Since I installed some milestones I can no longer boot the partition I want. ... I wanted to the view the progression in OpenSuse and I had a free partition so ... I installed on part3 milestone 6 with its own boot directory in the rootdir. ...
    (SuSE)
  • Re: mkraid could not lock sda2
    ... Your fstab shows that sda1 is being used, ... going to try to boot from your raid array, mark the partition as bootable. ...
    (Debian-User)
  • Re: Migrating Boot Device fom SCSI to SATA
    ... RAID 5 SATA volume on an Addonics Compact RAID enclosure. ... large RAID 5 on the Addonics Compact RAID, and then I used a disk partition ... management utility to make an image copy from the boot partition on C: ... you'd want to compare the source MBR and dest MBR. ...
    (microsoft.public.windowsxp.hardware)
  • Re: [opensuse] new hardware, system wont boot up in 2nd partion with RAID1 setup
    ... title openSUSE 11.4 on md2 as sda5 ... So you see that my raid drive is listed as /dev/md126. ... Somewhere in the copy over to the single partition, it kept the configuration so that when it booted up, it still thought it was running as RAID. ...
    (SuSE)