Fresh Ubuntu Install Crash

[Tim Wagaman]

Installing a fresh installation of Ubuntu from a USB stick crashed during installation.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.19
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/efi.img
CasperMD5CheckResult: fail
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 22 19:54:40 2022
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Erich Eickmeyer (eeickmeyer)]

From the description:

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

This means either you had a bad download, bad read to media, or bad write to media. Please re-download the .iso image, re-write to media, and try installing again.

[Chris Guiver (guiverc)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Bug reporting is about finding & fixing problems, thus preventing future users from hitting the same bug. You seem to need support more than have issues with a bug (your issue could be hardware related or lots of things).

Because of media validation fail; errors can be expected and what is reported in the logs may not be trustworthy, due to potentially bad coded read from a invalid ISO or bad write of ISO to installation media.

I do note

Mar 22 23:53:58 ubuntu kernel: [ 1022.718621] EXT4-fs error (device sdb2): htree_dirblock_to_tree:1027: inode #4720121: comm find: Directory block failed checksum
Mar 22 23:53:58 ubuntu kernel: [ 1022.718627] Aborting journal on device sdb2-8.
Mar 22 23:53:58 ubuntu kernel: [ 1022.719481] EXT4-fs (sdb2): Remounting filesystem read-only

I'd check the health of device sdb - https://help.ubuntu.com/community/Smartmontools

This bug report can be converted to a question (which is aimed at support). You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709