LTS Kernel - failed to mount /sysroot

Yes

1 Like

sudo dracut-rebuild also fixed it for me.

For future updates, do we have to create the .ko file and include ext4, or will that be fixed somewhere upstream?

seems the culprit is a change in dracut upstream, in relation to the different configs of the kernels.. in the end this needs to get a fix on the source for the moment you could add add_drivers+=" ext4 " to the dracut config in case your rootfs is ext4 and it would force to include the modules..

I already mentioned this fix earlier as a response to @ckid .

Thought another way it could be addressed was with the .ko file.

Thanks for your help @joekamprad :heart:

All I did was log into LTS Fallback and do sudo dracut-rebuild. I’m not seeing any issues at all anymore. I can log into LTS without problems. So, I’m assuming I don’t need to edit or add anything to the Dracut config?

1 Like

The question is, what happens should you decide to update your LTS kernel in case of a new version.

I would suppose, that for future updates it might make sense to add_drivers+=" ext4 ". Until it is fixed upstream.

I think it is better to downgrade dracut instead:

true as if adding add_drivers+=" ext4 " we will may forget about added it and would wonder one day about it may causing another issue .. . .

1 Like

What’s strange then is I’ve already gone through an LTS update. I did sudo dracut-rebuild from within the LTS Fallback 6.12.27-1. This seemed to correct the issue. It has since updated to 6.12.28-1 and I still have no issue booting into LTS.

Agreed.

If you do the upgrade from the LTS kernel it should work fine.

The issue will only manifest if you rebuild the initrd while booted on the other kernel.

3 Likes

Very confusing … many different moving things are involved in the one thing.
It took a while until I understood it. But you can rely on the Endavournauts, your answers here have helped a lot.

2 Likes

TEAMWORK :enos_flag:

3 Likes

Thanks a bunch for having made this thread, I just now resolved the failed /sysroot mounting on my laptop.
It was indeed related to the LTS kernel. I was using the LTS kernel because it was supposed to provide more stability but today it just gave me a headache instead.
Simply switching to the mainline kernel restored my laptop.

1 Like

Actually the problem was with dracut-107-1 and it has a bug report.
In the mean time, it is recommended to downgrade to dracut-106-1.
There was nothing wrong with the LTS kernel.

EDIT:
More information on this problem can be found here:

Pudge

1 Like

Danke für Hilfe ! sudo dracut-rebuild
damit funktioniert es mit dem LTS Kernel bei mir wieder.
Danke !

3 posts were split to a new topic: Failed to mount /sysroot during boot