[Expired for initramfs-tools (Ubuntu Bionic) because there has been no
activity for 60 days.]
** Changed in: initramfs-tools (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for live-installer (Ubuntu Bionic) because there has been no
activity for 60 days.]
** Changed in: live-installer (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for live-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: live-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for base-installer (Ubuntu Bionic) because there has been no
activity for 60 days.]
** Changed in: base-installer (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I came across this old bug while doing some clearance.
Xenial reached EOSS (End of Standard Support) so I'm afraid it can't be
fixed. It is unfortunate that we were unable to resolve this defect,
however, there appears to be no further action possible at this time
because it's not a security
** Changed in: base-installer (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: initramfs-tools (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm marking this as incomplete for 18.04.2 and wont fix for xenial based
on @ahasenack's last input.
** Also affects: base-installer (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also
Thank you for taking the time to file a bug report.
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete
Thank you for taking the time to file a bug report.
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete
I'm marking this as incomplete for 18.04.2 and wont fix for xenial based
on @ahasenack's last input.
** Also affects: base-installer (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also
This bug has a lot of troubleshooting comments, but lacks a good summary
about what is going on. I don't expect the xenial installer to be
changed anymore, short of critical bugs affecting it.
@tcstone, you say you hit something similar with 18.04.2. Current bionic
release is 18.04.3, would you
This bug has a lot of troubleshooting comments, but lacks a good summary
about what is going on. I don't expect the xenial installer to be
changed anymore, short of critical bugs affecting it.
@tcstone, you say you hit something similar with 18.04.2. Current bionic
release is 18.04.3, would you
** Tags removed: server-triage-discuss ubuntu-server
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
To manage
** Tags removed: server-triage-discuss ubuntu-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
To manage notifications
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
To manage notifications about
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
To manage notifications about this bug go
nicely researched and documented bug. Why not fixed three years later? I
hit this (or seeminly this same bug) doing an install of server 18.04.2
yesterday. I needed to enable ssh for remote install and lowered debconf
priority. This gave me some good clues I'll now try some work-arounds.
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: live-installer (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/1582899
** Tags added: ubuntu-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
To manage notifications about this bug go to:
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Changed in: base-installer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582899
** Description changed:
Sysadmin reported in #ubuntu (later #ubuntu-kernel) the 16.04 ubuntu-
- server failed due to being unable to configure linux-
+ server ISO installer failed due to being unable to configure linux-
image-4.4.0-21-generic.
Lots of diagnostics and one SSH remote
** Description changed:
Sysadmin reported in #ubuntu (later #ubuntu-kernel) the 16.04 ubuntu-
server failed due to being unable to configure linux-
image-4.4.0-21-generic.
Lots of diagnostics and one SSH remote session later we seem to have
narrowed it down to the installer.
- The
After ensuring the "normal" option (not "live") was selecting in the
"Install the System" step I checked which processes were running when it
paused to ask which kernel should be installed.
This confirms the live-installer.postinst script is running:
$ grep -Ev '\]$' ~/installer-ps.log
PID
After noticing /var/lib/dpkg/info/live-installer.postinst and seeing it
has the crucial step commented out I think the source of the issue is
now identified.
live-installer debian/live-installer.postinst:
waypoint 1 check_target
waypoint 1 get_mirror_info
waypoint 100install_live_system
** Also affects: live-installer (Ubuntu)
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/1582899
Title:
in-target: mkinitramfs: failed to determine device
In expert mode the kernel command-line carries "priority=low" which is a
debconf configuration parameter. It suggests that it affects the order
of functions called such that "setup_dev" isn't being called before
"install_kernel", which would make sense because in tests after a manual
I mis-read the code in the previous comment; the condition is fine. To
figure it out I added some lines that do each test independently so as
to identify which of the three fails. That reveals the problem is the
block-device test:
Examining /etc/kernel/postinst.d.
run-parts: executing
I added "set -x" to the start of /usr/share/initramfs-tools/hook-
functions::dep_add_modules_mount() and after it failed I grabbed the
output from /var/log/apt/term.log:
The link /initrd.img is a dangling linkto /boot/initrd.img-4.4.0-21-generic
vmlinuz(/boot/vmlinuz-4.4.0-21-generic
) points to
This is triggered by the debconf setting in base-installer's
library.sh:install_kernel_linux():
Where it writes out the alternate module policy for initramfs-tools:
root@tmpstorage:/# cat /etc/initramfs-tools/conf.d/driver-policy
+ cat /etc/initramfs-tools/conf.d/driver-policy
# Driver
I've now successfully reproduced the issue in the virtual machine.
Firstly, at the installer boot menu, choose Expert Mode.
This allows selection of each installer step from a menu and causes
debconf to ask many more questions.
At "Install the System" choose a "normal" installation and then for
Using a virtual machine I'm able to reproduce the differing UUIDs but
not able to reproduce the failure of the initrd generation.
The code that fires the error is /usr/share/initramfs-tools/hook-
functions::dep_add_modules_mount()
--
You received this bug notification because you are a member
** Attachment added: "apt term.log"
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+attachment/4664936/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582899
** Attachment added: "partman log"
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+attachment/4664935/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582899
** Attachment added: "syslog from installer"
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+attachment/4664934/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
34 matches
Mail list logo
