I have a similar message trying to install 20.04.1:
An error occured handling 'partions-sda5': RuntimeError - Verifying
/dev/sda5 partition flag, expecting swap, found None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for the delay in trying this out, I seem to have gotten
unsubscribed from the bug report so I didn't get an email saying there
was a new comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I followed the instructions to get the new installer from edge. When I
try to edit an existing LVM volume to make it root for the install the
installer crashes as soon as I hit return on "Edit". There are some
lines of backtrace, but they disappear before I can see them. I did
upload a bug report,
** Changed in: subiquity
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878890
Title:
[Ubuntu Server 20.04 LTS]: Failed Install
It is now (as of a few minutes) in the snap currently in edge, so you
should be able to test following the instructions in
https://discourse.ubuntu.com/t/how-to-test-the-latest-version-of-
subiquity/12428
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Are there any plans to incorporate the fix to curtin? It was released 27
May 2020 but the status of this bug doesn't seem to have changed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878890
Title:
> @Ryan,
>
> Since the installer refuses to install, there are no crash logs that I can
> provide you with. If you try to install 20.04 onto a disk with the mentioned
> layout (the "Custom layout" option), you should find that you are unable to
> choose sda1 and sda3 as destinations for /boot and
@Ryan
I booted the server into the 20.04 installer and copied off the /var/log
directory.
/var/log/installer/subiquity-debug.log.3179 ends with:
2020-06-02 21:22:21,793 INFO root:39 start: subiquity/Filesystem: starting UI
2020-06-02 21:22:21,793 DEBUG root:39 start:
@Ryan,
Since the installer refuses to install, there are no crash logs that I
can provide you with. If you try to install 20.04 onto a disk with the
mentioned layout (the "Custom layout" option), you should find that you
are unable to choose sda1 and sda3 as destinations for /boot and /.
Don't
@Kai
Can you provide the installer crash or logs?
"refuses to use /dev/sda1 as boot partition and /dev/sda3 as root
partition"
I wonder if recent changes in subiquity around ESPs may have something to do
with this.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@raharper I'd like to have this bug reopened, as it is still not fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878890
Title:
[Ubuntu Server 20.04 LTS]: Failed Install
Still not fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878890
Title:
[Ubuntu Server 20.04 LTS]: Failed Install
(subiquity...install_fail/add_info) during partitioning
To manage
With Ubuntu 20.05.2, the curtin/subiquity installer continues to fail to
install onto existing partitions.
With the following partition table, subiquity/curtin refuses to use
/dev/sda1 as boot partition and /dev/sda3 as root partition - something
it previously accepted as choices (but it failed
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/384776
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/384777
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/384778
This bug was fixed in the package curtin - 20.1-0ubuntu1
---
curtin (20.1-0ubuntu1) groovy; urgency=medium
* New upstream release.
- Release 20.1 (LP: #1880741)
- Handle multiple separators which were found in TestAllindata vmtest
- verify_ptable_flag: dos primary
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/384582
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878890
Title:
[Ubuntu Server 20.04 LTS]: Failed
@Michael
I'll sync with mwhudson, subiquity will need to pull in the fix and
release an update to edge, once that's done you can select the Update
Installer option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for fixing this @raharper!
How can I make use of this so I can finally successfully run the installation?
Do I just need to select the "Update Installer" option again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is fixed with commit cb60d8a7 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=cb60d8a7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: curtin (Ubuntu)
Status: Confirmed => In Progress
** Changed in: curtin (Ubuntu)
Assignee: (unassigned) => Ryan Harper (raharper)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/384133
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878890
Title:
[Ubuntu Server 20.04 LTS]: Failed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878890
Title:
>From the crash:
Verifying /dev/sda2 exists
Running command ['sfdisk', '--json', '/dev/sda'] with allowed return codes [0]
(capture=True)
Verifying /dev/sda2 size, expecting 86564143104 bytes, found 86564143104 bytes
Device /dev/sda2 ptable
23 matches
Mail list logo
