[Bug 1536664] Re: Installer cannot use DASD if it was used with LVM before

[Launchpad Bug Tracker]

This bug was fixed in the package lvm2 - 2.02.133-1ubuntu5

---------------
lvm2 (2.02.133-1ubuntu5) xenial; urgency=medium

  * Drop udev rules from lvm2-udeb package. Otherwise, lvm groups and
    volumes are activated behind partman's back e.g. after dasd drive
    activation. And thus prevents dasdfmt from succeeding. LP: #1536664
  * Drop watershed-udeb dependency, no longer needed.
  * Keep dmsetup udev rules.

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Tue, 09 Feb 2016 10:14:58
+0000

** Changed in: lvm2 (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1536664

Title:
  Installer cannot use DASD if it was used with LVM before

Status in lvm2 package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Michael Roesch <ROESCH3 at de.ibm.com> - 2016-01-21 07:31:16 ==
  A DASD that has been used with and partitioned for LVM, cannot be used for installation. The installer cannot format the disk. It throws the error "An installation step failed. You can try to run the failing item again from the menu, or skip it and choose something else. The failing step is: Configure direct access storage devices (DASD)". 
  When you just select the DASD without formatting, the installer accepts the DASD, but hangs at "Scanning disks..." at 45 percent. I have attached the syslog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1536664/+subscriptions