http://bugzilla.novell.com/show_bug.cgi?id=548243 Summary: Boot from degraded RADI1 fails on RC1 Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: birger.kollstrand@googlemail.com QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-3.2 Firefox/3.5.3 I just did a test on a boot from a RAID1, works well. Then I degraded the RAID1 by taking out one disk, the system fails to boot. Reattached disk and it booted fine. Took out the other disk in the raid, boot fails. Reattached disk and it booted fine. The Yast boot loader program tells me that the boot loader is installed to both disks and that "Enable redundancy for md array" is checked. Reproducible: Always Steps to Reproduce: 1.Make a / on RAID1 2.take out one disk from the RAID and reboot Actual Results: Crashes in the GRUB stage, before booting the kernel. Expected Results: Clean boot I'm not sure what to attach in this case... /dev/md0: Version : 1.00 Creation Time : Sat Oct 17 10:31:44 2009 Raid Level : raid1 Array Size : 6297436 (6.01 GiB 6.45 GB) Used Dev Size : 6297436 (6.01 GiB 6.45 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Mon Oct 19 22:42:01 2009 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : 10.0.0.64:0 UUID : 6c46ff91:ff094cad:597cecdb:87be983a Events : 64 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 corot:/var/log # df -h Filesystem Size Used Avail Use% Mounted on /dev/md0 6.0G 3.4G 2.3G 60% / udev 3.8G 528K 3.8G 1% /dev /dev/md2 6.0G 140M 5.5G 3% /home /dev/md3 58G 180M 55G 1% /srv /dev/md1 4.0G 197M 3.6G 6% /var -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.