calamares install (grub-install?) issue - jammy

Bug #2045410 reported by Chris Guiver
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calamares (Ubuntu)
Opinion
Undecided
Unassigned

Bug Description

Install of jammy (daily) on
- hp prodesk 600 g3 sff (i5-7500, 8gb, nvidia geforce gt710 (gk208b) + intel graphics 630)

re-use SDA2 for / & ESP, no /home is selected (I'll do that manually given issue last time)...

( SDA3 is currently / for noble, plus a /home partition also exists but these are NOT USED for this install )

this has failed, but why?? this install was repeated, and `ubuntu-bug calamares` executed before I rebooted on subsequent install; both installs failed identically....

** EXPECTED RESULT

- install completes; reboot and GRUB shows two installed systems, being new JAMMY INSTALL + prior NOBLE install

- system boots & allows me to login

** ACTUAL RESULT

- no 24.04 LTS system was detected by grub?? as grub shows only one (L) Ubuntu system offered
- system failed to boot

** NOTICED

There should be two options in grub (noble + this new jammy install) but only one shows??

Further the kernel attempting to be booted according to grub is 6.5??? yet manifest shows the kernel should be `linux-generic-hwe-22.04 6.2.0.39.40~22.04.16` thus the grub appears to be the noble grub...

boot ended at busybox, UUID wasn't found according to messages (when 'quiet splash' disable). Did the GRUB-INSTALL FAIL ???

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: calamares 3.2.61-0ubuntu0.1
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.shellprocess_logs.conf:
 ---
 dontChroot: true
 timeout: 30
 script:
     - calamares-logs-helper @@ROOT@@
.etc.calamares.modules.unpackfs.conf:
 ---
 unpack:
     - source: "/cdrom/casper/filesystem.squashfs"
         sourcefs: "squashfs"
         destination: ""
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.470.3
CurrentDesktop: LXQt
Date: Fri Dec 1 23:34:19 2023
LiveMediaBuild: Lubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20231130)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:22.04.4.3
 calamares-settings-lubuntu 1:22.04.4.3
 xfsprogs 5.13.0-1ubuntu2
 btrfs-progs 5.16.2-1
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Guiver (guiverc) wrote :
Changed in calamares (Ubuntu):
status: New → Incomplete
status: Incomplete → New
Chris Guiver (guiverc)
description: updated
summary: - calamares install issue - jammy
+ calamares install (grub-install?) issue - jammy
Revision history for this message
Chris Guiver (guiverc) wrote :

I wonder if the issue is Secure-boot related ???

(trying to use grub-rescue & I'm getting secure boot reasons for failing to boot now)

Revision history for this message
Chris Guiver (guiverc) wrote :

I installed Ubuntu Desktop (jammy daily) yesterday successfully using the same parameters (sda2 for / & ESP only partitions used)

I did note proposed packages existed on the Ubuntu Desktop ISO, but unsure if this differs to my used Lubuntu ISO from the day before.

Revision history for this message
Chris Guiver (guiverc) wrote (last edit ):

(THIS COMMENT MAYBE UNRELATED.. as it relates to a NOBLE install, and not jammy)
I've experienced this (OR SIMILAR) on a legacy/BIOS box too
- hp dc7700 (c2d-e6320, 8gb amd/ati rv610/radeon hd2400 pro/xt)
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2046024

(sorry, I forget which release I was installing when I made this comment/link)

Revision history for this message
Simon Quigley (tsimonq2) wrote :

I'm not seeing an error in the log; what I am seeing is this:

2023-12-01 - 22:58:04 [6]: [PYTHON JOB]: "Bootloader: grub (efi)"
2023-12-01 - 22:58:04 [6]: .. Running ("grub-install", "--target=x86_64-efi", "--efi-directory=/boot/efi", "--bootloader-id=ubuntu", "--force")

Maybe grub-update is missing??

Changed in calamares (Ubuntu):
status: New → Incomplete
status: Incomplete → Opinion
Revision history for this message
Simon Quigley (tsimonq2) wrote :

I don't know what to put the bug status for now - I trust your judgement.

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2045410

tags: added: iso-testing
To post a comment you must log in.