2020-03-20 11:31:20 |
Frank Heimes |
description |
While doing a subiquity installation on s390x using DASD disk storage that was used before and was therefore already partitioned, I wanted to change the partition layout during install time.
But in the 'Storage configuration' task I was not able to delete an existing partition:
┌───────────────── Cannot delete partition of local disk ────────────────┐
│ │
│ Cannot delete a single partition from a device that already has │
│ partitions. │
│ │
│ [ Close ] │
│ │
└────────────────────────────────────────────────────────────────────────┘
It should always be possible to delete an existing disk or to white out (low-level format in case of a DASD) the entire disk.
Otherwise existing and already used disks cannot be used with a different disk layout (without manual intervention).
subiquity 20.03.1 was in use.
Btw. I updated to 20.03.2, but subiquity didn't automatically restarted, and since I forgot to do it manually I stayed on 20.03.1.
Not sure if this issue is the same for all disks, or limited to s390x DASD disks. |
While doing a subiquity installation on s390x using DASD disk storage that was used before and was therefore already partitioned, I wanted to change the partition layout during install time.
But in the 'Storage configuration' task I was not able to delete an existing partition:
┌───────────────── Cannot delete partition of local disk ────────────────┐
│ │
│ Cannot delete a single partition from a device that already has │
│ partitions. │
│ │
│ [ Close ] │
│ │
└────────────────────────────────────────────────────────────────────────┘
It should always be possible to delete an existing partition or to white out (low-level format in case of a DASD) the entire disk.
Otherwise existing and already used disks cannot be used with a different partition scheme anymore (without manual intervention).
subiquity 20.03.1 was in use.
Btw. I updated to 20.03.2, but subiquity didn't automatically restarted, and since I forgot to restart it manually I stayed on 20.03.1.
Not sure if this issue is the same for all disks, or limited to s390x DASD disks. |
|