https://bugzilla.novell.com/show_bug.cgi?id=712177 https://bugzilla.novell.com/show_bug.cgi?id=712177#c1 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |fehr@novell.com --- Comment #1 from Thomas Fehr 2011-08-15 10:53:43 UTC --- Reassigned to maintainter of yast2-storage -- 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=712177 https://bugzilla.novell.com/show_bug.cgi?id=712177#c3 --- Comment #3 from Günther J. Niederwimmer 2011-08-15 11:50:17 UTC --- Created an attachment (id=445794) --> (http://bugzilla.novell.com/attachment.cgi?id=445794) Grub Menu List -- 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=712177 https://bugzilla.novell.com/show_bug.cgi?id=712177#c5 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gjn@gjn.priv.at --- Comment #5 from Thomas Fehr 2011-08-15 12:27:42 UTC --- I can only see what is contained in the logs. The logs did not contain any created partitions but the following: INSTALL INFO info:Formatting device /dev/md126p11 (501.00 MB) with ext4 INSTALL INFO info:Formatting device /dev/md126p5 (20.07 GB) with btrfs INSTALL INFO info:Formatting device /dev/md126p6 (15.00 GB) with btrfs INSTALL INFO info:Mounting /dev/sdd1 to swap INSTALL INFO info:Adding entry for mount point swap to /etc/fstab INSTALL INFO info:Mounting /dev/md126p5 to / INSTALL INFO info:Adding entry for mount point / to /etc/fstab INSTALL INFO info:Mounting /dev/md126p11 to /boot INSTALL INFO info:Adding entry for mount point /boot to /etc/fstab INSTALL INFO info:Mounting /dev/md126p6 to /home INSTALL INFO info:Adding entry for mount point /home to /etc/fstab INSTALL INFO info:Mounting /dev/md126p1 to /windows/C INSTALL INFO info:Adding entry for mount point /windows/C to /etc/fstab INSTALL INFO info:Mounting /dev/md126p2 to /windows/D INSTALL INFO info:Adding entry for mount point /windows/D to /etc/fstab INSTALL INFO info:Mounting /dev/md126p3 to /windows/E INSTALL INFO info:Adding entry for mount point /windows/E to /etc/fstab INSTALL INFO info:Mounting /dev/md126p10 to /windows/F INSTALL INFO info:Adding entry for mount point /windows/F to /etc/fstab INSTALL INFO info:Creating subvolume @/tmp on device /dev/md126p5 INSTALL INFO info:Creating subvolume @/opt on device /dev/md126p5 INSTALL INFO info:Creating subvolume @/srv on device /dev/md126p5 INSTALL INFO info:Creating subvolume @/var/spool on device /dev/md126p5 INSTALL INFO info:Creating subvolume @/var/log on device /dev/md126p5 INSTALL INFO info:Creating subvolume @/var/run on device /dev/md126p5 INSTALL INFO info:Creating subvolume @/var/tmp on device /dev/md126p5 This looks ok. The menu list contains root=/dev/disk/by-uuid/89f535a8-6404-4edb-951f-1a8944467707 which should be fine as long as the devices are set up correctly in mkinitrd. It seems mkinitrd does not detect that it needs feature md added to initrd. Maybe this is caused by having UUID= in /etc/fstab instead of /dev/md0p... but it is perfectly legal to have the root fs mounted by UUID. Please try the following: 1) run "mkinitrd -f md" in your system (after set up manually e.g. from rescue media) this should add feature md to initrd and then initrd should start md devices 2) reinstall and change mount-by option for root fs to "mount by id" or "mount by device". While "mount by UUID" is default for BTRFS one can change the default like any other fstab entries 3) do an install where partitions are created an attach y2log so that I can see what happens in such a case. Unfortunately Arvin who has much more knowledge with partitonable raid stuff is on vacation but will be back next Wednesday. it is true that your raids can either be configured by mdadm or dmraid. In the log you attached you said that mdadm should handle your raids. Lets simply stay with mdadm until we see where the problems are. -- 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=712177 https://bugzilla.novell.com/show_bug.cgi?id=712177#c7 Günther J. Niederwimmer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gjn@gjn.priv.at | --- Comment #7 from Günther J. Niederwimmer 2011-08-20 14:16:09 UTC --- I Tested it again with this board and creatre a new Partition with YaST2 this is the Problem "Picture" I tested it also on a older Board with ICH7 and a RAID 5 on this Computer I Have not so much Problems ? The different are ICH7 / ICH10 the Name that is configured volume0 / Volume0 -- 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=712177 https://bugzilla.novell.com/show_bug.cgi?id=712177#c9 --- Comment #9 from Günther J. Niederwimmer 2011-08-21 10:17:17 UTC --- I forgot :(, the different are Newer System ICH10 Raid1 Name of the Volume "Volume0" Older System ICH7 Raid5 Name of the Volume "volume0" The Error is from the newer System I found also a Kernel Parameter "dodmraid" and tested it but it is not working. -- 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=712177 https://bugzilla.novell.com/show_bug.cgi?id=712177#c11 --- Comment #11 from Thomas Fehr 2011-08-24 09:31:22 UTC --- While testing for SLES 11 SP2 I fixed a bug in handling dmraid stuff that also exists in openSuSE 12.1 so maybe this fix will also fix your problem. Fix will be available with Milestone 5. -- 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=712177 https://bugzilla.novell.com/show_bug.cgi?id=712177#c13 --- Comment #13 from Thomas Fehr 2011-08-24 11:50:48 UTC --- I cannot do much without y2log file. I do not have access to this hardware here. While the error popup is displayed you can still save y2log files (yast2 and inst-sys terminates after you press return in error popup): http://en.opensuse.org/openSUSE:Bugreport_YaST#I_get_a_red_text_pop-up_telli... The translation is a little strange (as most translations of such a deeply technical fact are). I would advise to use English language for 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.

https://bugzilla.novell.com/show_bug.cgi?id=712177 https://bugzilla.novell.com/show_bug.cgi?id=712177#c15 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@novell.com AssignedTo|fehr@novell.com |puzel@novell.com --- Comment #15 from Thomas Fehr 2011-08-24 16:52:44 UTC --- Ok, here you said "no" to the question if your raid should be managed by md driver. The consequences is that your raid is managed by dmraid and your device names are /dev/mapper/isw_cecaadgiie_Volume0 for the dmraid "disk" and /dev/mapper/isw_cecaadgiie_Volume0_part[0-9]+ for the "partitions" of that disk. In the log attached in initial report you said "Yes" to the question and your raids were afterwards managed by md driver. Your raid "disk" was /dev/md126 and your "partitions" were /dev/md126p[0-9]+. So this works as expected so far. The problem with partitioning the dmraid device seems to one with parted. parted seems to have a problem handling creation (and removal) of logical partitions on dm devices. Petr: My tests here show that the problem starts after the first logical partition is created (creation partition 5 still works), creation of the second logical partition (partition 6) fails: inst-sys:~ # parted --align=optimal /dev/mapper/isw_cfffigicif_test2 GNU Parted 2.3 Using /dev/mapper/isw_cfffigicif_test2 Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) mklabel msdos Warning: The existing disk label on /dev/mapper/isw_cfffigicif_test2 will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? Y (parted) p Model: Linux device-mapper (mirror) (dm) Disk /dev/mapper/isw_cfffigicif_test2: 10.5GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags (parted) mkpart primary 1M 200M (parted) mkpart primary 200M 2G (parted) mkpart primary 2G 5G (parted) mkpart extended 5G 10.5G (parted) mkpart logical 5G 6G (parted) mkpart logical 6G 7G device-mapper: remove ioctl failed: Device or resource busy Warning: parted was unable to re-read the partition table on /dev/mapper/isw_cfffigicif_test2 (Device or resource busy). This means Linux won't know anything about the modifications you made. (parted) quit Information: You may need to update /etc/fstab. inst-sys:~ # dmsetup table isw_cfffigicif_test2_part5: 0 1951744 linear 253:4 2048 isw_cfffigicif_test2_part4: 0 10704896 linear 253:0 9764864 isw_cfffigicif_test2: 0 20470528 mirror core 2 16384 nosync 2 8:16 0 8:32 0 1 handle_errors inst-sys:~ # Reassigning to parted 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.

https://bugzilla.novell.com/show_bug.cgi?id=712177 https://bugzilla.novell.com/show_bug.cgi?id=712177#c16 --- Comment #16 from Günther J. Niederwimmer 2011-08-27 12:05:30 UTC --- Created an attachment (id=448032) --> (http://bugzilla.novell.com/attachment.cgi?id=448032) Yast2 Log on primary Partition This is a Installation on a clear Disk RAID 1 This is not a extended Partition, but a EFI 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.

https://bugzilla.novell.com/show_bug.cgi?id=712177 https://bugzilla.novell.com/show_bug.cgi?id=712177#c18 Petr Uzel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |DUPLICATE --- Comment #18 from Petr Uzel 2011-09-07 15:21:11 UTC --- Duplicate, both fixed in Factory. *** This bug has been marked as a duplicate of bug 679780 *** http://bugzilla.novell.com/show_bug.cgi?id=679780 -- 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.