# Update 161 --\> 162 IPfire doesn't boot **URL:** \ **Category:** Update Trouble\ **Created:** [26 December 2021 13:34 UTC](https://community.ipfire.org/t/update-161-162-ipfire-doesnt-boot/6895 "2021-12-26T13:34:18Z")\ **Posts on this page:** 1\ **Showing post:** 17
**Author:** ![cmisch](https://community.ipfire.org/user_avatar/community.ipfire.org/cmisch/32/16502_2.png) [@cmisch](https://community.ipfire.org/u/cmisch)\ **Post date:** [13 February 2022 10:27 UTC](https://community.ipfire.org/t/update-161-162-ipfire-doesnt-boot/6895/17 "2022-02-13T10:27:29Z")
Hi, thanks for the welcome. > Um, this should have been fixed by [this commit](https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=e9084d9b4fb32373663f462bec97537ef3dd05fb) in Core Update 163. Odd to see `dracut` is missing this one… Yes this commit will put the driver to the list. But the dracut command you are using will only recreate the initrd for the currently running kernel. Which in my case was the old 5.10.76-ipfire one. So i get the message `Kernel version 5.10.76-ipfire has no module directory /lib/modules/5.10.76-ipfire` /lib/modules/5.10.76-ipfire was deleted at this point. The new initrd was missing `the modules Failed to install module xen\_blkfront Failed to install module reiserfs In case not changing the kernel everthing would be ok i assume “ **dracut --regenerate-all** ” will regenerate “all” initrd’s of all installed kernels. Or you may use the **–kver** option and specify the new Kernel Version. Ok i will try to check the core updates earlier (before release) if possible. Switched to testing… There should be not many differences from ipfire on Xen to other systems. The included xen\_blkfront (needed in initrd) and xen\_netfront might be the only ones. And even this can be avoided by using standard drivers by performance decrease. --- _[View the full topic](https://community.ipfire.org/t/update-161-162-ipfire-doesnt-boot/6895)._