On Tue, 2007-01-02 at 03:41 +0100, Eberhard Moenkeberg wrote: > Hi, > > On Mon, 1 Jan 2007, Kenneth Schneider wrote: > > On Sun, 2006-12-31 at 12:49 -0600, Glenn Holmer wrote: > > > On Sunday 31 December 2006 11:47, Kenneth Schneider wrote: > > > > > "The partitioning on disk /dev/cciss/c0d0 is not readable by the > > > > partitioning tool parted, which is used to change the partition > > > > table. > > > > > > https://bugzilla.novell.com/show_bug.cgi?id=219496 > > > > > > There's an expert option on the partitioning screen that will allow you > > > to blow away the existing partition table and recreate it, then you can > > > install. > > > > > > > Doesn't help when doing an upgrade rather then a fresh install. > > So take a console (ALT-CTRL-F2) as early as possible and use fdisk. > It must be before YaST is reading your partition table. > > Cheers -e
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. Ken --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
