Thanks for that. The failure is different now (which suggests my changes
have helped):
Running command ['sgdisk', '--new', '2:18432:2424585727', '--typecode=2:8300',
'/dev/mapper/mpathr'] with allowed return codes [0] (capture=True)
An error occured handling 'partition-1': ProcessExecutionError - Unexpected
error while running command.
Command: ['sgdisk', '--new', '2:18432:2424585727', '--typecode=2:8300',
'/dev/mapper/mpathr']
Exit code: 4
Reason: -
Stdout: ''
Stderr: Could not create partition 2 from 18432 to 2424585727
Could not change partition 2's type code to 8300!
Error encountered; not saving changes.
I think curtin has some bugs with multipath disks where the block size
is 4096.
The end of the attempted partition in bytes is 2424585727*4096 =
9931103137792, larger than the reported size of the disk, 9931038130176.
The first call to sgdisk was
['sgdisk', '--new', '1:256:2303', '--typecode=1:4100',
'/dev/mapper/mpathr']
So simply based on this, I would expect the start sector of the second
partition to be 2304, not 18432. Chasing code a bit, I think the
function calc_dm_partition_info
(https://git.launchpad.net/curtin/tree/curtin/commands/block_meta.py#n666)
is doing something wrong wrt sector sizes but it's too late at night for
me to really even try to see what. Back tomorrow with a fresher brain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878041
Title:
installation fails creating user on large multipath system -
multipathd show command times out in curtin log with 163 paths
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1878041/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
