I'll ask Heinz-Werner to attach the logs and the screenshots from that
mail conversation.

So you are using a DASD ECKD - since it has about 50 GB I assume it's
probably a 3390 Model54 - I'll try to find a spare one for test and re-
creation.

The storage configuration screen should look like this:
================================================================================
  Storage configuration                                               [ Help ]
================================================================================
  To continue you need to: Mount a filesystem at /

  AVAILABLE DEVICES
^

    DEVICE                                         TY┌─────────────────────────┐
  [ LX0200                                         lo│< (close)                │
    partition 1  existing, already formatted as ext2,│  Info                  >│
                 mounted                             │  Reformat              >│
    partition 2  existing, unused                    │  Add VTOC Partition    >│
                                                     │  Format                >│
  [ Create software RAID (md) > ]                    │  Remove from RAID/LVM   │
  [ Create volume group (LVM) > ]                    └─────────────────────────┘
                                                                             │
                                                                             │
  USED DEVICES
                                                                             v

                                 [ Done       ]
                                 [ Reset      ]
                                 [ Back       ]

Based on the selected DASD (ECKD), specified by it's device name (here
LX0200), the installer provides options to 'Add VTOC' (wipe out disk,
too) and to (re-)format.

The suggestion about 1GB for /boot and a 4GB for root is indeed too limited, 
and this got already 
addressed here: https://bugs.launchpad.net/subiquity/+bug/1785321 and further 
more fixed here: https://github.com/CanonicalLtd/subiquity/pull/737
This happened a while ago and the modification got already rolled out with 
subiquity 20.05.1 
(https://github.com/CanonicalLtd/subiquity/releases/tag/20.05.1).
Hence with current installations (of course in non-air-gapped environments) the 
subiquity installer looks for updates at the beginning and in case there is 
one, it let's you know and offers to update itself.
The update screen comes with a message like "Version 20.05.1 of the installer 
is now available (20.04.3 is currently running)."
Doing so and accepting to update, you shouldn't run into that issue with the 
small LVs anymore.


** Changed in: ubuntu-z-systems
       Status: New => Triaged

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

Title:
  [Ubuntu 20.04] - Install - problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1878596/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to