http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c yang xiaoyu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |mmarek@novell.com |ovo.novell.com | -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c2 --- Comment #2 from Dennis Olsson 2010-03-17 00:01:49 CET --- After having done some more debugging, it seems that there is also a problem with "mkinitrd". After having installed the packages, YaST issues a pop-up window with a count down to a reboot. During this reboot MD device does *not* get (re)activated, which then causes problems with the next stage of the installation process, while the disk setup is now screwed-up (in my case the LVM gets activated using "/dev/sdb3" instead of "/dev/md/raid1p3"!). But, instead of using the YaST "reboot", it does not help either to do a real reboot, while the MD device does *not* get activated during the running of the "initrd" either! The reason why the MD device does not get initialized during the running of the "initrd" is that the "md_dev" variable tested for in "boot/51-md.sh" has *not* been set, which means that "mdadm -A" does not get called! And thus does not assemble and starts the partitioned MD device. The "md_dev" variable is *only* getting set in either "boot/03-storage.sh" and here _only_ when the *root* device is a MD device (/dev/md*), i.e. when root is a MD device itself (which is not the case here -- see below), or "boot/51-md.sh" and here _only_ when the root device name consists of hexadecimal digits, i.e. (as far as I can deduce) when root is kept in a (MD) container. But, in this case, we have: /dev/sda + /dev/sdb => /dev/md/raid1 where /dev/md/raid1 has 3 (three) partitions: /dev/md/raid1p1 containing /boot file system /dev/md/raid1p2 containing swap device (used as resume device) /dev/md/raid1p3 containing LVM partition with volume group named "raid1" where the LVM volume group named "raid1" contains: /dev/raid1/root113 containing / file system In the used configuration (see comment #1) the "rootdev" is defined (in "/config/storage.sh") as "/dev/block/253:1" (device mapper minor 1), which has the consequence that the "md_dev" variable is being left empty, and thus not calling "mdadm -A". As I have not been able to figure out how "mkinitrd" determines how to setup these things, I cannot say what should be done for configurations like the one I am using. Instead, I stopped the YaST2 installation at the pop-up "reboot" countdown by clicking "Stop", switch to a text console, and made the following changes to the generated "initrd": config/md.sh (adding new line; only works, when doing "slow_boot=on"): md_dev="/dev/md/raid1" run_all.sh (added after line with "root_md"; only works, when doing "fast boot"): md_dev="/dev/md/raid1" etc/mdadm.conf (changed existing line to these two lines instead): ARRAY /dev/md/raid1 metadata=1.00 name=raid1 UUID=<value from existing file> HOMEHOST Loke Returning to the YaST console and clicking "OK" will *not* work, while for reasons I do not understand the MD device does _not_ get activated, resulting in LVM getting very confused about finding the volume group "raid1" twice on "/dev/sdb3" as well as "/dev/sda3", choicing "/dev/sdb3" over "/dev/sda3". It should not have - of course - seen the "/dev/sd*" partitions at all, but instead the "/dev/md/raid1p3" alias "/dev/md127p3" and have used this one instead. So, instead, after having replaced the "initrd" with the changes from above incorporated, I *rebooted* the system by issueing: vgchange -a n mdadm --stop /dev/md/raid1 reboot But, also here LVM gets confused -- this time, though, the MD device *does* get started, but the LVM activation still sees the "/dev/sdb3" and "/dev/md/raid1" and prefers "/dev/sdb3" over "/dev/md/raid1" (which, of course, should really have been "/dev/md/raid1p3"!). The reason for this confusion is that the MD activation only activates one device (here "/dev/sda"), but not the other device (here "/dev/sdb"), which is (also) part of the MD device! But, why not?? I have not been able to figure that one out... In any instances, the installation cannot be continued, while the root file system has a completely wrong setup, eventual corrupting it beyond repair. It seems that the changes made by Arvin Schnell to implement feature #305883 still needs a few fixes in YaST as well as "mkinitrd", before it works correctly. ;-) -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c4 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from Michal Marek 2010-03-23 14:12:42 UTC --- Fixed. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c6 --- Comment #6 from Dennis Olsson 2010-04-12 21:10:03 CEST --- Sorry, Michal, but using the newest packages from the mentioned repository in comment #16 in bug #589676#c16 does not fix the problem. I tried to do an installation yesterday using the "openSUSE 11.3 Milestone 2 DVD" as base and "http://download.opensuse.org/repositories/Base:/System/openSUSE_Factory/" as add-on product. The resulting system was (as expected) using "mdadm-3.0.3-22.1" and "udev-151-30.2". But this system still results in ending up with using "/dev/sdb3" over "/dev/md127p3", when activating the LVM. It also seems that the activation of the MD device does not do, what it is supposed to do. As far as I can see (although I currently cannot firmly confirm this - see below), it seems that the activation of the MD device only activates the "/dev/sda" part of the MD raid1 configuration ignoring the "/dev/sdb" disk. This behaviour is consistent with a "mdadm -A --scan", whereas when a mdadm -E --scan >/etc/mdadm.conf mdadm -A --scan -c /etc/mdadm.conf does a correct assembly of the MD raid1 device! I was using the following disk configuration (see also bug #586837 c#0): "/dev/sda" and "/dev/sdb" as physical disks. "/dev/md/raid1" configured out of "/dev/sda" and "/dev/sdb". Partitioned "/dev/md/raid1" with 3 partitions: "/dev/md/raid1p1" as "ext3" file system mounted as "/boot" using LABEL="boot113" "/dev/md/raid1p2" as "swap" partition with priority 10 using LABEL="resumep10" "/dev/md/raid1p3" as LVM volume named "raid1" LVM configured with: "/dev/raid1/root113" as "ext4" file system mounted as "/" using LABEL="root113" I am unfortunately not able to supply you with any outputs, while after the system has rebooted into the YaST installation console, the system freezes up ignoring *any* keys from the keyboard -- only a power off is possible! Also, when trying to reboot the system after the power off, each time the system gets to the point, where the graphic is running, *all* keyboard activity is *ignored*! What I do see, though, is that the system is complaining about the device mapper has already been activated and that the LVM is preferring "/dev/sdb3" over "/dev/md127p3", which most likely is due to the fact that the MD device was wrongly configured (the "/dev/sdb" is missing in the MD device). -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c8 --- Comment #8 from Arvin Schnell 2010-04-13 16:02:29 UTC --- Works for me with Milestone 5. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c10 Dennis Olsson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #10 from Dennis Olsson 2010-05-16 22:20:52 CEST --- Have tested with openSUSE 11.3 Milestone 6. Sorry to have to tell you, but it still does not work. Not only it is complicated through all the additionally bugs that have turned up in M6, but also because with M6 it is complicated by the fact that "mdadm" no longer creates the sub-directory "/dev/md", when issuing the command: mdadm --create /dev/md/raid1 --name="raid1" --homehost="Loke" --level="raid1" --metadata="1.0" --auto=part3 -v -n 2 /dev/sda /dev/sdb Instead only "/dev/md_d127" is created. Having awaited the sync'ing to finish, I do: mdadm --manage --stop /dev/md_d127 mdadm -A --scan After which you have the device "/dev/md127", but no "/dev/md/raid1" or "/dev/md/Denmark-VB:raid1", which then causes the creation of the following configuration setup to get confused -- See also attached screenshots. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c12 --- Comment #12 from Dennis Olsson 2010-05-16 22:36:33 CEST --- Created an attachment (id=362510) --> (http://bugzilla.novell.com/attachment.cgi?id=362510) Screenshot of grub error message. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c14 --- Comment #14 from Dennis Olsson 2010-05-16 22:46:15 CEST --- Created an attachment (id=362511) --> (http://bugzilla.novell.com/attachment.cgi?id=362511) Screenshot of failed 2nd stage of installation. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c16 Dennis Olsson changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 3 |RC 2 --- Comment #16 from Dennis Olsson 2010-07-07 02:11:33 CEST --- Have tested with openSUSE 11.3 RC2. Still does not work! After the installation procedure reaches the 1. reboot, the system cannot reboot correctly, in that it stops with the message "Waiting for device /dev/disk/by-label/root113 to appear: ............", a device node that never appears! For complete error messages, see attachment "20100707T0039 Error messages.jpg". After having tried with "Y", the boot sequence continues, but still cannot mount any of the file systems using "LABEL=<name>"; Here it fails to mount "/home" and "/boot" (attachment "20100707T0050 More errors.jpg"). In spite of these errors the installation procedure continues, although warning about "/home" not having been mounted, which may cause problems later on. Also, the MD device has not been correctly assembled (see also bug #588840c11), even to the extend that "/dev/sda" has been removed; Needed to re-add it manually. After having awaiting the resync'ing of the re-added "/dev/sda" disk, the system was rebooted to see, if it would be able to boot correctly. Unfortunately, the installed system cannot boot cleanly -- It has the same problem as during the 1. pre-install rebooting, i.e. is waiting on the "/dev/disk/by-label/root113" to appear! Answering "Y" to the question of using "/dev/mapper/system-root" instead, allows for the boot sequence to continue, but once again neither "/boot" (LABEL=boot) nor "/home" (LABEL=home) gets mounted! -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c18 --- Comment #18 from Dennis Olsson 2010-07-07 02:14:28 CEST --- Created an attachment (id=374132) --> (http://bugzilla.novell.com/attachment.cgi?id=374132) Error messages resulting from the 1. reboot during installation -- Continueing with "/dev/mapper/system-root", sort of... -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c20 --- Comment #20 from Arvin Schnell 2010-07-07 09:57:36 UTC --- In that case it looks like a duplicate of bug #619461. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586837 http://bugzilla.novell.com/show_bug.cgi?id=586837#c22 Dennis Olsson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #22 from Dennis Olsson 2010-07-07 13:12:51 CEST --- OK -- Thanks for looking into this and for the reference to bug #619461, which indeed seems to be the problem I am having. -- 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.