I don't know why I never caught this before:
2020-02-22 - 18:56:39 [6]: Running "env" ("/sbin/udevadm", "settle")
2020-02-22 - 18:56:39 [6]: Finished. Exit code: 127
2020-02-22 - 18:56:39 [6]: Target cmd: ("/sbin/udevadm", "settle")
2020-02-22 - 18:56:39 [6]: Target output:
/usr/bin/env: ‘/sbin/udevadm’: No such file or directory
2020-02-22 - 18:56:39 [2]: WARNING: Could not settle disks.
That was the activity mentioned in the upstream bug that they suspected
would fix the issue. I believe they even added a second run of it in
hopes if making it better.
And here it is not running at all because it's calling a full path
that's the wrong one. But /usr/bin/udevadm is the right one.
Creating a symlink fixes the issue: `sudo ln -s /usr/bin/udevadm
/sbin/udevadm`.
Though the original upstream bug
(https://github.com/calamares/calamares/issues/1170) is still relevant,
it really came to no clear conclusion because we weren't looking in the
wrong place.
There's a new bug to fix this and several other issues which I have now
linked instead.
** Bug watch added: Calamares Issues #1324
https://github.com/calamares/calamares/issues/1324
** Changed in: calamares
Remote watch: Calamares Issues #1170 => Calamares Issues #1324
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851188
Title:
Failed to create a partition table - install failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1851188/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
