Ubuntu fails to boot after "sudo apt upgrade"

VIM3
1

Which system do you use? Android, Ubuntu, OOWOW or others?

Ubuntu 24.04

Which version of system do you use? Please provide the version of the system here:

I am using “vim3-ubuntu-24.04-gnome-linux-6.9-fenix-1.6.8-240605.img” and I wish to boot from SD card, instead of eMMC, as my memory usage is more than 32GB.

Please describe your issue below:

When I flash the image “vim3-ubuntu-24.04-gnome-linux-6.9-fenix-1.6.8-240605.img” to the SD card. It boots up and everything goes well and I am able to use the system without issues.

But if I do “sudo apt update && sudo apt upgrade”, the upgrade process also goes well.

But the system doesn’t boot. It gets stuck in KHADAS splash screen.

Post a console log of your issue below:


NOTICE:  BL31: v1.3(release):4fc40b1
NOTICE:  BL31: Built : 15:58:17, May 22 2019
NOTICE:  BL31: G12A normal boot!
NOTICE:  BL31: BL33 decompress pass
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2021.04 (Jun 05 2024 - 10:10:54 +0800) khadas-vim3

Model: Khadas VIM3
SoC:   Amlogic Meson G12B (A311D) Revision 29:b (10:2)
DRAM:  3.8 GiB
MMC:   sd@ffe03000: 0, sd@ffe05000: 1, mmc@ffe07000: 2
In:    serial
Out:   serial
Err:   serial
fusb302_init: Device ID: 0x91
Net:   eth0: ethernet@ff3f0000
Failed to load 'splash.bmp'
** Unrecognized filesystem type **
Can't set block device
1080138 bytes read in 54 ms (19.1 MiB/s)
DISPLAY: setup failsave FullHD mode
starting USB...
Bus usb@ff500000: Register 3000140 NbrPorts 3
Starting the controller
USB XHCI 1.10
scanning bus usb@ff500000 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Setting bus to 0
Hit SPACE in 2 seconds to stop autoboot
Device 0: unknown device
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
222 bytes read in 2 ms (108.4 KiB/s)
Retrieving file: /splash.bmp
Failed to load '/splash.bmp'
1:      Default
Retrieving file: /initrd.img
Failed to load '/initrd.img'
Skipping Default for failure retrieving initrd
SCRIPT FAILED: continuing...
81255 bytes read in 6 ms (12.9 MiB/s)
Card did not respond to voltage select! : -110
Scanning disk sd@ffe03000.blk...
Disk sd@ffe03000.blk not ready
Scanning disk sd@ffe05000.blk...
Scanning disk mmc@ffe07000.blk...
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
Found 9 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
switch to partitions #0, OK
mmc2(part 0) is current device
** Unrecognized filesystem type **
ethernet@ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff3f0000
missing environment variable: pxeuuid
Retrieving file: /extlinux/pxelinux.cfg/01-c8-63-14-73-c9-72
ethernet@ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff3f0000
Retrieving file: /extlinux/pxelinux.cfg/00000000
ethernet@ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff3f0000
Retrieving file: /extlinux/pxelinux.cfg/0000000
ethernet@ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
...
2

Hello @aananthcn

Thanks for your feedback, we will check this issue.

3

I am extensively using the Yocto build system for creating images. But at times this Ubuntu image is useful to quickly evaluate or test some configuration. So, please provide me updates once the fix (upgrades could be blocked by default) is ready.

4

Hello @aananthcn

This issue already fixed. But you need to reinstall the image to SD card.

After reinstall , you can execute apt upgrade without issues.

5

Hi @numbqq, thanks for the fix. Should I download a new image? Or the fix is done on the package server end? Kindly clarify.

6

Just the previous image you used.

Yes, we fixed on the server side.

7

Hi Nick, I can now confirm that Ubuntu 24.04, which was flashed with “vim3-ubuntu-24.04-gnome-linux-6.9-fenix-1.6.8-240605.img.xz” successfully updated/upgraded packages and rebooted without the original problem of filesystem corruption error message in the boot loader.

However, I notice an error message in the upgrade log (see below), which didn’t recreate the original problem of not booting.

Setting up gnome-shell-extension-ubuntu-tiling-assistant (46-1ubuntu1.1) ...
Setting up ubuntu-desktop-minimal (1.539.1) ...
Setting up ubuntu-desktop (1.539.1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.2) ...
ln: failed to create hard link '/boot/initrd.img-6.9.1+.dpkg-bak' => '/boot/init
rd.img-6.9.1+': Operation not permitted
update-initramfs: Generating /boot/initrd.img-6.9.1+
update-initramfs: Converting to u-boot format
Processing triggers for libc-bin (2.39-0ubuntu8.3) ...
8

Hello @aananthcn

It is not harmful, you can just ignore it.