Hi again!
I had a 13.1 on a Dell Precision M6400 notebook with an Intel RAID 1, dual boot with Win 7. Yesterday I decided to upgrade to 13.2 from DVD. So far so good, Kernel problems during installation (found a Bugzilla, but the solution posted there did not help), could not be resolved, but boot works fine, except that the GRUB2 shows now not only Win and Suse on the MD126 RAID partition, but also one EACH for every partition of the two HDDs in the RAID.
Normally not a problem, but I want to get rid of these boot options in GRUB2, but no way, apparently. I upgraded again from the DVD, tried to re-write GRUB and finally did a fresh install of 13.2 on the partition of the old 13.1 install. Every time GRUB2 comes bach with the boot options for the two members of the RAID.
Please, help to get rid of these GRUB2 boot options 
Kind regards
rasputin
Please upload grub.cfg to http://susepaste.org/ and post link here.
Well, os-prober does not recognize that disks are part of partitioned RAID. Could you show output of “cat /proc/partitions” and “cat /proc/mdstat” (if inline, in tags code please).
Hi arvidjaar!
Hope this helps:
user@linux-1234:~> cat /proc/partitions
major minor #blocks name
8 0 976762584 sda
8 16 976762584 sdb
11 0 1048575 sr0
9 126 976759808 md126
259 0 102400 md126p1
259 1 102296576 md126p2
259 2 46080000 md126p3
259 3 1 md126p4
259 4 725877760 md126p5
259 5 2106368 md126p6
259 6 20971520 md126p7
259 7 79304704 md126p8
user@linux-1234::~> cat /proc/mdstat
Personalities : [raid1]
md126 : active raid1 sda[1] sdb[0]
976759808 blocks super external:/md127/0 [2/2] [UU]
md127 : inactive sdb[1](S) sda[0](S)
5288 blocks super external:imsm
unused devices: <none>
user@linux-1234:~> sudo mdadm --detail /dev/md126
/dev/md126:
Container : /dev/md/imsm0, member 0
Raid Level : raid1
Array Size : 976759808 (931.51 GiB 1000.20 GB)
Used Dev Size : 976759940 (931.51 GiB 1000.20 GB)
Raid Devices : 2
Total Devices : 2
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 33deca71:cdcbdf67:1125181c:4656a88d
Number Major Minor RaidDevice State
1 8 0 0 active sync /dev/sda
0 8 16 1 active sync /dev/sdb
sudo mdadm --detail /dev/md127
/dev/md127:
Version : imsm
Raid Level : container
Total Devices : 2
Working Devices : 2
UUID : 5e939cbe:f998187b:ab631c7f:34e73ae0
Member Arrays : /dev/md/WDred042014_0
Number Major Minor RaidDevice
0 8 0 - /dev/sda
1 8 16 - /dev/sdb
Hope this helps! 
Could you show “ls -l /sys/block /sys/block/*/” additionally? Thank you!
…here we go:
user@linux-1234:~> ls -l /sys/block /sys/block/*/
/sys/block:
total 0
lrwxrwxrwx 1 root root 0 Mar 21 10:43 md126 -> ../devices/virtual/block/md126
lrwxrwxrwx 1 root root 0 Mar 21 10:43 md127 -> ../devices/virtual/block/md127
lrwxrwxrwx 1 root root 0 Mar 21 10:44 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Mar 21 10:44 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sdb
lrwxrwxrwx 1 root root 0 Mar 21 10:44 sr0 -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sr0
/sys/block/md126/:
total 0
-r--r--r-- 1 root root 4096 Mar 21 10:44 alignment_offset
lrwxrwxrwx 1 root root 0 Mar 21 10:44 bdi -> ../../bdi/9:126
-r--r--r-- 1 root root 4096 Mar 21 10:44 capability
-r--r--r-- 1 root root 4096 Mar 21 10:43 dev
-r--r--r-- 1 root root 4096 Mar 21 10:44 discard_alignment
-r--r--r-- 1 root root 4096 Mar 21 10:44 ext_range
drwxr-xr-x 2 root root 0 Mar 21 10:44 holders
-r--r--r-- 1 root root 4096 Mar 21 10:44 inflight
drwxr-xr-x 5 root root 0 Mar 21 10:43 md
drwxr-xr-x 5 root root 0 Mar 21 10:43 md126p1
drwxr-xr-x 5 root root 0 Mar 21 10:43 md126p2
drwxr-xr-x 5 root root 0 Mar 21 10:43 md126p3
drwxr-xr-x 5 root root 0 Mar 21 10:43 md126p4
drwxr-xr-x 5 root root 0 Mar 21 10:43 md126p5
drwxr-xr-x 5 root root 0 Mar 21 10:43 md126p6
drwxr-xr-x 5 root root 0 Mar 21 10:43 md126p7
drwxr-xr-x 5 root root 0 Mar 21 10:43 md126p8
drwxr-xr-x 2 root root 0 Mar 21 10:44 power
drwxr-xr-x 2 root root 0 Mar 21 10:44 queue
-r--r--r-- 1 root root 4096 Mar 21 10:44 range
-r--r--r-- 1 root root 4096 Mar 21 10:44 removable
-r--r--r-- 1 root root 4096 Mar 21 10:44 ro
-r--r--r-- 1 root root 4096 Mar 21 10:44 size
drwxr-xr-x 2 root root 0 Mar 21 10:44 slaves
-r--r--r-- 1 root root 4096 Mar 21 10:44 stat
lrwxrwxrwx 1 root root 0 Mar 21 10:43 subsystem -> ../../../../class/block
drwxr-xr-x 2 root root 0 Mar 21 10:44 trace
-rw-r--r-- 1 root root 4096 Mar 21 10:43 uevent
/sys/block/md127/:
total 0
-r--r--r-- 1 root root 4096 Mar 21 10:44 alignment_offset
lrwxrwxrwx 1 root root 0 Mar 21 10:44 bdi -> ../../bdi/9:127
-r--r--r-- 1 root root 4096 Mar 21 10:44 capability
-r--r--r-- 1 root root 4096 Mar 21 10:43 dev
-r--r--r-- 1 root root 4096 Mar 21 10:44 discard_alignment
-r--r--r-- 1 root root 4096 Mar 21 10:44 ext_range
drwxr-xr-x 2 root root 0 Mar 21 10:44 holders
-r--r--r-- 1 root root 4096 Mar 21 10:44 inflight
drwxr-xr-x 5 root root 0 Mar 21 10:43 md
drwxr-xr-x 2 root root 0 Mar 21 10:44 power
drwxr-xr-x 2 root root 0 Mar 21 10:44 queue
-r--r--r-- 1 root root 4096 Mar 21 10:44 range
-r--r--r-- 1 root root 4096 Mar 21 10:44 removable
-r--r--r-- 1 root root 4096 Mar 21 10:44 ro
-r--r--r-- 1 root root 4096 Mar 21 10:44 size
drwxr-xr-x 2 root root 0 Mar 21 10:44 slaves
-r--r--r-- 1 root root 4096 Mar 21 10:44 stat
lrwxrwxrwx 1 root root 0 Mar 21 10:44 subsystem -> ../../../../class/block
drwxr-xr-x 2 root root 0 Mar 21 10:44 trace
-rw-r--r-- 1 root root 4096 Mar 21 10:43 uevent
/sys/block/sda/:
total 0
-r--r--r-- 1 root root 4096 Mar 21 10:44 alignment_offset
lrwxrwxrwx 1 root root 0 Mar 21 10:44 bdi -> ../../../../../../../../virtual/bdi/8:0
-r--r--r-- 1 root root 4096 Mar 21 10:44 capability
-r--r--r-- 1 root root 4096 Mar 21 10:43 dev
lrwxrwxrwx 1 root root 0 Mar 21 10:43 device -> ../../../0:0:0:0
-r--r--r-- 1 root root 4096 Mar 21 10:44 discard_alignment
-r--r--r-- 1 root root 4096 Mar 21 10:44 events
-r--r--r-- 1 root root 4096 Mar 21 10:44 events_async
-rw-r--r-- 1 root root 4096 Mar 21 10:44 events_poll_msecs
-r--r--r-- 1 root root 4096 Mar 21 10:44 ext_range
drwxr-xr-x 2 root root 0 Mar 21 10:43 holders
-r--r--r-- 1 root root 4096 Mar 21 10:44 inflight
drwxr-xr-x 2 root root 0 Mar 21 10:44 power
drwxr-xr-x 3 root root 0 Mar 21 10:44 queue
-r--r--r-- 1 root root 4096 Mar 21 10:44 range
-r--r--r-- 1 root root 4096 Mar 21 10:44 removable
-r--r--r-- 1 root root 4096 Mar 21 10:44 ro
-r--r--r-- 1 root root 4096 Mar 21 10:44 size
drwxr-xr-x 2 root root 0 Mar 21 10:44 slaves
-r--r--r-- 1 root root 4096 Mar 21 10:44 stat
lrwxrwxrwx 1 root root 0 Mar 21 10:43 subsystem -> ../../../../../../../../../class/block
drwxr-xr-x 2 root root 0 Mar 21 10:44 trace
-rw-r--r-- 1 root root 4096 Mar 21 10:43 uevent
/sys/block/sdb/:
total 0
-r--r--r-- 1 root root 4096 Mar 21 10:44 alignment_offset
lrwxrwxrwx 1 root root 0 Mar 21 10:44 bdi -> ../../../../../../../../virtual/bdi/8:16
-r--r--r-- 1 root root 4096 Mar 21 10:44 capability
-r--r--r-- 1 root root 4096 Mar 21 10:43 dev
lrwxrwxrwx 1 root root 0 Mar 21 10:43 device -> ../../../4:0:0:0
-r--r--r-- 1 root root 4096 Mar 21 10:44 discard_alignment
-r--r--r-- 1 root root 4096 Mar 21 10:44 events
-r--r--r-- 1 root root 4096 Mar 21 10:44 events_async
-rw-r--r-- 1 root root 4096 Mar 21 10:44 events_poll_msecs
-r--r--r-- 1 root root 4096 Mar 21 10:44 ext_range
drwxr-xr-x 2 root root 0 Mar 21 10:43 holders
-r--r--r-- 1 root root 4096 Mar 21 10:44 inflight
drwxr-xr-x 2 root root 0 Mar 21 10:44 power
drwxr-xr-x 3 root root 0 Mar 21 10:44 queue
-r--r--r-- 1 root root 4096 Mar 21 10:44 range
-r--r--r-- 1 root root 4096 Mar 21 10:44 removable
-r--r--r-- 1 root root 4096 Mar 21 10:44 ro
-r--r--r-- 1 root root 4096 Mar 21 10:44 size
drwxr-xr-x 2 root root 0 Mar 21 10:44 slaves
-r--r--r-- 1 root root 4096 Mar 21 10:44 stat
lrwxrwxrwx 1 root root 0 Mar 21 10:43 subsystem -> ../../../../../../../../../class/block
drwxr-xr-x 2 root root 0 Mar 21 10:44 trace
-rw-r--r-- 1 root root 4096 Mar 21 10:43 uevent
/sys/block/sr0/:
total 0
-r--r--r-- 1 root root 4096 Mar 21 10:44 alignment_offset
lrwxrwxrwx 1 root root 0 Mar 21 10:44 bdi -> ../../../../../../../../virtual/bdi/11:0
-r--r--r-- 1 root root 4096 Mar 21 10:44 capability
-r--r--r-- 1 root root 4096 Mar 21 10:44 dev
lrwxrwxrwx 1 root root 0 Mar 21 10:44 device -> ../../../1:0:0:0
-r--r--r-- 1 root root 4096 Mar 21 10:44 discard_alignment
-r--r--r-- 1 root root 4096 Mar 21 10:44 events
-r--r--r-- 1 root root 4096 Mar 21 10:44 events_async
-rw-r--r-- 1 root root 4096 Mar 21 10:44 events_poll_msecs
-r--r--r-- 1 root root 4096 Mar 21 10:44 ext_range
drwxr-xr-x 2 root root 0 Mar 21 10:44 holders
-r--r--r-- 1 root root 4096 Mar 21 10:44 inflight
drwxr-xr-x 2 root root 0 Mar 21 10:44 power
drwxr-xr-x 3 root root 0 Mar 21 10:44 queue
-r--r--r-- 1 root root 4096 Mar 21 10:44 range
-r--r--r-- 1 root root 4096 Mar 21 10:44 removable
-r--r--r-- 1 root root 4096 Mar 21 10:44 ro
-r--r--r-- 1 root root 4096 Mar 21 10:44 size
drwxr-xr-x 2 root root 0 Mar 21 10:44 slaves
-r--r--r-- 1 root root 4096 Mar 21 10:44 stat
lrwxrwxrwx 1 root root 0 Mar 21 10:43 subsystem -> ../../../../../../../../../class/block
drwxr-xr-x 2 root root 0 Mar 21 10:44 trace
-rw-r--r-- 1 root root 4096 Mar 21 10:43 uevent
Actually I do not see where os-prober can find information about individual partitions. What “os-prober” (as root of course) prints?
Info requested, I don’t understand the output at all, I must confess…
linux-1234:~ # os-prober
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
No volume groups found
/dev/md126p1:Windows 7 (loader):Windows:chain
OK, so if you now run “grub2-mkconfig -o /boot/grub2/grub.cfg” - does grub.cfg still contain entries for two RAID disks?
Hey! Everything back to normal and both, Suse and Win7 boot normally! Great work, do you have any idea what was wrong at all? Kind regards rasputin
pure guess that maybe the upgrade process did not see the FAKE RAID (BIOS assisted). FAKE RAID is tricky and some chip sets are better then others
But funny thing: Upgrade also booted well from the RAID (I never tried to boot from one of the members of the RAID…). Is there any way to mark the thread as “solved”? Many thanks again to arvidjaar!
No all threads are always open.
It is possible you could have over ruled the installer and forced the RAID upgrade if it missed the actual config you run
Ok, thanks !
Just to add, the kernel problem during upgrade from 13.1 to 13.2 from DVD was this here: https://bugzilla.opensuse.org/show_bug.cgi?id=903747
…and the fix in Comment 18 was the one that did not work for me.