ubiquity crashed due to input/output error (disk/file system is ok !!)

Bug #1775705 reported by martin suchanek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

ubuntu 18.04 LTS
ubiquity

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 7 22:47:04 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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)

Revision history for this message
martin suchanek (martin-suc) wrote :
Revision history for this message
Phillip Susi (psusi) wrote :

It appears that your hard disk simply stopped responding during the install, and that it was a qemu disk. What is your host system? It looks like qemu broke.

Jun 7 20:44:34 ubuntu kernel: [ 1678.198766] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun 7 20:44:34 ubuntu kernel: [ 1678.198770] ata1.00: failed command: FLUSH CACHE EXT
Jun 7 20:44:34 ubuntu kernel: [ 1678.198774] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jun 7 20:44:34 ubuntu kernel: [ 1678.198774] res 40/00:00:00:4f:c2/00:00:00:00:00/a0 Emask 0x4 (timeout)
Jun 7 20:44:34 ubuntu kernel: [ 1678.198776] ata1.00: status: { DRDY }
Jun 7 20:44:39 ubuntu kernel: [ 1683.238632] ata1: link is slow to respond, please be patient (ready=0)
Jun 7 20:44:44 ubuntu kernel: [ 1688.218497] ata1: device not ready (errno=-16), forcing hardreset

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.