[Bug 706411] New: YaST2 fails to install on RAID5 on a ASUS-mainboard P7P55D-E with Intel Core i7
https://bugzilla.novell.com/show_bug.cgi?id=706411 https://bugzilla.novell.com/show_bug.cgi?id=706411#c0 Summary: YaST2 fails to install on RAID5 on a ASUS-mainboard P7P55D-E with Intel Core i7 Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: arakora.hoguanebu@t-online.de QAContact: jsrain@novell.com Found By: --- Blocker: --- Created an attachment (id=440577) --> (http://bugzilla.novell.com/attachment.cgi?id=440577) log of the failed yast2 installation User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; MATM) In the BIOS of the ASUS mainboard P7P55D-E with INTEL Core i7 (64bit) processor and 8GB RAM I applied a RAID5 with 4 SATA-II-harddrives (Samsung HD642JJ, 640GB). Graphic-card = ATi Radeon HD5850 The RAID is recognized by Yast2 and I declare the following partitions: 1,7 TB enhanced, in it the following: part5 = /boot 70.60MB part6 = swap 8.2GB part7 = / 40GB part8 = /var 200GB part9 = /usr 400GB part10 = /home 500GB part11 = /data 500GB (Rest) (everything on EXT4) Start bootloader from MBR. Yast2 lets me do all the configuring and is running fine until it starts to format the partitions/harddisks: At this step it changes the size of every partition from GB to TB. Of course this is to much and it pops up a window to tell me that on each partition. No matter if I confirm or not: Yast hangs up and I have to reboot. Reproducible: Always Steps to Reproduce: 1. Apply RAID5 on mainboard ASUS P7P55D-E with Intel Core i7 2. Start Yast2 from installation-CD of openSuSE 11.4 3. enter partitions as described in "Details" 4. continue Yast Actual Results: Yast is doing all installation steps except the formatting of the harddisks/partitions on the RAID5: the volume size is changed from GB to TB. Yast hangs up. Expected Results: I expect Yast to run through the whole installation. If I do not apply a RAID5, but install on the separate harddisks, everything is running fine. -- 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=706411 https://bugzilla.novell.com/show_bug.cgi?id=706411#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- 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=706411 https://bugzilla.novell.com/show_bug.cgi?id=706411#c Arvin Schnell <aschnell@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@novell.com AssignedTo|yast2-maintainers@suse.de |aschnell@novell.com -- 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=706411 https://bugzilla.novell.com/show_bug.cgi?id=706411#c1 Arvin Schnell <aschnell@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aschnell@novell.com |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #1 from Arvin Schnell <aschnell@novell.com> 2011-07-19 09:42:36 UTC --- After creating partition 5 on md126 YaST checks the size in sysfs. This is sometimes required since parted can fail to inform the kernel about changes to the partition table. Apparently the partition is unknown to the kernel so YaST calls delpart and addpart. After that the partition is known to the kernel but the start and end values are multiplied by 512.
From the logs:
/usr/sbin/addpart '/dev/md126' 5 768 144000 addpart failed sysfsBlkRegion:[393216,73728000] (YaST logs this since the values mismatch) 259 1 36864000 md126p5 (/proc/partitions) You can see that the values we read from sysfs are 512 times the values passed to addpart. The sizes in /proc/partitions are also to large (and much larger than the disk). To the customer: The problem should not occur if the disk is already partitioned during installation and you only format and assign mount points. You could either partition from the rescue system or restart the installation after the failure. -- 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=706411 https://bugzilla.novell.com/show_bug.cgi?id=706411#c2 Horst G. A. Butz <arakora.hoguanebu@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |arakora.hoguanebu@t-online. |ovo.novell.com |de --- Comment #2 from Horst G. A. Butz <arakora.hoguanebu@t-online.de> 2011-07-26 15:51:35 UTC --- Created an attachment (id=442410) --> (http://bugzilla.novell.com/attachment.cgi?id=442410) 2nd log of the further failure of YaST2 YaST2 fails at system reboot after 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=706411 https://bugzilla.novell.com/show_bug.cgi?id=706411#c3 --- Comment #3 from Horst G. A. Butz <arakora.hoguanebu@t-online.de> 2011-07-26 15:59:36 UTC --- I did as recommended and restarted the installation until every partition was formatted and the mount points were assigned properly. Everything seemed fine till YaST started the system new: hang up again. -- 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=706411 https://bugzilla.novell.com/show_bug.cgi?id=706411#c Horst G. A. Butz <arakora.hoguanebu@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=706411 Horst G. A. Butz <arakora.hoguanebu@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Horst G. A. Butz <arakora.hoguanebu@t-online.de> --- this bug was resolved by myself (user) in the year 2011 already. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com