Bugzilla – Bug 246918
Segmentation fault at Storage.ycp
Last modified: 2007-02-20 13:49:49 UTC
Command: /sbin/yast2 disk & Segmentation fault at Storage.ycp:1416 /sbin/yast2: line 274: 3965 Segmentation fault $ybindir/y2base $module "$@ " "$SELECTED_GUI" "$Y2_GEOMETRY" $Y2QT_ARGS The partition program crashes when I have five disks attached, but it is ok if I have one. (indeed I partitioned and installed on root)
Need y2log files. How much memory do you have?
Additioanlly the output of "rpm -qa | grep yast2-storage" would be interesting.
Created attachment 120085 [details] /var/log/YaST2 tar files d-> cat /proc/meminfo MemTotal: 1026020 kB MemFree: 790932 kB Buffers: 592 kB Cached: 185116 kB SwapCached: 0 kB Active: 106680 kB Inactive: 93296 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 1026020 kB LowFree: 790932 kB SwapTotal: 1052248 kB SwapFree: 1052248 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 14320 kB Mapped: 7836 kB Slab: 19432 kB PageTables: 2352 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 1565256 kB Committed_AS: 50568 kB VmallocTotal: 34359738367 kB VmallocUsed: 14344 kB VmallocChunk: 34359724015 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 Hugepagesize: 2048 kB d-> rpm -qa | grep yast2-storage yast2-storage-2.14.18-3 yast2-storage-lib-2.14.18-3 yast2-storage-evms-2.14.18-3
This is a duplicate of bug #223843. Problem is caused by a invalid dmraid on your disk /dev/sdc. The command "dmraid -s -c -c -c" detects a dmraid on /dev/sdc and when YaST2 trys to query the dmraid it is not really there and YaST2 crases. I assume you are not really using the dmraid on /dev/sdc but it just happens to be there because the disk was part of a dmraid in a previous syste. The bug that causes YaST2 crashing is already fixed in current code base for SL 10.3. You have the following possibilities as workaround: - remove raid signature on /dev/sdc by calling "dmraid -E -r /dev/sdc" - set the environment variable YAST2_STORAGE_NO_DMRAID before calling YaST2. This tells YaST2 to skip dmraid detection. *** This bug has been marked as a duplicate of bug 223843 ***