Repository navigation
Conversation
Contributor
Author
kvnloo
force-pushed
the
fix/root-btrfs-extra-luks-warn
branch
from
September 21, 2026 09:33
69c4725 to
eb25ef4
Compare
1 of 4 tasks
Contributor
Author
|
Salvaged into the fresh re-cut wave: #12932 ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Warn when root Btrfs spans extra LUKS devices the initramfs cannot unlock.
Fixes #10029.
Stock encrypt opens one
cryptdevice=. Adding a second LUKS-backed Btrfs member makes the filesystem unmountable immediately; the next boot only reveals it. Surface that fromupdate-analyze-logswithout blocking the update or changing the hook stack.Testing
root-btrfs-extra-luks-test.shFAIL on pinned quattro (missing helper) / PASS on this SHA (11 ok)