[Bug 1550456] Re: Formatting of DASD disks always stops at 9% during installation

[Dimitri John Ledkov]

s390-dasd (0.0.35ubuntu1) xenial; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Bump s390-dasd menu item, to be before disk-detect.

s390-dasd (0.0.35) unstable; urgency=low

  * Team upload

  [ Hendrik Brueckner ]
  * dasdfmt: detect format status and improve handling (Closes: #815918)
    - report user error if disk is in use
    - detect and properly handle already formatted DASDs
    - correct and improve <Go back> handling
  * Detect if a DASD is already configured. (Closes: #815912)

  [ Updated translations ]
  * French (fr.po) by Christian Perrier
  * Japanese (ja.po) by Kenshi Muto
  * Portuguese (Brazil) (pt_BR.po) by Adriano Rafael Gomes
  * Portuguese (pt.po) by Miguel Figueiredo

s390-dasd (0.0.34) unstable; urgency=medium

  [ Colin Watson ]
  * Use HTTPS for Vcs-* URLs, and link to cgit rather than gitweb.

  [ Hendrik Brueckner ]
  * dasd-config: always list available DASDs for selection and configuration
    (Closes: #666399)

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Mon, 07 Mar 2016 12:13:59
+0000

** Changed in: s390-dasd (Ubuntu)
       Status: New => Fix Released

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

Title:
  Formatting of DASD disks always stops at 9% during installation

Status in s390-dasd package in Ubuntu:
  Fix Released
Status in s390-dasd package in Debian:
  Fix Released

Bug description:
  == Comment: #0 - Ekaterina Teplova - 2016-02-23 11:53:50 ==
  Formatting of DASD disks always stops at 9% during installation

  Please see attachment

  == Comment: #3 - Hendrik Brueckner - 2016-02-24 03:31:44 ==
  The problem fix description is as follows:

      dasd-config: always list available DASDs for selection and configuration
      
      Previously, the DASD configuration module prompted the user to specify
      DASDs if there were more than 20 DASDs available.  If this dialog is
      shown, the user can configure DASD devices; but can only return to the
      installer through the <Go Back> button.  The <Go Back> triggers a special
      debconf return code and the "hardware-detection" dependency for this is
      not satisfied.  Later the partitioner will complain and the intermediate
      configuration file might not be copied to the target system.
      
      The second disadvantage with prompt is that the user does not see which
      DASDs are already online and configured.  See also Debian bug 666399 for
      more details.
      
      This commit removes the prompt to manually type DASDs.  The panel to
      select particular DASDs is displayed instead.
      
      Of course, there can be the case where LPARs have access to (almost)
      every device.  For this case, the solution is to use the "cio_ignore"
      kernel parameter.  With this kernel parameter you can control the
      devices that are visible to the Linux instance.
      
      For example,
      
              cio_ignore=all,!ipldev,!condev,!0.0.da00-0.0.da10
      
      ignores all devices except the console device, the IPL device, and the
      range of devices from 0.0.da00 to 0.0.da10 that might be DASDs or any
      other devices.  Note that you can change the cio_ignore settings at
      runtime, so you can later make additional devices visible.
      
      With this solution, there is no hardcoded limit necessary and the user
      can still see the list of DASDs to be configured.
      
      Signed-off-by: Hendrik Brueckner <brueckner at linux.vnet.ibm.com>

  == Comment: #10 - Hendrik Brueckner - 2016-02-26 07:44:27 ==
  For problem tracking and resolution, see Debian bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666399

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s390-dasd/+bug/1550456/+subscriptions