https://bugzilla.novell.com/show_bug.cgi?id=227377 franz.x.maier@aon.at changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #1 from franz.x.maier@aon.at 2006-12-10 03:23 MST ------- In the meantime I solved the problem: I partitioned like the automatic partitioning from another Pc with a hardware raid (fake raid), namely /boot swap / and /home and it works! You should at least document this special requirement, as it is quite new. Regards Franz X. Maier -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 andreas.pfaller@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andreas.pfaller@gmail.com Status|CLOSED |REOPENED Resolution|FIXED | ------- Comment #2 from andreas.pfaller@gmail.com 2006-12-10 18:39 MST ------- Why close this. The problem exists. I have just installed 10.2 with software raid (2 identical partioned SATA disks with among others / /boot /var configured as raid 1 and the system does not boot after first installation step (after the first reboot after installation). I left the bootloader configuration unchanged from the one suggested by the installer. I have booted with the rescue system and the content off all relevant partitions looks OK and the raid partitions are currently syncing. This is a NEW installation where all disks were completely repartioned. So it looks like if the only problem is the bootloader installation. Currently I am trying to figure out how to install grub manually but have not yet been successful. /etc/grub.conf contains: setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0) setup --stage2=/boot/grub/stage2 (hd1,0) (hd0,0) quit and /boot/device.map: (hd0) /dev/sda (hd1) /dev/sdb Both look OK to me. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 ------- Comment #4 from andreas.pfaller@gmail.com 2006-12-11 10:10 MST ------- Created an attachment (id=109185) --> (https://bugzilla.novell.com/attachment.cgi?id=109185&action=view) YaST2 logs Obtained via rescue system from /var/log on HD of installed system. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 ------- Comment #6 from andreas.pfaller@gmail.com 2006-12-11 10:13 MST ------- Created an attachment (id=109187) --> (https://bugzilla.novell.com/attachment.cgi?id=109187&action=view) fstab Obtained from /etc on HD of installed system. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 ------- Comment #8 from andreas.pfaller@gmail.com 2006-12-11 10:16 MST ------- Created an attachment (id=109189) --> (https://bugzilla.novell.com/attachment.cgi?id=109189&action=view) mdadm output Obtained by running "mdadm --examine /dev/sda*" while running rescue system. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 ------- Comment #10 from andreas.pfaller@gmail.com 2006-12-11 17:16 MST ------- Since I was running out of ideas I opted for a complete reinstall. The differences from my previous attempt are: - No separate /boot partition - Only one primary partition (sd[ab]1 - not used for install). The previous attempt had a primary partition (sd[ab]3) physically located behind the extended partition - this worked without problem on the same hardware with 10.1. The reason for this layout was to ease replacement of a raid component drive if one of the drives fails and the replacement has a slightly smaller capacity. This new installation also did not install a working grub configuration. However after installing grub with

root (hd0,4) setup (hd0) from the rescue system the system booted unlike my previous attempt where the initrd failed to assemble the root fs (see boot log of comment #9).

-- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 jsuchome@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |fehr@novell.com ------- Comment #11 from jsuchome@novell.com 2006-12-18 02:03 MST ------- Thomas, isn't this a partitioner problem? -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 ------- Comment #13 from andreas.pfaller@gmail.com 2006-12-18 07:56 MST ------- Thomas, I think you misread my description. The system WITH a separate boot had problems which failed in the initrd. My first try had a boot partition (sda1,sdb1). / was the first extended partition (sda5,sdb5). In both my tries the partition layout was created completely manually by me with the installation system partitioner. Both attempts also failed to create a working grub configuration (configuration left unchanged from the default proposal of the installer). -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 ------- Comment #15 from stefan.fent@novell.com 2006-12-20 01:39 MST ------- As the serial output looks ok (the kernel commandline is correct) I doubt this is a bootloader problem. For some reasons, /dev/md1 seems to be broken. /boot being a software RAID is problematic, though. stage2 bootloader requires to be on the same physical blocks on both disks, which can't be guaranteed with YaST partitioning the disks. /etc/grub.conf looks broken to me, it should be: setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0) setup --stage2=/boot/grub/stage2 (hd1,0) (hd1,0) ^ -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 ------- Comment #17 from andreas.pfaller@gmail.com 2006-12-20 07:26 MST ------- Sorry, somehow Firefox sent comment #16 before I was finished. I am not really familiar with grub but shouldn't the correct setup for raid-1 be: setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0) device (hd0) /dev/sdb setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0) I have not tested it yet but I think the above command will assure that sdb will be properly booted if sda completely fails or is removed as it will be the the new "0" drive for the BIOS. Different physical blocks should not really happen for stage1 because raid-1 should guarantee the they are located in identical blocks. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 ------- Comment #19 from andreas.pfaller@gmail.com 2006-12-21 12:59 MST ------- Stefan, you got me confused: I thought the "device (hd0) /dev/sdb" command essential makes grub use /dev/sdb whenever the grub "hd0" specification is used. So the 2nd setup command should install grub on /dev/sdb. At least for my current setup (see below) this works - I have verified that the system is bootable from both disks by temporary removing /dev/sda and for the next try /dev/sdb. I even zeroed the relevant disk sectors and they were restored on both disks by grub (the stage1.5 sectors, see below). Regarding the modification of stage2: Thanks for the hint Stefan, I was not aware of this problem. (Note: I meant stage2 in the last paragraph of my comment #17). Currently I have installed grub with device (hd0) /dev/sda root (hd0,4) setup (hd0) and device (hd0) /dev/sdb root (hd0,4) setup (hd0) and as far as I interpret grubs output this should be safe as this install stage1.5 in the physical sectors (1-15) (i.e. outside of any mirrored partition) and as stage1.5 understands ext2 it should have no problems finding stage2 even if the sectors occupied by stage2 change or are not identical because of different physical positions of the raid component partitions. And as I said above I have verified that it works as expected on my system. Shouldn't YaST enforce something like this automatically as soon as /boot gets installed inside an raid-1 partition? One thing however still make me nervous. Does grub's e2fs_stage1_5 understand all current ext2 features? dir_index may be a problem. A further suggestion: All documentation I found regarding the combination of raid/grub while googling is highly contradicting. It would be nice if SuSE manual would provide some details about this quite common scenario. This leaves the problem with initrd failing to assemble the root device. In hindsight I should have opened a separate bugzilla entry for this. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 ------- Comment #21 from andreas.pfaller@gmail.com 2006-12-29 00:22 MST ------- The result from comment #20 surprises me. My first attempt had a separate /boot on ext2! While I could fix grub from the rescue system I never figured out how to make it past the initrd. With my second installation attempt boot was put on my root partition which is ext3! That attempt also created a non working grub installation (fixed again from the rescue system, final version see comment #19) and booted normally after that. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 ------- Comment #23 from andreas.pfaller@gmail.com 2006-12-31 08:53 MST ------- Markus, if you look at the many details I have provided above you will see that the bootable flag was set on the boot partition (see comment #7). -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377 odabrunz@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #25 from odabrunz@novell.com 2007-02-23 05:35 MST ------- I looked into this, but could not find any quick answer. Since software-RAID issues have been postponed until after SLES10 SP1, I will work on this for 10.3 (earliest?). -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227377#c27 --- Comment #27 from Richard Creighton 2007-07-03 17:39:23 MST --- Apparantly this *used* to work in 10.o. see: HOWTO: SUSE 10.0 and Software RAID a.k.a FakeRAID http://www.howtoforge.com/forums/showthread.php?t=1664 It appears that dmraid looks for a module 'raid45' but 10.2 & 3Ax load 'raid456' -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=227377#c29 --- Comment #29 from Richard Creighton 2007-08-14 10:34:46 MST --- Created an attachment (id=157474) --> (https://bugzilla.novell.com/attachment.cgi?id=157474) Partition information on MD raid system used exhibiting bug -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=227377#c31 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|franz.x.maier@aon.at | --- Comment #31 from Stephan Kulow 2007-09-08 00:08:26 MST --- info provided -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=227377#c32 Leonce Eraly changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leo@kangaroot.net --- Comment #32 from Leonce Eraly 2007-09-25 01:32:53 MST --- The problem is still present in SLES10 SP1. I did some recent installs on IBM blades with 2 simple SAS disks sda1 -> md0 sdb1 -> md0 sda2 -> md1 sdb2 -> md1 My /dev/md1 contains my ext3 root filesystem, the first stage of the installation goes well (no errors) but if I reboot my system stops with 'No operating systems found'. To fix this I boot again with my SLES10 SP1 cd , go to the rescue system. Once I'm in the rescue system , I mount /dev/md1 under /mnt , chroot into /mnt , create the proper device files with mknod mknod /dev/sda b 18 0 , mknod /dev/sda2 b 18 2 , .... I start grub , and I execute the following commands: root (hd0,1) setup (hd0) root (hd1,1) setup (hd1) quit I also add an extra entry to my grub config. So 1 entry for disk0 which points to hd0 and a second entry for disk1 which is identical to the first one except for the hd1 part. As a final step I unmount /mnt , reboot and everything works! -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=227377#c35 Stefan Fent changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID --- Comment #35 from Stefan Fent 2007-10-10 05:10:03 MST --- The bootloader can't write to /dev/md, it has to write to the devices directly. As the combination of ext3 and md destroys this information again, this doesn't work, so you have to use ext2 / reiserfs. --> invalid. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=227377 Matej Horvath changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |stefan.fent@novell.com Status|REOPENED |NEW -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=227377#c38 Joachim Plack changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Component|Installation |Installation Product|openSUSE 10.3 |openSUSE 11.0 Version|Final |unspecified --- Comment #38 from Joachim Plack 2007-10-26 05:22:06 MST --- we'll address the root on Raid1 issues in the code11 cycle in a way that is less error prone and works on all systems, all Bioses and with all file systems. in the meantime the above setup is not supported as it works on some machines and on some no, given the test results above, so do not expect a maintenance update. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=227377 User jplack@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=227377#c40 Joachim Plack changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |LATER --- Comment #40 from Joachim Plack 2007-12-12 13:03:54 MST --- No ressources assigned here right now, will address problem later -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=227377 User jplack@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=227377#c42 Joachim Plack changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jplack@novell.com Status|RESOLVED |REOPENED Resolution|LATER | --- Comment #42 from Joachim Plack 2008-03-19 22:13:49 MST --- reevaluate for SLE11 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=227377 User jplack@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=227377#c43 Joachim Plack changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jplack@novell.com |juhliarik@novell.com Status|REOPENED |NEW --- Comment #43 from Joachim Plack 2008-07-15 05:21:44 MDT --- assign to yast2-bootloader maintainer -- 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.