Yes
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 ![]()
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?
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 .. . .
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.
What’s strange then is I’ve already gone through an LTS update. I did
sudo dracut-rebuildfrom within the LTS Fallback6.12.27-1. This seemed to correct the issue. It has since updated to6.12.28-1and I still have no issue booting into LTS.
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.
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.
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.
It was indeed related to the LTS kernel.
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:
There is currently a known issue with dracut 107 and the LTS kernel. When booting the system and selecting the LTS kernel, you will recieve the error “failed to mount /sysroot”. You can avoid this issue by booting the fallback initrd or a different kernel. It only manifests in the following conditions: You have both the LTS kernel and one of the other kernels installed You use both kernels You use a filesystem that is modular in linux-lts but not modular in linux such as ext4 It is worth n…
Pudge
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