[Bug 2121320] [NEW] Upgrades prevent booting
Jim
2121320 at bugs.launchpad.net
Sun Aug 24 19:00:30 UTC 2025
Public bug reported:
GigaByte Mobo, AMD with 8 cores. PC.
This is difficult to describe fully. What happened was I could not get
Ubuntu 24.04 to 24.10 to 25.04 upgrade path to work starting last
November '24. Multiple attempts ended with some sort of error each time.
I keep full backups by cloning so I was always able to just install my
clone, update the changed files and get back to normal. Recently, two
auto-updates caused the Red-Screen-Of-Death (RSOD) to show up during
booting to kernel 6.14.0-24 and then to 6.14.0-27 (was at 6.11.0-29
before each update which occurred at different times). Asked for help at
askubuntu but never got an answer that worked to allow booting. So I
burned a live 25.04 thumb drive and just installed a new copy of Ubuntu.
However, this is where the bug report comes in.
Possible BUG: With 25.04 running and booting alone just fine, if I
attached the cloned HDD with the RSOD in order to copy my files, despite
which HDD I told BIOS to boot from, instead of booting I get a "No boot
drive found" error message just after the BIOS splash screen. This tells
me that the RSOD is somehow overriding the BIOS settings because there
WAS a bootable drive. In fact both of them booted alone, and the drive
with the 6.14.0-27 drive would display GRUB and I could boot to
6.11.0-29 if I chose that option.
I was attaching both drives because I wanted to copy my files to the new
installed 25.04 OS drive. Eventually I used my cloning tool attached to
a USB port and was able to copy everything in HOME to the upgraded
25.04.
See this askubutu link for pics and further info:
https://askubuntu.com/questions/1554324/auto-update-will-not-boot-goes-
to-the-red-screen-of-death
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: ubuntu-release-upgrader-core 1:25.04.18
ProcVersionSignature: Ubuntu 6.14.0-28.28-generic 6.14.8
Uname: Linux 6.14.0-28-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.3
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: MATE
Date: Sun Aug 24 11:28:13 2025
InstallationDate: Installed on 2025-08-18 (7 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug dist-upgrade plucky
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/2121320
Title:
Upgrades prevent booting
Status in ubuntu-release-upgrader package in Ubuntu:
New
Bug description:
GigaByte Mobo, AMD with 8 cores. PC.
This is difficult to describe fully. What happened was I could not get
Ubuntu 24.04 to 24.10 to 25.04 upgrade path to work starting last
November '24. Multiple attempts ended with some sort of error each
time. I keep full backups by cloning so I was always able to just
install my clone, update the changed files and get back to normal.
Recently, two auto-updates caused the Red-Screen-Of-Death (RSOD) to
show up during booting to kernel 6.14.0-24 and then to 6.14.0-27 (was
at 6.11.0-29 before each update which occurred at different times).
Asked for help at askubuntu but never got an answer that worked to
allow booting. So I burned a live 25.04 thumb drive and just installed
a new copy of Ubuntu. However, this is where the bug report comes in.
Possible BUG: With 25.04 running and booting alone just fine, if I
attached the cloned HDD with the RSOD in order to copy my files,
despite which HDD I told BIOS to boot from, instead of booting I get a
"No boot drive found" error message just after the BIOS splash screen.
This tells me that the RSOD is somehow overriding the BIOS settings
because there WAS a bootable drive. In fact both of them booted alone,
and the drive with the 6.14.0-27 drive would display GRUB and I could
boot to 6.11.0-29 if I chose that option.
I was attaching both drives because I wanted to copy my files to the
new installed 25.04 OS drive. Eventually I used my cloning tool
attached to a USB port and was able to copy everything in HOME to the
upgraded 25.04.
See this askubutu link for pics and further info:
https://askubuntu.com/questions/1554324/auto-update-will-not-boot-
goes-to-the-red-screen-of-death
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: ubuntu-release-upgrader-core 1:25.04.18
ProcVersionSignature: Ubuntu 6.14.0-28.28-generic 6.14.8
Uname: Linux 6.14.0-28-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.3
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: MATE
Date: Sun Aug 24 11:28:13 2025
InstallationDate: Installed on 2025-08-18 (7 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2121320/+subscriptions
More information about the foundations-bugs
mailing list