Boot very fast on a VM or i7, but very slow and hanging on a N150

Support and Help
1

I have created a GPT disk image with 1) an UEFI partition and 2) an Ubuntu root partition.

The root partition was created from files extracted from the official Ubuntu files in ubuntu-24.04-minimal-cloudimg-amd64-root.tar.xz.

The disk boots perfectly on a VirtualBox VM and on my good old i7 Intel desktop computer, but when I deploy it on a Mini NUC N150 computer, the boot starts normally, then every step in the boot process becomes very slow, and after more than 30 minutes the boot process hangs, after the journal service has been started.

In the context of a chroot on the disk image I created (i.e. executing the commands on the “offline” Ubuntu system), I installed these additional packages with apt: linux-firmware, intel-microcode, amd64-microcode, linux-generic-hwe-24.04. I also did “add-apt-repository restricted” and “ubuntu-drivers autoinstall” to get proprietary drivers.

I doubled-checked, and the /boot folder of the root Ubuntu partition contains the Linux kernel 6.14.0, which is supposed to support the N150.

Any idea why the boot process is that slow, and what can cause it to hang?

2

Do you see any related messages if you boot the system without quiet splash boot parameters?

Does systemd-analyze blame and/or systemd-analyze critical-chain provide any insight?

1 Like
3

Have you updated UEFI firmware to latest available?

And old systems work a lot better with an SSD.
My 2006 laptop became functional, but not speedy, with an external SSD. Boot on internal HDD.

4

Hello, I removed “quiet splash” from /etc/default/grub and at boot time, I do not see additional errors that would explain why the boot process becomes so slow and halts. Thanks anyway !

5

And I can’t run the utilities you mention because the boot process hangs, I can’t get to the console. Thanks.

6

Shouldn’t be a UEFI issue because when I boot using the standard Ubuntu installer ISO it works perfectly. It is just when I boot with my own DIY-made pre-installed image that the issue arises. I’m trying to build my own DIY-made pre-installed image because Ubuntu pulled this type of image from their web site few weeks ago, and we rely on it for our deployment process.

7

This topic was automatically closed after 30 days. New replies are no longer allowed.