Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kvdo builds just fine with kernel 6.6 but it fails to boot with vdo root device #70

Open
beertje44 opened this issue Nov 25, 2023 · 3 comments
Assignees

Comments

@beertje44
Copy link

Tried your latest version, 8.2.3.3, on ALmaLinux 9.3 with kernel 6.6.2. It seems to build just fine with dkms as did it with 6.5.
However this time it fails to boot: unknown device boot 0,0.

Was hoping I could finally test if the problems with my onboard AMD GPU were solved. But guess I'll have to wait a bit longer.

Is 6.6 supported, or is this work in progress?

@lorelei-sakai
Copy link
Member

lorelei-sakai commented Dec 1, 2023

As far as I know VDO should work with a 6.6 kernel. If you're using it as a boot device, I know some people have seen startup races where the VDO device isn't ready yet when the system tries to use it. Without more details it's hard to say if that's what you're running into.

There are a few adjustments that we expect to have to make for a 6.7 kernel but we'll look into those more when that kernel gets finalized.

@beertje44
Copy link
Author

You are right, the problem seems to be with dkms. kvdo builds just fine, but after that there is a problem during the "Adding weak modules" stage: it gives depmod file not found errors on modules I know are really there. Among those are the nvidia drivers and zfs drivers I also added though dkms. Not sure if this is something with the latest release of kvdo or a local setup issue.

For now I was able to boot 6.6 by rebuilding those through dkms which didn't produce these errors and running dracut after that.

Also I was unable to reproduce by just running "dnf --enablerepo=elrepo-kernel update" which installed 6.6.3 and which booted just fine. Guess it was a local setup issue.

@beertje44
Copy link
Author

FYI: on 6.6.5 there does seem to be a race condition, it boots but then eventually dracut is unable to find the main (vdo backed) lv. 6.6.3 boots and works just fine.

@beertje44 beertje44 reopened this Dec 9, 2023
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

No branches or pull requests

3 participants