[Spce-user] [EXTERNAL] mr13.5.1 Bare Metal Installation woes

[Michael Prokop]

Hi,

* Newbie [Thu Oct 30, 2025 at 11:55:05AM +0000]:
> 'Morning all,
> 
> 1. Expected Behaviour
> 
> After selecting "CE" from the menu, grml installer leaves bootable
> mr13.5.1 on the SSD after installation completes.
> 
> 
> 2. Actual Behaviour
> 
> After selecting "CE" from the menu, grml installer prints:
[...]
> Then after selecting < Yes > to alert "Do you want to check the
> install media?" it immediately alerts "Integrity check failed.
> Reason: The media check is complete the result is: NA.
> File not found.  Abort installation or continue anyway?" and
> continuing, the installer completes printing:

Hm, interesting. Couldn't reproduce this yet, my ISO checksum also
matching yours exactly. This *might* be related to the usage of
/dev/sr0 when booting via USB, I'll look into this.

[...]
> After selecting reboot, the BIOS prints:
> 
> No boot device has been detected, please press any key to reboot!

Ok, that's clearly unexpected.

What type of bare metal system are you running here exactly?
And are you using BIOS or EFI mode? (The behavior by syslinux reported
further below, indicates that you're booting in BIOS mode?)

> If the grml rescue is entered, the lvms are visible but inactive:
> 
> lvm> lvscan
>   inactive      '/dev/ngcp/root' [10.00 GiB] inherit
>   inactive      '/dev/ngcp/fallback' [10.00 GiB] inherit
>   inactive      '/dev/ngcp/data' [192.78 GiB] inherit
> lvm> lvchange -a y /dev/ngcp/root
> lvm> lvchange -a y /dev/ngcp/fallback
> lvm> lvchange -a y /dev/ngcp/data
> lvm> lvscan
>   ACTIVE        '/dev/ngcp/root' [10.00 GiB] inherit
>   ACTIVE        '/dev/ngcp/fallback' [10.00 GiB] inherit
>   ACTIVE        '/dev/ngcp/data' [192.78 GiB] inherit
> lvm>

That's good though and indicates, that the installation itself
might have worked, and we're only failing somewhere in bootloader
setup on your system.

Could you please mount /dev/ngcp/root from the resuce system, and
look into its /var/log/deployment-installer-debug.log (feel free to
provide it via personal mail to me, given it might be >1MB and might
contain sensible data you might not want to share with the public)?

> Without success in making it bootable.  Using BIOS to target 1st,
> 2nd, 3rd disks to boot from it prints on each occasion:

Chainloading from further disks via syslinux tends to fail, but:

> Failed to load COM32 file /boot/addons/chain.c32 !2
[...]
> !2: chain.c32 is not in addons but in isolinux
[...]

... this indeed is a bug on our side, thanks for reporting, we'll fix this.

regards
-mika-