https://bugzilla.novell.com/show_bug.cgi?id=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c0 Summary: Root and boot partitions on a sw raid volume, system cannot boot Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jjletho67-esus@yahoo.it QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=531933) --> (http://bugzilla.novell.com/attachment.cgi?id=531933) y2log captured using the procedure described here: https://en.opensuse.org/SDB:YaST_logging_to_USB_stick_during_installation User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 It looks like it was impossible to configure boot and root partitions on raid volume using the standard yast installation. The system that I obtain is unable to boot Reproducible: Always Steps to Reproduce: 1. start a fresh installation of opensuse 12.3 64 bit using the installation DVD 2. disks must be completely zeroed 3. create, through yast partitioner, a layout like this: /boot -> /dev/md0 (raid1) -> sda1, sdb1 swap -> /dev/md1 (raid1) -> sda2,sdb2 / -> logvol1 -> volgroup1 -> /dev/md2 -> sda3,sdb3 /home -> logvol2 ->volgroup1 -> /dev/md2 -> sda3,sdb3 /tmp -> logvol3 -> volgroup1 -> /dev/md2 -> sda3,sdb3 /var -> logvol4 -> volgroup1 -> /dev/md2 -> sda3,sdb3 empty extended partition -> sda4,sdb4 4. select grub2 as bootloader (grub legacy exhibits almost the same behavior) and install it on MBR Actual Results: After the installation the system was not able to boot (it fails on its very first reboot). On the screen there is this grub error message: ###################### Booting from local disk GRUB loading. Welcome to GRUB! error: file '/grub2/i386-pc/normal.mod' not found. Entering rescue mode grub rescue> ####################### Expected Results: The system is able to properly reboot and the second stage of the installation is launched Using the recovery cd from wich i booted I did some investigation discovering several problems: PROBLEM N. 1 the md raid 1 volume on wich i put /boot is not correctly initialized and /dev/sda1 appears to be empty. Consequently Grub is not able to find its configuration file and the kernel this is the situation i can see from the recovery cd: ******************* linux:~ # cat /proc/mdstat Personalities : [raid1] md125 : active (auto-read-only) raid1 sdb3[1] sda3[0] 23069568 blocks super 1.0 [2/2] [UU] resync=PENDING bitmap: 1/1 pages [4KB], 65536KB chunk md126 : active (auto-read-only) raid1 sdb1[1] 697280 blocks super 1.0 [2/1] [_U] bitmap: 1/1 pages [4KB], 65536KB chunk md127 : active (auto-read-only) raid1 sdb2[1] sda2[0] 1052608 blocks super 1.0 [2/2] [UU] resync=PENDING bitmap: 1/1 pages [4KB], 65536KB chunk unused devices: <none> ******************** Please note that /dev/md126 is the raid volume of our interest which i configured as /dev/md0, to be mounted as /boot ******************** linux:~ # mdadm --detail /dev/md126 /dev/md126: Version : 1.0 Creation Time : Fri Mar 22 10:50:00 2013 Raid Level : raid1 Array Size : 697280 (681.05 MiB 714.01 MB) Used Dev Size : 697280 (681.05 MiB 714.01 MB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Fri Mar 22 11:01:17 2013 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : linux:0 UUID : 70fb55c6:47dfef14:7f280172:f5642bcd Events : 8 Number Major Minor RaidDevice State 0 0 0 0 removed 1 8 17 1 active sync /dev/sdb1 ******************** So the array is in degraded mode and /dev/sda1 looks like it was removed If I examine directly the two single devices I obtain this: ******************** linux:~ # mdadm --examine /dev/sdb1 /dev/sdb1: Magic : a92b4efc Version : 1.0 Feature Map : 0x1 Array UUID : 70fb55c6:47dfef14:7f280172:f5642bcd Name : linux:0 Creation Time : Fri Mar 22 10:50:00 2013 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 1394664 (681.10 MiB 714.07 MB) Array Size : 697280 (681.05 MiB 714.01 MB) Used Dev Size : 1394560 (681.05 MiB 714.01 MB) Super Offset : 1394672 sectors State : clean Device UUID : c9a37b38:98bda5c8:8e38f11b:6701829e Internal Bitmap : -8 sectors from superblock Update Time : Fri Mar 22 11:01:17 2013 Checksum : 976c3f59 - correct Events : 8 Device Role : Active device 1 Array State : .A ('A' == active, '.' == missing) linux:~ # mdadm --examine /dev/sda1 /dev/sda1: Magic : a92b4efc Version : 1.0 Feature Map : 0x1 Array UUID : 70fb55c6:47dfef14:7f280172:f5642bcd Name : linux:0 Creation Time : Fri Mar 22 10:50:00 2013 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 1394664 (681.10 MiB 714.07 MB) Array Size : 697280 (681.05 MiB 714.01 MB) Used Dev Size : 1394560 (681.05 MiB 714.01 MB) Super Offset : 1394672 sectors State : active Device UUID : de82b920:cd0eb164:f7fbfd57:7c27ca4d Internal Bitmap : -8 sectors from superblock Update Time : Fri Mar 22 10:50:05 2013 Checksum : 709567b - correct Events : 1 Device Role : Active device 0 Array State : AA ('A' == active, '.' == missing) ******************** So I can conclude that the array was created with both sda1 and sdb1, but, for some unknown reasons, sda1 has been pulled out before the first synchronization. I recovered from this situation booting from the recovery cd and issuing this command to hotadd /dev/sda1 to /dev/md0. mdadm --manage /dev/md126 --add /dev/sda1 I waited until the synchronization was completed and then the system was able to boot PROBLEM N. 2 grub is only installed on /dev/sda MBR Once I started the system I verified that grub was only installed on /dev/sda. So in the case /dev/sda is failed, the system cannot boot from /dev/sdb. I issued a grub2-install /dev/sdb without touching the grub config and the system was able to boot also with the first disk pulled out. PROBLEM N. 3 As you can see from the mdstat above, chunk size i selected (32 kb) was not honored PROBLEM N.4 Sometimes (i did several test installation) After applying the recovery workaround i described above the second stage of the installation was not launched (I selected runlevel 3 as my default, but this was not a problem on a non raid installation) -- 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.