build_library: set raid0 default layout to alternate in grub.cfg for Alpha 2345 #39
Conversation
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
Set the new kernel module parameter for raid0 `default_layout=2` in `grub.cfg`, to make kernel >= 5.4 (and stable kernels) properly load `raid0.ko`. Without the change, raid0 arrays cannot be created at all. The issue started to appear since torvalds/linux@c84a137, which is meant to fix a kernel bug that may cause data corruption. The value for `default_layout` can be 1 (original) or 2 (alternate). 1 is the orignal layout kernel < 3.14, while 2 is the new layout kernel 3.14. Since kernel 3.14 is already 5 years old, we can probably assume that we do not have to care about migration from raid0 devices that were created by Kernel < 3.14. So simply set it to 2.
Member
Author
|
Since flatcar/baselayout#2 was merged, this PR is not needed any more. |
pothos
added a commit
that referenced
this pull request
Sep 26, 2022
ci-automation: Don't skip nightly build when the previous one failed
pothos
added a commit
that referenced
this pull request
Sep 26, 2022
ci-automation: Don't skip nightly build when the previous one failed
pothos
added a commit
that referenced
this pull request
Sep 26, 2022
ci-automation: Don't skip nightly build when the previous one failed
pothos
added a commit
that referenced
this pull request
Sep 26, 2022
ci-automation: Don't skip nightly build when the previous one failed
pothos
added a commit
that referenced
this pull request
Sep 26, 2022
ci-automation: Don't skip nightly build when the previous one failed
t-lo
pushed a commit
that referenced
this pull request
Apr 13, 2023
coreos-base/coreos-init: Exclude K8s' special interfaces
t-lo
pushed a commit
that referenced
this pull request
Apr 13, 2023
Move mantle's dnsmasq dependency to the SDK dependencies
pothos
added a commit
that referenced
this pull request
Jun 20, 2023
coreos-base/coreos-cloudinit: Don't use configdrive on DigitalOcean
pothos
added a commit
that referenced
this pull request
Oct 29, 2025
minimal-initrd: Use kmod's modprobe also for simple module loading
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.
Set the new kernel module parameter for raid0
default_layout=2ingrub.cfg, to make kernel >= 5.4 (and stable kernels) properly loadraid0.ko. Without the change, raid0 arrays cannot be created at all.The issue started to appear since torvalds/linux@c84a137, which is meant to fix a kernel bug that may cause data corruption.
The value for
default_layoutcan be 1 (original) or 2 (alternate). 1 is the orignal layout kernel < 3.14, while 2 is the new layout kernel 3.14. Since kernel 3.14 is already 5 years old, we can probably assume that we do not have to care about migration from raid0 devices that were created by Kernel < 3.14. So simply set it to 2.