Core 2.21 Update 127 -> 128 Failed

Post Reply
gh4wi
Posts: 15
Joined: March 29th, 2018, 3:20 pm

Core 2.21 Update 127 -> 128 Failed

Post by gh4wi » March 19th, 2019, 7:57 pm

Used Pakfire to Update from Core 2.21 127 to 128.
Pakfire said it completed ok.
Used WUI to reboot IPFire PC.
Upon rebooting, the IPFire PC displayed full screen wallpaper with the Big Penguin and
the "grub>" prompt. It should have booted Linux & the Firewall.
Did not know what to do with same ?
The CD does not contain a fix tool for fixing booting problems, please consider adding one.
Also is there a console command to display the IPFire Version & update level ?

rodneyp
Posts: 149
Joined: October 4th, 2010, 2:17 am
Location: Australia

Re: Core 2.21 Update 127 -> 128 Failed

Post by rodneyp » March 19th, 2019, 9:44 pm

The "grub>" prompt is an indication that grub is installed (and probably working) but a configuration file was not found.

Type the following sequence of commands, for non-EFI installations:

grub> set root='hd0,msdos1'
grub> linux /vmlinuz-4.14.103-ipfire root=/dev/sda3
grub> initrd /initramfs-4.14.103-ipfire.img

Then either type the additional command "boot" or press F10

It's possible to later create soft links "vmlinuz" and "initramfs", so that you don't have to recall the exact kernel version.

rodneyp
Posts: 149
Joined: October 4th, 2010, 2:17 am
Location: Australia

Re: Core 2.21 Update 127 -> 128 Failed

Post by rodneyp » March 20th, 2019, 9:01 pm

I've upgraded my Banana Pi and i586-PAE from core 127 to 128 without problem.
Have now upgraded my KVM virtual machine of x86_64 from core 125 to core 128, again without problem. This is not a working system - simply a way of testing that the cores & upgrades work.

A few others have reported similar failure with grub following upgrade from core 127 to 128. Are you using x86_64 ? and does the file /boot/grub/grub.cfg exist ?

User avatar
Roberto Peña
Posts: 761
Joined: July 16th, 2014, 3:56 pm
Location: Bilbao (España)
Contact:

Re: Core 2.21 Update 127 -> 128 Failed

Post by Roberto Peña » March 31st, 2019, 7:15 pm

Will it be solved with this?.

viewtopic.php?f=22&t=22490

If someone has tried and solved it, tell them.

Regads.
Image
Image

╔════════════════════════════════════════════════╗
Donate to improve IPFire: https://www.ipfire.org/donate
╚════════════════════════════════════════════════╝

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8518
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: Core 2.21 Update 127 -> 128 Failed

Post by Arne.F » April 1st, 2019, 5:56 am

The removed update-bootloader is no issue and not the reason for the problem. I think the updater is crashed or boot runs out of diskspace.

And rerun the grub-mkconfig is not easy if the conf is already missing.
Symlinks symlinks where possible on some systems but grub-mkconfig ignores it on on systems with fat bootpartition (arm) they are not allowed.
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

Post Reply