https://bugzilla.novell.com/show_bug.cgi?id=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c0 Summary: 13.1RC2 Cannot boot from RAID1 volume(s) Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: i586 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vmicho@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=566785) --> (http://bugzilla.novell.com/attachment.cgi?id=566785) 12.3 partition setup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 Image used: openSUSE-13.1-DVD-Build0084-i586.iso My partition setup is simple: 2 disks, 4 primary partitions on each disk, same setup on both disks, raid1 for each identical partition pair (see attached screen shot): 15gb /, 200mb /boot, 90gb /home, 40gb /mnt/data, no swap, no EFI. Setup + installation + 1st boot to system works OK. Next boot fails though. I've recreated same setup in 12.3 on zeroed disks and all works. The only obvious difference between 12.3 and 13.1rc2 is: - raids are named md124-md127 instead of md0-md3 - you can give the raid a name/label (I've used root, boot, home, data) -> see "KO clean partition setup*" for details. -> on rescue system, all raids look OK and are mountable without errors And of course the sstem doesn't boot -> see the "boot failure*" screen shots Note: Just a maybe a related observation: I've redone installation of rc2 3 or four times, usually on zeroed disks. I've reused the raid setup once from previous installation and (I do not remember precisely) I think after the 1st boot to system after installation, one partition was mounted twice (!). Two md devices somehow 'pointed' to the same partitions (e.g. md124 was mounted on /, md125 on /mnt/data, but in /mnt/data I saw the root filesystem again!) Reproducible: Always Steps to Reproduce: 1. PC with 2 zeroed HDDs (I zeroed few MB on the beginning with dd), no EFI 2. run installation dvd 3. create new custom partition setup as described in this bug 4. click bootloader settings, confirm (just in case, to allow/check redundancy) 5. complete installation, 1st reboot 6. 2nd installation phase and login into desktop 7. reboot and fail Actual Results: 7. No longer able to boot after 1st boot to system Expected Results: Should boot every time -- 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.