[UBUNTU 20.04] Unsupported setup: Directory '/boot' is located on a multi-target device-mapper device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
New
|
High
|
Skipper Bug Screeners | ||
s390-tools (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
---Problem Description---
System Update did not work on Ubuntu 20.04.6 LTS. After apt update and apt full-upgrade came the following error message:
...
Calling hook copymods
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
Building cpio /boot/initrd.
Using config file '/etc/zipl.conf'
Run /lib/s390-
Error: Unsupported setup: Directory '/boot' is located on a multi-target device-mapper device
Error: Script could not determine target parameters
run-parts: /etc/initramfs/
But the error message is not true. Update used to work before. It is a KVM guest. The disk is a qcow2 file not multipath. There is no separate /boot partition. It is an ext4 file system.
Filesystems:
root@lnxproxy:/# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/
/dev/mapper/
udev 888M 0 888M 0% /dev
tmpfs 900M 12K 900M 1% /dev/shm
tmpfs 900M 0 900M 0% /sys/fs/cgroup
Contact Information = <email address hidden>
---uname output---
Linux lnxproxy 5.4.0-150-generic #167-Ubuntu SMP Mon May 15 17:35:14 UTC 2023 s390x s390x s390x GNU/Linux
Machine Type = zKVM guest
---System Hang---
The system was not booting any more. I attached the disk to an other system.
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Run the command update-initramfs -uv.
*Additional Instructions for <email address hidden>:
-Post a private note with access information to the machine that the bug is occuring on.
tags: | added: architecture-s39064 bugnameltc-202774 severity-medium targetmilestone-inin--- |
Changed in ubuntu: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
affects: | linux (Ubuntu) → subiquity (Ubuntu) |
Changed in subiquity (Ubuntu): | |
assignee: | Skipper Bug Screeners (skipper-screen-team) → nobody |
Changed in ubuntu-z-systems: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
tags: | added: installer |
tags: | added: rls-ff-incoming |
Changed in ubuntu-z-systems: | |
importance: | Undecided → High |
tags: |
added: foundations-todo removed: rls-ff-incoming |
Changed in ubuntu-z-systems: | |
status: | New → Incomplete |
Changed in ubuntu-z-systems: | |
status: | Incomplete → New |
Changed in s390-tools (Ubuntu): | |
status: | Incomplete → New |
tags: |
added: installation removed: installer |
I think the warning comes because / is on an LVM logical volume, and there is no separate /boot partition. I would have expected there to be a separate /boot partition in such a case or does zipl have native lvm support?