Bug 223843

Summary: Can't install Suse 10.2 YaST2 crash
Product: [openSUSE] openSUSE 10.2 Reporter: Dnaiel Dubiel <yogi>
Component: YaST2Assignee: Matthias Koenig <mkoenig>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None CC: aj, forgotten_3Fef81aWgP, locilka, psyche
Version: RC 1   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2logs
hwinfo

Description Dnaiel Dubiel 2006-11-27 10:36:17 UTC
This problem is with Open SUSE 10.2 beta 2 and RC1
When I try install a get something like that:

*** Starting YaST2***
Segmentation fault at Storage.ypc:1416
/usr/lib/YaST2/startup/YaST.call: line 451: 3016 Segmentation fault  (core dumped) $OPT_FBITERM y2base "$Y2_MODULE_NAME" $Y2_MODE_FLAGS $Y2_MODULE_ARGS $Y2_MODE $Y2_UI_ARGS

Hardware:
CPU: Intel Core Duo 1,86 1066 FSB 2MB Cash E6300
RAM: 1GB DDR2 PC4200 Good RAM GR533D264L4/1G
Mainboard: Gigabyte GA-965P-S3
HDD: 2x SEAGATE SATAII 250GB ->GSATA RAID 1
     2x SEAGATE SATAII 160GB
CDROM: LITE-ON SHM-165S65
Comment 1 Matej Horvath 2006-11-27 19:02:28 UTC
Please attach your yast log files.
http://en.opensuse.org/Bugs/YaST
Thank you.
Comment 2 Dnaiel Dubiel 2006-11-28 09:48:03 UTC
Created attachment 107151 [details]
y2logs
Comment 3 Dnaiel Dubiel 2006-11-28 09:48:28 UTC
Created attachment 107153 [details]
hwinfo
Comment 4 Dnaiel Dubiel 2006-11-28 11:07:27 UTC
OK i find the problem. Open SUSE start install when I delete raid matrix and disable the RAID in bios. So the problem is with GRAID controller.
Comment 5 Lukas Ocilka 2006-11-29 13:23:26 UTC
YaST2 exit code on level (1): 139

SystemCmd.cc(execute):160 SystemCmd Executing:"dmraid -s -c -c -c jmicron_GRAID
error:
SystemCmd.cc(doExecute):301 system (dmraid -s -c -c -c jmicron_GRAID           .) = -127
SystemCmd.cc(doExecute):305 system() Returns:-127
EvmsHelper.cc(cleanup):263 - lsock:-1 spath:/var/lib/YaST2/socket_libstorage_evms semid:0

GRAID and/or EVMS related (storage) -> reassigning to Thomas Fehr
Comment 6 Lukas Ocilka 2006-11-29 13:27:52 UTC
Konstruktor SystemCmd:"dmsetup table jmicron_GRAID           ." Nr:0
"Incorrect number of arguments"
"Usage:"
"dmsetup [--version] [-v|--verbose [-v|--verbose ...]]"

...etc
Comment 8 Thomas Fehr 2006-12-06 15:03:10 UTC
The dot is really a binary with value 0x01 or Ctrl-A.
I fixed now libstorage to not crash any more.

But I think this is a problem with dmraid in the first place since I cannot see
much sense in having blanks and and control characters as part of the raid name.
This raid name ends as a device name below /dev/mapper and it will certainly
cause problems to have device names containing blanks and control characters.

Reassigned to maintainer of dmraid.
Comment 9 Matthias Koenig 2006-12-06 16:11:27 UTC
Yes, this looks bogus.
Please dump metaformats with dmraid -rD in the rescue environment and attach the dumped files.
Comment 10 Matthias Koenig 2006-12-11 10:33:24 UTC
Anyway, it is evil to copy strings that are not zero terminated:
		sprintf(ret, "%s_%s%s", HANDLER, name, buf);

Fixed in stable.
Comment 11 Thomas Fehr 2006-12-20 09:44:57 UTC
*** Bug 227451 has been marked as a duplicate of this bug. ***
Comment 12 Thomas Fehr 2007-02-20 13:49:49 UTC
*** Bug 246918 has been marked as a duplicate of this bug. ***