https://bugzilla.novell.com/show_bug.cgi?id=862187 https://bugzilla.novell.com/show_bug.cgi?id=862187#c0 Summary: Yast2/bootloader and yast2/partitioner allways crash Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i386 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers@suse.de ReportedBy: w.pelser@web.de QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; YPC 3.0.1; NET CLR 1.1.4322; .NET CLR 2.0.50727) The new Version (3.1.17-2.10) from build.opensuse.org/YAST: Yast/bootloader and yast/partitioner stop allways with:"undefined method `empty' for #Storage::ListString:0x977951c" The old Version of yast (3.0.11-7.1) from Suse 13.1 had no problems, also if I go back from (3.1.17-2.10)! Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: crash it seems to be a Raid-problem libstorage can manage this, but ruby does not. RAID: Intel Matrix Storage Manager option ROM v5.6.2.1002 ICH7R wRaid5. /proc/partitions: major minor #blocks name 8 0 312571224 sda 8 16 312571224 sdb 8 32 976762584 sdc 8 33 52436160 sdc1 8 34 52436129 sdc2 8 35 1 sdc3 8 36 767031457 sdc4 8 37 2096451 sdc5 8 38 102759741 sdc6 9 126 625137664 md126 259 0 52427776 md126p1 259 1 1 md126p2 259 2 52428288 md126p3 259 3 258140672 md126p4 259 4 5245184 md126p5 259 5 20980736 md126p6 259 6 235913216 md126p7 11 0 1048575 sr0 11 1 1048575 sr1 8 48 8097792 sdd 8 49 6482227 sdd1 8 50 1614848 sdd /proc/mdstat: Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md126 : active raid0 sda[1] sdb[0] 625137664 blocks super external:/md127/0 128k chunks md127 : inactive sda[1](S) sdb[0](S) 4524 blocks super external:imsm unused devices: <none> md127 seems to be the problem. I wonder what this is. I have called the raid-disk "maindisk", but this is md126. How can I write a new /proc/mdstat and probably get rid of this md127 or what does this md127 mean???? I´m interested, how to solv my problem without destroying the raid-system. Thanks W.Pelser -- 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.