12.3 installed with RAID, some success

I just installed 12.3 on my desktop. It installed in a RAID-1 mirror in
extended partitions.

Here is my setup:


21 TB drives partitioned exactly the same:
Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048     4192255     2095104   82  Linux swap / Solaris
/dev/sda2         4192256    46139391    20973568   fd  Linux raid
autodetect
/dev/sda3        46139392   976752639   465306624   fd  Linux raid
autodetect
/dev/sda4   *   976752640  1953523711   488385536    f  W95 Ext'd (LBA)
/dev/sda5       976754688  1018697727    20971520   fd  Linux raid
autodetect
/dev/sda6      1018699776  1060642815    20971520   83  Linux
/dev/sda7      1060644864  1953503231   446429184   fd  Linux raid
autodetect

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048     4192255     2095104   82  Linux swap / Solaris
/dev/sdb2         4192256    46139391    20973568   fd  Linux raid
autodetect
/dev/sdb3        46139392   976752639   465306624   fd  Linux raid
autodetect
/dev/sdb4   *   976752640  1953523711   488385536    5  Extended
/dev/sdb5       976754688  1018697727    20971520   fd  Linux raid
autodetect
/dev/sdb6      1018699776  1060642815    20971520   83  Linux
/dev/sdb7      1060644864  1953503231   446429184   fd  Linux raid
autodetect

Here are the RAID drives:


/dev/md0 raided from /dev/sda2 - /dev/sdb2
/dev/md1 raided from /dev/sda3 - /dev/sdb3
/dev/md2 raided from /dev/sda5 - /dev/sdb5
/dev/md3 raided from /dev/sda7 - /dev/sdb7

When I was running 12.2, my root drive (this was my /, and /boot is
included rather than being mounted and partitioned separately) was
/dev/md0. I wanted to install 12.3 on /dev/md2, but I know people have
had some trouble installing 12.3 on a RAID-1 mirror (or rather not
trouble installing it, but getting it to boot). Knowing that /dev/md2 is
raided from 2 extended partition drives, I was prepared for the worst.

However, the install program worked very smoothly. I had to edit my
partition setups so that it would install in /dev/md2, and after doing
so, it booted up from grub2 without a hitch. I am now running with
/dev/md2 as my root in 12.3. Seems to be fine so far.

I do know that I have grub2 only installed in the MBR of /dev/sda, and
so I need to also put it into /dev/sdb also in case /dev/sda fails.

The only little thing that is a problem is this. I had 12.1 installed in
the single non-raided partition /dev/sdb6 from before. So the new grub2
boot menu that shows up when I boot includes this as an option to boot.

However, the 12.2 system that I had running does not show up on the menu
as an option. Since grub2 is supposed to detect all OS’s available, and
it seems to miss this one (probably because it is on a RAID), I assume
this is a bug. If anyone knows if this bug has already been filed,
please post. Otherwise, I will file a bug report.

So for now, I am going to research how to get that added to the grub
boot menu. I knew how to add it in grub legacy with the menu.lst file;
it is a bit more challenging in grub2.

I am just getting started, so nothing else to report.


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.1 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.2 | KDE 4.9.2 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

On 03/22/2013 12:08 PM, golson765 wrote:
> The only little thing that is a problem is this. I had 12.1 installed in
> the single non-raided partition /dev/sdb6 from before. So the new grub2
> boot menu that shows up when I boot includes this as an option to boot.
>
> However, the 12.2 system that I had running does not show up on the menu
> as an option. Since grub2 is supposed to detect all OS’s available, and
> it seems to miss this one (probably because it is on a RAID), I assume
> this is a bug. If anyone knows if this bug has already been filed,
> please post. Otherwise, I will file a bug report.
>
> So for now, I am going to research how to get that added to the grub
> boot menu. I knew how to add it in grub legacy with the menu.lst file;
> it is a bit more challenging in grub2.
>
> I am just getting started, so nothing else to report.
>
After doing some research, I can’t seem to find anyone else with this
same problem. It seems like many people have had a problem getting
os_prober to detect a windows installation, but nobody seems to have it
causing a problem detecting a RAIDed opensuse installation. There is a
patch script for os_prober for grub2 when you have UEFI, but I couldn’t
find any kind of patch for what I am looking for.

I also have had quite a difficult time finding an example of exactly the
proper syntax if I were to add a custom menu entry in
/etc/grub.d/40_custom. Does anyone have an example of that for openSUSE?
I found some in ubuntu, and I know it is probably basically the same.
But what about all the insmod commands and things like that? It seems
like grub2 has more commands in the boot line than we see in the
menu.lst listings for grub legacy.


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.1 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.2 | KDE 4.9.2 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

Run os-prober and post output here, also upload /var/log/messages after running os-prober to SUSE Paste and post link.

On 03/22/2013 01:46 PM, arvidjaar wrote:
> golson765;2539300 Wrote:
>> However, the 12.2 system that I had running does not show up on the
>> menu
>> as an option.
> Run os-prober and post output here, also upload /var/log/messages
> after running os-prober to ‘SUSE Paste’ (http://susepaste.org) and
> post link.
>
>
>
Ok, thanks for your help. On paste it wouldn’t let me put in the entire
/var/log/messages file, so I just went up a few lines and cut it off,
hopefully enough information is there. I did that after running
os-prober. Here is the link: http://susepaste.org/26662529

I am not sure I ran os-prober the right way, but here is what I did. If
there is a better way to run os-prober than as a shell script like I did
below, please let me know.


linux-ip49:/etc/grub.d # ./30_os-prober
No volume groups found
Found openSUSE 12.1 (x86_64) on /dev/sdb6
menuentry 'openSUSE 12.1 (x86_64) (on /dev/sdb6)' --class gnu-linux
--class gnu --class os $menuentry_id_option
'osprober-gnulinux-simple-bf0cd224-28c4-4f17-9f89-fadaf0d9af4c' {
insmod part_msdos
insmod ext2
set root='hd1,msdos6'
if  x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos6
--hint-efi=hd1,msdos6 --hint-baremetal=ahci1,msdos6 --hint='hd1,msdos6'
bf0cd224-28c4-4f17-9f89-fadaf0d9af4c
else
search --no-floppy --fs-uuid --set=root
bf0cd224-28c4-4f17-9f89-fadaf0d9af4c
fi
linux /boot/vmlinuz-3.1.0-1.2-desktop
root=/dev/disk/by-label/roottemp resume=/dev/disk/by-label/swap1
splash=silent quiet showopts vga=0x317
initrd /boot/initrd-3.1.0-1.2-desktop
}
submenu 'Advanced options for openSUSE 12.1 (x86_64) (on /dev/sdb6)'
$menuentry_id_option
'osprober-gnulinux-advanced-bf0cd224-28c4-4f17-9f89-fadaf0d9af4c' {
menuentry 'Desktop -- openSUSE 12.1 - 3.1.0-1.2 (on /dev/sdb6)'
--class gnu-linux --class gnu --class os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.1.0-1.2-desktop--bf0cd224-28c4-4f17-9f89-fadaf0d9af4c'
{
insmod part_msdos
insmod ext2
set root='hd1,msdos6'
if  x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-bios=hd1,msdos6 --hint-efi=hd1,msdos6
--hint-baremetal=ahci1,msdos6 --hint='hd1,msdos6'
bf0cd224-28c4-4f17-9f89-fadaf0d9af4c
else
search --no-floppy --fs-uuid --set=root
bf0cd224-28c4-4f17-9f89-fadaf0d9af4c
fi
linux /boot/vmlinuz-3.1.0-1.2-desktop
root=/dev/disk/by-label/roottemp resume=/dev/disk/by-label/swap1
splash=silent quiet showopts vga=0x317
initrd /boot/initrd-3.1.0-1.2-desktop
}
menuentry 'Failsafe -- openSUSE 12.1 - 3.1.0-1.2 (on /dev/sdb6)'
--class gnu-linux --class gnu --class os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.1.0-1.2-desktop--bf0cd224-28c4-4f17-9f89-fadaf0d9af4c'
{
insmod part_msdos
insmod ext2
set root='hd1,msdos6'
if  x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-bios=hd1,msdos6 --hint-efi=hd1,msdos6
--hint-baremetal=ahci1,msdos6 --hint='hd1,msdos6'
bf0cd224-28c4-4f17-9f89-fadaf0d9af4c
else
search --no-floppy --fs-uuid --set=root
bf0cd224-28c4-4f17-9f89-fadaf0d9af4c
fi
linux /boot/vmlinuz-3.1.0-1.2-desktop
root=/dev/disk/by-label/roottemp showopts apm=off noresume edd=off
powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset
x11failsafe vga=0x317
initrd /boot/initrd-3.1.0-1.2-desktop
}
}



G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.1 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.2 | KDE 4.9.2 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

Just run “os-prober”. Verbatim.

Anyway this is a missing feature in os-prober, it does not look inside MD arrays. Please open bug report (http://bugzilla.novell.com) and attach the following information:

  1. output of “cat /proc/mdstat” on 12.3
  2. output of “blikid” on 12.3
  3. output of “cat /proc/mdstat” on 12.2
  4. /etc/fstab from 12.2
  5. /boot/grub2/grub.cfg or /boot/grub/menu.last from 12.2 (whatever you use)

You account for forums is valid for bugzilla as well. Post bug number here.

On 03/22/2013 06:36 PM, arvidjaar wrote:
> golson765;2539365 Wrote:
> You account for forums is valid for bugzilla as well. Post bug number
> here.

Ok, it is bug number 811006.
https://bugzilla.novell.com/show_bug.cgi?id=811006

Ok, so in light of not being able to get grub2 to automatically detect
this array, how do I set up my system so that I can boot back into 12.2?
I have not been able to find any good guidance on setting up a custom
menu entry.


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.1 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.2 | KDE 4.9.2 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it