https://bugzilla.novell.com/show_bug.cgi?id=777067 https://bugzilla.novell.com/show_bug.cgi?id=777067#c1 --- Comment #1 from Felix Miata 2012-08-23 18:18:03 UTC --- After reducing partition count to 35, which alone did not help on next try, I tried again with BrokenModules=hptiop,hpt37x,scsi_dh,raid0,raid10,raid456,raid6_pq,dm_mod,dm_multipat and got what appeared to be a complete minimal installation + apache + samba/cifs + nfs-kernel-server. Y2logs for the subsequent install available on request. -- 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=777067 https://bugzilla.novell.com/show_bug.cgi?id=777067#c3 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com AssignedTo|aschnell@suse.com |nfbrown@suse.com --- Comment #3 from Arvin Schnell 2012-08-24 08:12:38 UTC --- The disk sdc is part of a BIOS RAID: /sbin/dmraid -s -c -c -c hpt37x_ccedfbhiib:156301440:128:mirror:ok:0:1:0 /dev/sdc:hpt37x:hpt37x_ccedfbhiib:mirror:ok:156301477:10 But the RAID is broken: /sbin/dmraid -ay -p ERROR: creating degraded mirror mapping for "hpt37x_ccedfbhiib" RAID set "hpt37x_ccedfbhiib" was activated RAID set "hpt37x_ccedfbhiib" was not activated So for YaST sdc is used by the RAID and its partitions are not shown. Why the RAID is broken or why dmraid doesn't setup device-mapper tables for the partitions I cannot say. Adding hpt37x to broken modules disables the BIOS RAID completely and the system behaves like you expected. Anyway, removing the BIOS RAID signature from the disk is a better solution. Neil, can you comment on the behavior of dmraid? -- 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=777067 https://bugzilla.novell.com/show_bug.cgi?id=777067#c5 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mrmazda@earthlink.net | --- Comment #5 from Felix Miata 2012-08-24 10:58:22 UTC --- Created an attachment (id=503405) --> (http://bugzilla.novell.com/attachment.cgi?id=503405) tar -cvf of dmraid -r -D /dev/sdc output As I wrote in comment 0, this sdc has mostly ever been used as a backup device, and likely was never booted except to its DOS partition until attempting to put 12.2 on it. IIRC, this SATA device was initialized by cloning from an 80G PATA disk that had once been installed in a system that did have a hpt3xx controller enabled for fake RAID, but there have been no working systems with hpt3xx controllers here in many many moons. I've now wiped 0x3d sectors starting @ 0x01 on sdc. Could YaST have done this for me while I was attempting to install? -- 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=777067 https://bugzilla.novell.com/show_bug.cgi?id=777067#c7 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #7 from Arvin Schnell 2012-10-02 11:56:07 UTC --- Ok, what might have confused me is that although it's a mirror RAID parted detects no partitions. But that's due to an offset on the RAID: /sbin/dmsetup table 'hpt37x_ccedfbhiib' 0 156301477 linear 8:32 10 Assuming this is correct there is indeed nothing wrong. The user is also able to delete the RAID in YaST as Neil mentions. YaST has a column names "Used By" and the overview for sdc also shows the "used by" information. All operations on sdc also also display a popup that the disk is in use. So I don't see room for improvement. -- 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.