Hello all,
I’m writing this with my phone and 4g, so appologize for mistakes or typos…
I just upgrade from 180 to 181, and asked a reboot. But it hangs on a :
setfont: ERROR setfont.c:417 kfont_load_font: Unable to find file: eurlatgr dracut Warning: Could not boot.
Hello all,
As I didn’t quickly find any solution, I decide to reinstall 180 and avoid 181 for now.
Having other hardware available, I leaved the crashed host for autopsy. So, I did :
boot crashed FW with a live distro and grab /var/ipfire and /var/log from fourth partition (I don’t have any happy experiences with IPFire’s backups, while I still do some. I also have own backups, but the firewall is so central that nothing was working any more in my LAN ! Quickest and easiest for me was a live CD-USB) ;
ssh’ed freshly installed FW, save /var/ipfire as /var/ipfire.180 (same for logs), then copy grabbed /var/ipfire and logs too (you need to https//FW.IP:444 and allow ssh first) ;
https//FW.IP:444, first visit network configs, and “validate” (press “save” or toggle a button twice…) to generate corresponding /etc configuration files. I also had to deal with MAC addresses for red interface and a few things… ;
reboot, reboot, reboot, test, and relax ;
think at a disaster solution for my customers (hopefully, it was my own FW !).
By the way, I searched for eurlatgr file inside the new FW, and didn’t find it (I don’t have all addons installed yet, and I’m on a 180) yet. But find some traces on git 181…
First thoughts : I was stupid launching upgrade late in an afternoon. I was stupid not having any disaster recovery solution.
Many thanks to the developers for providing ipfire.
The same problem here: After upgrading to 181 the system hangs at reboot.
Boot hangs – first trial
After upgrading from 180 to 181 without reboot, the firewall remained funtional.
After a scheduled shutdown the firewall could not boot.
Boot hangs – second trial
I inserted a storage card with an ipfire-backup into the same APU2C4. The Symptoms again:
After upgrading from 173 to 181 without reboot, the firewall remained functional.
After a scheduled shutdown the firewall could not boot.
In both trials the error messages were identical. The following is an excerpt from those messages:
Run /init as init process
dracut: IPFire-2
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
udevd[337]: starting version 208
random: crng init done
setfont: ERROR setfont.c:417 kfont_load_font: Unable to find file: eurlatgr
dracut Warning: Could not boot.
dracut Warning: Could not boot.
dracut Warning: /dev/disk/by-uuid/<disk-uuid root-partition> does not exist
dracut Warning: /dev/disk/by-uuid/<disk-uuid root-partition> does not exist
. . .
Dropping to debug shell.
Adding rd.debug to the kernel command line produces a repetitive rdsosreport.txt file with several hundreds pages.
From my point of view, the following facts may be relevant:
During boot process, the contents of the boot-partition can be read.
dracut complains about a non-existing root partition.
However, the partition can be mounted without problems on my desktop computer.
The setfont error message emerges at first but may not point to the root cause.
My Hardware: APU2C4. I am using ipfire in a router cascade for several years. As a result of this error, I am working without ipfire now, but would like to use it again as soon as possible.
Does anyone have an idea or even a solution?
I would greatly appreciate your help.
The missing font file should not prevent the system from boot. (on an APU sentfont fails in every case because there is not video card set could set a font.)
the question is why it cannot find the root partition (looks like a missing kernel module in the ramdisk). Is there a problem with disc space or a file system error? Can you check the upgrade logs in /opt/pakfire/log/upgrade…
The bootpartition is too small. kernel+initrd more than 60MiB and grub is also not small.
This must be a very old installation we have changed the size 2018 to 128MB and later to 256MB because the kernel grow and grow…
@ Arne F.
Thank you for your reply. Indeed, this is an installation from 2017.
I can resize the boot partition to 256 MB, or even to 512 MB. But would resizing alone solve the problem?
Presumably some files are missing now on the boot partition. What steps would you recommend to make the system functional again? I would like to avoid a complete re-installation.
You have right. I have overlooked that message because there was always a setfont message at my tests.
You can resize it and after this copy the kernel initrd and the modules from /lib/modules/ from an other installation. (Modules and kernelimage must from the same built because they are signed)
I would copy the flashimage to an usb-stick and use this kernel/modules as source.
There was a typo in my post that i have changed.
I would xzcat the flashimage to an usb stick (whick result in a install without swap partition) but you can also use the iso to install it on a spare disk.
But you know that 60 (128) MB is definitely too small for a new version and you can then cancel the update process. This doesn’t help in all cases, but it’s better than nothing.