@ roesch3 it's best to open new (more) bugs to track subtle things separately. And fix them, close them as duplicate, remove duplicate flags etc.
Most likely you have to deactive the volume groups before attempting to re-dasdformat the drive. And that's a slightly separate issue. The root cause that I can see, is that dasdformat step does not "force" the formatting (-F) flag which would, well force the formatting, hopefully. =) Please open a new bug report with this newly reported issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 <roes...@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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
