Mailinglist Archive: yast-devel (128 mails)

< Previous Next >
Re: [yast-devel] Problem with lvm on hardware raid
  • From: Arvin Schnell <aschnell@xxxxxxx>
  • Date: Wed, 17 Feb 2010 23:05:22 +0100
  • Message-id: <20100217220522.GA8335@xxxxxxx>
On Wed, Feb 17, 2010 at 08:05:13PM +0100, Christian Ehrlicher wrote:

We've a similar problem like described in bug #231221 ( ). Yast can't create a
logical volume and fails with error -4017 (LVM_PV_STILL_ADDED)
--> /dev/block/104:3 needs a mapping to /dev/cciss/c0d0p3

It's correctly detected:
"dev_names":["/dev/cciss/c0d0", "/dev/block/104:0", "/dev/disk/by-
id/cciss-3600508b1001052395359305442350500", "/dev/disk/by-
path/pci-0000:06:00.0", "/dev/disk/by-id/edd-int13_dev80"]
I can provide the full y2log - but it's huge and therefore I decided to only
append the error part.

When I'm correct I need to add an additional check for /dev/cciss in
Storage::findVolume() ( - is this correct?

The normal way is to add "/dev/block/104:3" to the alt_names of
the partition, e.g. in the constructor of Partition. Major and
Minor number should already be read in the Volume constructor.

If so - how can I add a modified libstorage to my install source (we're doing
network install)? We need to install 9 servers with this raid controller and
our plan was to use autoyast for this...

You can make a new RPM of libstorage and add it as a driver
update (dud) in linuxrc, see


Arvin Schnell, <aschnell@xxxxxxx>
Senior Software Engineer, Research & Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N├╝rnberg)
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups