crash on ubuntu install

[Martin Miglio]

error on new ubuntu minimal install, default settings with LVM on

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: ./pool/restricted/n/nvidia-graphics-drivers-440/libnvidia-common-440_440.100-0ubuntu0.20.04.1_all.deb
CasperMD5CheckResult: skip
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 16 18:22:45 2021
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
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)

[Chris Guiver (guiverc)]

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

This installation looks like it was caused by a corrupted file system, or device problems (sda1). I notice in the logs

Feb 16 23:22:15 ubuntu kernel: [ 621.992126] sd 2:0:0:0: [sda] tag#148 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
Feb 16 23:22:15 ubuntu kernel: [ 621.992297] sd 2:0:0:0: [sda] tag#148 Sense Key : Medium Error [current]
Feb 16 23:22:15 ubuntu kernel: [ 621.992299] sd 2:0:0:0: [sda] tag#148 Add. Sense: Unrecovered read error
Feb 16 23:22:15 ubuntu kernel: [ 621.992301] sd 2:0:0:0: [sda] tag#148 CDB: Read(10) 28 00 03 66 3a f0 00 02 00 00
Feb 16 23:22:15 ubuntu kernel: [ 621.992303] blk_update_request: I/O error, dev sda, sector
..
Feb 16 23:22:19 ubuntu kernel: [ 625.970238] Aborting journal on device dm-0-8.
Feb 16 23:22:19 ubuntu kernel: [ 625.978878] EXT4-fs (dm-0): Remounting filesystem read-only

I've marked this bug as incomplete (due hardware issues), if you believe I'm in error please leave a comment as to why, and you can return the status to "New".

I suggest you validate the health of your hardware (esp. disk by checking it's SMART status using `smartctl`, `gnome-disks` or whichever tool you prefer), and possibly the integrity of your partition table. If you're unfamiliar with these, I suggest seeking looking up refer to https://discourse.ubuntu.com/t/finding-help/709

[Launchpad Janitor (janitor)]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]