Could not create partition 1 on raid device during installation

Bug #1816777 reported by Lyze
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
subiquity
Fix Released
High
Unassigned

Bug Description

There's a similar bug report from half a year ago: https://bugs.launchpad.net/subiquity/+bug/1783374

Summary: Install fails when using a raid 1 device for /
Expected behaviour: Install completes

Actual behaviour:
    Could not create partition 1 from 2048 to 976750591
    Could not change partition 1's type code to 8300
    Error encountered: not saving changes.

Steps I took, could it reproduce on the same hardware 100%:
Infos:
    Iso: ubuntu-18.04.2-live-server-amd64.iso dated 2019-02-14 10:06
    Baremetal
    Sata Ssds: 2x Crucial - MX500 500 GB 2.5" Solid State Drive
    M.2 Ssd: Corsair - MP300 120 GB M.2-2280 Solid State Drive
Setup:
    Sata Sssds in software RAID 1 during installation
        / ext4: with 100% disk size
    M.2 Ssd:
        /boot: 2GB
        efi partition
        Swap: 16GB
        /other plain ext 4: rest of disk size

Fix:
    Set the /'s size to 1GB less than full size

Working drive setup:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 95408128 1 loop /snap/core/6350
sda 8:0 0 500107862016 0 disk
└─md0 9:0 0 499972571136 0 raid1
  └─md0p1 259:5 0 498216206336 0 md /
sdb 8:16 0 500107862016 0 disk
└─md0 9:0 0 499972571136 0 raid1
  └─md0p1 259:5 0 498216206336 0 md /
nvme0n1 259:0 0 120034123776 0 disk
├─nvme0n1p1 259:1 0 536870912 0 part /boot/efi
├─nvme0n1p2 259:2 0 2147483648 0 part /boot
├─nvme0n1p3 259:3 0 17179869184 0 part [SWAP]
└─nvme0n1p4 259:4 0 100167319552 0 part /other

Disk /dev/loop0: 91 MiB, 95408128 bytes, 186344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme0n1: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E863E980-0CB8-4BA8-A0E4-837CE549C8A6

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 5244927 4194304 2G Linux filesystem
/dev/nvme0n1p3 5244928 38799359 33554432 16G Linux swap
/dev/nvme0n1p4 38799360 234438655 195639296 93.3G Linux filesystem

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/md0: 465.7 GiB, 499972571136 bytes, 976508928 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: BB769CAD-C248-49F6-A3B9-B301C5E4D1BA

Device Start End Sectors Size Type
/dev/md0p1 2048 973080575 973078528 464G Linux filesystem

Revision history for this message
Lyze (lyze237) wrote :
Changed in subiquity:
status: New → Triaged
importance: Undecided → High
Lyze (lyze237)
description: updated
description: updated
tags: added: id-5c70061118f1391529747909
Revision history for this message
Lee Azzarello (lee-rockingtiger) wrote :

This bug blocked a project I'm working with and I rewrote the procedure to use the Alternative Installer built much like D-I. This was a fine workaround but I do like subiquity so I tried to build the master branch. This failed (which is another bug) but I don't know if this is fixed in master. Is it?

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

This bug is at long last fixed in the edge channel and will be released to stable soon.

Changed in subiquity:
status: Triaged → Fix Committed
Changed in subiquity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.