Skip to content

Conversation

@schaefi
Copy link
Collaborator

@schaefi schaefi commented Jul 24, 2025

If we return from the repart stage it's important to wait for the root device to appear. This is because the device setup from udev might still be held back due to a former lock on the device. This means if we return fast after locking for example when check_repart_possible() quickly finds out that it's not possible, then udev has not yet got the time to create the device nodes.
This Fixes #2863

If we return from the repart stage it's important to wait
for the root device to appear. This is because the device
setup from udev might still be held back due to a former
lock on the device. This means if we return fast after
locking for example when check_repart_possible() quickly
finds out that it's not possible, then udev has not yet
got the time to create the device nodes.
This Fixes #2863
@schaefi schaefi requested a review from Conan-Kudo July 24, 2025 17:30
@schaefi schaefi self-assigned this Jul 24, 2025
@Conan-Kudo Conan-Kudo merged commit 5dd32d1 into main Jul 24, 2025
13 checks passed
@Conan-Kudo Conan-Kudo deleted the fix_return_from_dracut branch July 24, 2025 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Raw images built with 10.2.28 fails to boot properly due to a repart issue

3 participants