Ubuntu
grub2 package

bionic daily install to sdc, reboot and UUID not found (grub rescue)

Bug #1889041 reported by Chris Guiver
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
New
Undecided
Unassigned
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

xubuntu daily (bionic) qa-test install to SDC (full disk)
on reboot though, system reports UUID isn't found & only grub rescue

`blkid` reveals
/dev/sdc1: UUID="72d29572-9844-448c-adda-597d97d1a598" TYPE="ext4" PARTUUID="ec71cd4e-01"
which is where I installed to, and what it reported (I believe) wasn't found

please ignore this report until I do more digging, this box isn't used except for qa-testing, and I want to ensure I didn't make a mistake.

(successful test earlier today was to SDA not SDC)

this system has been rebooted into daily/live for ubuntu-bug, which will give me more details to explore I hope. No ubiquity log as I didn't expect issues on reboot.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.14
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic i686
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: i386
CasperVersion: 1.394.3
CurrentDesktop: XFCE
Date: Mon Jul 27 05:34:02 2020
InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd quiet splash ---
LiveMediaBuild: Xubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200727)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Guiver (guiverc) wrote :
Changed in ubiquity (Ubuntu):
status: New → Incomplete
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/1889041

tags: added: iso-testing
Revision history for this message
Chris Guiver (guiverc) wrote :

An earlier Lubuntu (daily) install was made to SDA without issues.

After the Xubuntu failure... I re-ran Lubuntu install but this time tried installing to SDC. It completed and looked good, (just as Xubuntu did), then on reboot - it dropped to GRUB RESCUE just as Xubuntu did.

I booted the LIVE daily image again, the UUID (now changed due to Lubuntu re-format of SDC) was the correct one it was looking for ... but same identical issue.

This box is STRANGE, it has settings for PATA drives, plus SATA, and I suspect issues is this, ie. a quirk to his box & how it handles PATA & SATA drives.. MBR security however is & was off.

SDA is PATA (so is DVD-RW)
SDB & SDC are SATA

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

A re-install of Xubuntu 18.04/bionic daily has completed.

Grub correctly shows (x)ubuntu on sda1, and another Ubuntu on sdc1 (last install in comment #3 was lubuntu)...

On selecting SDC1/Ubuntu 18.04 I get the error

----
error: no such device: 31c58e86-0f12-4980-ac89-eaa469ca4e80
error: hd2 cannot get C/H/S values.
error: you need to load kernel first.

Press any key to continue.
----

I've seen that issue before, had it on a QA-test install of 18.04.4, so it's not new, but it wasn't there during eoan (development) cycle, as it was the error on the eoan partition (now erased) on SDC, that booted fine until a RC of 18.04.4 was installed creating that issue. As I didn't care about eoan it was not a high priority (it'll be recorded on a qa-test for 18.04.4 if I can find it; this is a duplicate??)

I'm now convinced issue is with `grub2-common` (grub-install), wonder if there is a wordsize change or something... but I'm guessing...

Changed in ubiquity (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Chris Guiver (guiverc) wrote :

Further to comment #4, the C/H/S issue could still be a quirk on this boxes handling of SATA & PATA drives, and/or combination of BIOS setting that impacts or interferes with grub.... ie. will only impact some prehistoric boxes that contain both PATA & SATA drives, which will be EOL in Ubuntu world come 2019-April or end of x86 era maybe

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

Maybe related - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861788

(or it's the duplicate bug I'm looking for!)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.