installation displays error "cannot remove xxxx (file adress) read-only file", then installer crashes

[Denys Ferreira Malta]

..

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CasperVersion: 1.427
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 26 20:59:39 2019
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 LANGUAGE=C.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD). You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM. You might also retry your installation with new media. In the event that is is not in fact an error with your installation media please set the bug's status back to New. Thanks and good luck!

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Chris Guiver (guiverc)]

Checking through the Syslog, IO errors are repetitive. Because of numerous IO errors the file system flips to RO to protect any data on it.

Dec 26 23:26:00 ubuntu kernel: [ 8.716013] EXT4-fs warning (device sda1): ext4_clear_journal_err:5115: Filesystem error recorded from previous mount: IO failure
..
Dec 26 23:59:01 ubuntu kernel: [ 2003.111196] blk_update_request: I/O error, dev sda, sector 9393041 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0

I would check your hardware's health (using your drives SMART capabilities etc), then once corrected, try again.

If you need help, you could try 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

[Launchpad Janitor (janitor)]

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