Was installing OEM Dusty (19.04) and suddenly installation failed due to Ubiquity.

[pcwiz84]

Have been battling issues with hard drive having "garbage." While I was cleaning the "garbage," it suddenly stopped and so I force powered down. Promptly afterwards, I started an OEM installation and then next thing I know installation failed. This is the first time an installation has failed since making attempts to have my laptop be a Linux box for VHS home video digitizing and DJ gigs. Every time the bootloader would fail to load, so I have been attempting to get it installed on this system.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6
Uname: Linux 5.0.0-13-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
Date: Thu Oct 31 14:56:02 2019
InstallCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper only-ubiquity initrd=/casper/initrd --- priority=low oem-config/enable=true
LiveMediaBuild: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416)
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)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

[Jean-Baptiste Lallement (jibel)]

From syslog it's a hardware issue, there are memory and disk errors. Please check your hardware. Closing as invalid.