Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #83158 > unrolled thread

Bug#980021: initramfs-tools: Upgrading a LVM2 system with separate /usr to buster breaks booting

Started byBen Hutchings <ben@decadent.org.uk>
First post2024-07-24 05:20 +0200
Last post2024-07-24 05:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#980021: initramfs-tools: Upgrading a LVM2 system with separate /usr to buster breaks booting Ben Hutchings <ben@decadent.org.uk> - 2024-07-24 05:20 +0200

#83158 — Bug#980021: initramfs-tools: Upgrading a LVM2 system with separate /usr to buster breaks booting

FromBen Hutchings <ben@decadent.org.uk>
Date2024-07-24 05:20 +0200
SubjectBug#980021: initramfs-tools: Upgrading a LVM2 system with separate /usr to buster breaks booting
Message-ID<J3AHL-4hck-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreino

On Tue, 12 Jan 2021 21:23:55 -0600 Ryan Underwood
<nemesis@icequake.net> wrote:
> Package: initramfs-tools
> Version: 0.139
> Severity: important
> 
> Dear Maintainer,
> 
> I understand that separate /usr is deprecated, but many users do not
> have the luxury of wiping and reinstalling their entire system. 
Rather,
> a simple dist-upgrade procedure is expected to produce a working
system,
> making a best effort to migrate previously supported configurations.
> 
> Given that, upgrading a system to buster will break booting if the
> following two conditions are true:
> * /usr is a mount for a separate block device
> * The block device containing the /usr filesystem is a LVM volume.

No, that's a well-tested scenario.  There must be something unusual
about your system configuration.
 
> The reason is because the script
> /usr/share/initramfs-tools/scripts/local-top/lvm2 only attempts to
> activate the root and resume devices, and no other devices.
[...]

That's intentional and not a bug.  We find out the root and resume
devices from the built-in defaults or kernel command line.  But we find
the /usr device from /etc/fstab, after fscking and mounting root. 
There's a separate script,
/usr/share/initramfs-tools/scripts/local-block/lvm2, that is called to
handle /usr and should activate its volume group.

How was /usr listed in /etc/fstab?

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.

[toc] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web