This bug was fixed in the package livecd-rootfs - 25.04.20
---
livecd-rootfs (25.04.20) plucky; urgency=medium
[ Adriano Cordova ]
* riscv: add SUBARCH 'jh7110'. (LP: #203)
[ Michael Hudson-Doyle ]
* In ubuntu-server builds, install the first kernel in the base layer, not
** Merge proposal linked:
https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+merge/481992
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100148
Title:
Installation fails for
It turns out that (I'm fairly sure) this is an issue with how the ISO is
constructed -- the kernel package is not being installed in the correct
layer for any ISO which does not contain the generic kernel.
** Changed in: subiquity
Status: New => Invalid
** Changed in: multipath-tools (Ubun
FWIW the obvious thing to cause this would be a difference in the kernel
config for the generic and generic-64k kernel. Here's the diff between
the configs (as extracted from the debs):
https://paste.ubuntu.com/p/PsKk9DYV4S/ -- this is a lot more than I was
expecting but there's no obvious (to me)
> Here's the full journal from the target system (although I fear this
is included in the install logs, too).
No, sadly there is stuff that only ends up in the journal and this needs
to be collected separately. The apport flow does capture it but people
manually taring /var/log/installer need the
Here's a few lines from the journal (from early startup, well before
subiquity is doing anything):
Feb 25 15:45:30 ubuntu-server systemd[1]: Starting
modprobe@dm_multipath.service - Load Kernel Module dm_multipath...
Feb 25 15:45:30 ubuntu-server systemd[1]: modprobe@dm_multipath.service:
Deacti
** Also affects: subiquity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100148
Title:
Installation fails for pending plucky arm64+largemem iso
To manag
Here's the full journal from the target system (although I fear this is
included in the install logs, too).
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2100148/+attachment/5860624/+files/journal
--
You received this bug notification because you are
No it looks like it does. So I don't know what is going on here. Would
it be possible to get the journal / syslog / dmesg type output as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100148
Tit
The error seems to be this
Detected multipath support, reload maps
Running command ['multipath', '-r'] with allowed return codes [0]
(capture=False)
161.606954 | DM multipath kernel driver not loaded
finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta/cl
** Attachment added: "install_logs.tar"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2100148/+attachment/5860610/+files/install_logs.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/21
11 matches
Mail list logo
