Trying to re-install 20.04 choosing option 1 (erase and re-install) and the installer gets this error.

Bug #1897301 reported by Montecreasor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

My Nvidia graphics card stopped loading on Ubuntu 20.04 yesterday (works find when I boot to Windows 10) so I've found that the only way to get it to work again with Ubuntu is to re-install the OS.

After choosing install option 1 (erase 20.04 and re-install) the installer fails and asks me to log this error.

Please respond ASAP since I can't use my Thinkpad P70 until you fix this issue.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/efi.img
CasperMD5CheckResult: fail
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 25 11:08:58 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANGUAGE=en_CA.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Montecreasor (montecreasor) wrote :
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.

From the bug description:

CasperMD5CheckMismatches: ./boot/grub/efi.img
CasperMD5CheckResult: fail

It's possible you had a bad write to your media or for some other reason its contents could not be read correctly. Please always allow the integrity check to complete so that any errors can be displayed.

Closing as "Invalid" due to the time that elapsed since this issue was reported.

Changed in ubiquity (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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