IncusOS hanging and erroring on boot

[kaymin]

I’m trying to install IncusOS on an HPE ProLiant DL360 Gen10 with an Intel Xeon Gold 6254 3.10GHz CPU. I know this isn’t new hardware and doesn’t quite meet the specs but I was hoping it could still work since x86_64-v3 doesn’t seem to be strictly enforced yet.

Booting into the OS is hanging for 10-15 minutes and then gives messages like this:

(A bunch of no such file or directory messages)

timed out waiting for device dev-mapper-usr.device -/dev/mapper/usr.

timed out waiting for device dev-disk-by/x2dpartlabel-esp.device - /dev/disk/by-partlabel/esp.

timed out waiting for device dev-disk-by/2 .....................

timed out waiting for edevice dev-gpt/x2dauto/x2droot.device - /dev/gpt-auto-root

Followed by information about devices and my TPM.

• I’m installing an IncusOS 20260222 image. I’ve also tried some older ones in the past
• I’m installing from a USB and made sure to select the USB option when building the image
• I have a TPM 2.0 module installed an enabled and have tried both CRB and FIFO modes.
• I have secure boot enabled and have added IncusOS’s KEK and DB keys as instructed. I’ve also tried many other combinations of keys by removing some of the default ones and replacing the PK with the IncusOS PK and all ended with the same error if it was able to install.
• The server has smart array which could be causing problems, but I currently only one drive inserted and the port is in “mixed mode” which should mean if it’s not part of an array it should be passed through with HBU. I’ve tried installing to this and to a logical drive in a smart array and neither have made a difference.

The problem may just be with outdated hardware but I thought I should make a post and see if there’s something I can try before I scrap IncusOS on the bare metal. Thanks for all your hard work on this project!

[stgraber (Stéphane Graber)]

Can you take photos or screenshots of each of the debug screens that are shown after the 10 minutes timeout? There usually is enough information on those for us to figure out what driver may be missing.

[kaymin]

Here are some screenshots of what I’m seeing. Let me know if there’s any other helpful information I can provide.

Image used: IncusOS_202602240349.img

[stgraber (Stéphane Graber)]

Do you know exactly what storage controller is in that server?

We preload the hpsa driver, but since you’re not seeing any disks, I’m guessing your server needs something different.

[kaymin]

Here are the outputs of some commands I ran, looks like it uses megaraid_sas.

lspci |grep -i raid
12:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3324 [Intruder] (rev 01)

lsmod |grep sas
megaraid_sas          225280  18
xhci_pci_renesas       20480  1 xhci_pci

modinfo megaraid_sas
filename:       /lib/modules/6.8.0-90-generic/kernel/drivers/scsi/megaraid/megaraid_sas.ko.zst
description:    Broadcom MegaRAID SAS Driver
author:         megaraidlinux.pdl@broadcom.com
version:        07.727.03.00-rc1
license:        GPL
...
[snip]

[stgraber (Stéphane Graber)]

Hmm, that’s weird, we do have megaraid_sas included in our images already.

[kaymin]

Sorry, I made the incorrect assumption that my DL360 uses the same controller as my DL380. Looking at the 360, here is what I’m seeing with an lsmod:

It seems to be using smartpqi

[stgraber (Stéphane Graber)]

Ah, great, that makes a lot more sense!

[stgraber (Stéphane Graber)]

base: Add smartpqi to the initrd

[stgraber (Stéphane Graber)]

We’re planning another stable image build of IncusOS later today so you should have something to try tomorrow.

[kaymin]

With the new image today it I’m unfortunately not even able to install from the USB. Here is the error

[stgraber (Stéphane Graber)]

If possible, I would wipe the SmartArray volume (potentially re-create it) AND wipe the USB stick then write a clean image on it.

My guess as to the error you’re getting is that you’re booting from the USB stick but it then finds the boot partition of the installed system and tries to load files from that, failing as the installed version differs from what’s on the USB stick.

[kaymin]

That did the trick! Thanks for all your help.

One last question: Once IncusOS starts enforcing x86_64-v3, will I no longer be able to update to the new images on this hardware?

[stgraber (Stéphane Graber)]

You mention a Xeon Gold 6254, that’s a Cascade Lake part so should be plenty recent enough for x86-64-v3. It should even be recent enough for v4 as v4 starts with Skylake.

The cut off on the Intel side is basically between the old Intel Xeon v2 (Ivy Bridge) and Intel Xeon v3 generations (Haswell) where v2 doesn’t support x86-64-v3 but v3 does.