On Tue, 2007-01-02 at 14:46 +0100, Eberhard Moenkeberg wrote:
Hi,
On Tue, 2 Jan 2007, Kenneth Schneider wrote:
On Tue, 2007-01-02 at 03:41 +0100, Eberhard Moenkeberg wrote: <snip> You're missing the point. The disk is already partitioned, there should be no reason to use fdisk. The problem is that the partition names show as some strange name:
/dev/mapper/lsi_jhicccaiaa_part1 DM Raid (ext3 /dev/mapper/lsi_jhicccaiaa_part3 DM Raid (xfs)
and when I select what should be the proper partition for the upgrade (part3 with xfs) it tells me:
"No installed system that can be upgraded with this product was found on the selected partition"
Since the partition that I want to upgrade is on an xfs partition I cannot _upgrade_ my system.
Also the bug referenced shows this as resolved from Beta 2. If so why is it still around in the retail version?
I can also drop down to "F2" console and mount the proper partitions (/dev/ccissc/c0d0p3 is /, and /dev/cciss/c0d0p1 is /boot) without error.
What is if you mount by hand /dev/cciss/c0d0p3 -> /mnt /dev/cciss/c0d0p1 -> /mnt/boot and return to YaST? No chance to continue after YaST's failing mount attempts?
When I get to the language selection I dropped down to <alt-F2> and mounted the partitions. This had no effect on the install process, I still cannot "upgrade" my system. Another question I have is why are modules being loaded for the controller when it has clearly been loaded already while the install kernel is being loaded? This clearly points to a problem with parted and the "bug" has _NOT_ been "resolved" as stated in https://bugzilla.novell.com/show_bug.cgi?id=219496 (at lease not for openSUSE 10.2GM) Comment #2 From Thomas Fehr 2006-12-04 10:54:16 MST Problem fixed in STABLE and SLES10 SP1 apparently didn't make it into openSUSE 10.2 GM. Ken --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org