Bug 391756

Summary: Installation Problems (Partitioning) Intel onboard RAID
Product: [openSUSE] openSUSE 11.0 Reporter: Martin Forst <m.forst>
Component: InstallationAssignee: Neil Brown <nfbrown>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P4 - Low CC: adam.cetnerowski, aschnell, forgotten_0LOspkIJyJ, jason.d.gaston, kent.liu, marc.ruehrschneck, marcin.labun, youquan.song
Version: Beta 3   
Target Milestone: openSUSE 11.1   
Hardware: i686   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Kernel and YaST log of openSUSE 11.0 install system
Parted output for running RC1 system

Description Martin Forst 2008-05-17 10:19:06 UTC
I have a system with a running openSUSE 10.3 installation. I wanted to update to 11.0 (tried Betra2 and Beta 3). The installation program does not find the partition where 10.3 is installed. Installation also does not allow to make a new installation on the RAID array.

Hardware: Asus P5B-E Motherboard (Intel P965 with ICH8R)
Core Duo E6600
2 GBytes RAM
2 Samsung Spinpoint HD250HJ

Partitions:
80 GByte NTFS, Windows XP installed, Vista bootloader
160 GByte Extended partition, containing 80 GByte NTFS data and 80 GBytes NTFS with Vista installed
150 GBytes Ext3 parition with openSUSE 10.3 installed (all in one partition, no boot or swap partition)

Linux bootloader is installed in MBR of the linux parition. Linux is started using 
Vista bootloader, set up by EasyBCD.

Update does not allow to select any parition, the partitions list presented is empty.

Installation shows the raid partitions as DM partitions but does not allow to select them for installation.
Comment 1 Stephan Kulow 2008-05-17 16:11:11 UTC
please provide your yast and your kernel logs.
Comment 2 Martin Forst 2008-05-17 17:16:31 UTC
Created attachment 216194 [details]
Kernel and YaST log of openSUSE 11.0 install system
Comment 3 Robert Vojcik 2008-05-22 14:25:17 UTC
Please next time remove NEEDINFO status by selecting "This comment/atachment 
provides ..." checkbox after supplying needed information. Reassigning to maintainer.
Comment 4 Arvin Schnell 2008-05-23 09:55:52 UTC
From the logs I see:

- dmraid detects the raid 'isw_ceehdaebbf_Volume1'.

- parted cannot read the partition table on it, reports "Error:
  Unable to satisfy all constraints on the partition.". fdisk
  can read the partition table.

- later dmraid cannot give further information about the raid but
  reports 'No RAID sets and with names: "isw_ceehdaebbf_Volume1"'.

Matthias, any idea why dmraid what could cause the last issue?
Comment 5 Martin Forst 2008-06-02 10:07:33 UTC
Created attachment 219469 [details]
Parted output for running RC1 system
Comment 6 Martin Forst 2008-06-02 10:08:19 UTC
There seems to have been a problem with my partition tables. I used parted to check them on the running 10.3, displayed the same error messages. When parted was called directly with the partition names it reported two different error messages, one saying "partition outside disk" and one saying "overlapping paritions".

I then tried RC1, same result.

While palying around i lost two Vista partitions. After restoring them with Acronis I tried to setup SuSE again, Beta 2 didn't work, RC1 worked (although same parted version number 1.8.8).

I dont know why the problem occurred, all partitions have been created using Norton PartitionMagic 8.0, whos checking functions also didnt report any errors for the parition table.

I now have running RC1. Partitioning with YaST works correctly now, partitions are shown correctly and can be accessed correctly.

parted also prints the parition table correctly. But when called with the partition names it reports "partition outside disk" for all partitions except the SuSE root parition, which can be accessed (see attachment).

Conclusion: parted still seems to have troubles with dmraid partitions.
Comment 7 Matthias Koenig 2008-06-02 12:39:38 UTC
The 3rd problem in comment #4 is related to a bug in dmraid, which
I can also reproduce with my ISW test RAID, it probably also affects
the DDF1 format.
These formats create a RAID set of type GROUP, which is a abstract
superset which contains the actual RAID set. When dmraid searches for
a wanted RAID set (the one given on the commandline) it first hits the
GROUP superset, but as the names does not match dmraid deletes the set.
But it seems to delete it recursively, so it also deletes the RAID set
it was searching for and cannot find it anymore.
I have now a fix for this, which needs to be discussed upstream
(https://www.redhat.com/archives/ataraid-list/2008-June/msg00000.html).

Despite of this, there should not be any problems when enabling the RAID with
dmraid -ay -p
Comment 8 Arvin Schnell 2008-07-15 17:23:00 UTC
*** Bug 406681 has been marked as a duplicate of this bug. ***
Comment 10 Neil Brown 2009-12-15 03:54:00 UTC
I believe this bug was fixed in dmraid-1.0.0.rc15 which was included
in openSUSE 11.1 (11.0 had -rc14).