Installation in live disc crashes

[Robert G]

I set up the installation to install on my secondary 160GB Toshiba drive that I had recently just set up with a new HDD caddy. Upon installing and entering my credentials, I went to another workspace to browse the web. I have no idea what exactly was being installed at this point, but it came to me with an error saying it failed to finish the installation and/or it crashed (I cannot remember which). Hope you can either resolve or prevent this from happening.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.20
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
CasperVersion: 1.315
Date: Sun Sep 23 23:35:58 2012
LiveMediaBuild: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
ProcEnviron:
 TERM=unknown
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu Foundations Team Bug Bot (crichton)]

Exception during installation:
Sep 24 03:35:47 ubuntu plugininstall.py: Traceback (most recent call last):
Sep 24 03:35:47 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1728, in <module>
Sep 24 03:35:47 ubuntu plugininstall.py: install.run()
Sep 24 03:35:47 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 55, in wrapper
Sep 24 03:35:47 ubuntu plugininstall.py: func(self)
Sep 24 03:35:47 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 165, in run
Sep 24 03:35:47 ubuntu plugininstall.py: self.configure_plugins()
Sep 24 03:35:47 ubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 538, in configure_plugins
Sep 24 03:35:47 ubuntu plugininstall.py: raise install_misc.InstallStepError("Plugin %s failed with code %s" % (plugin.NAME, ret))
Sep 24 03:35:47 ubuntu plugininstall.py: InstallStepError: Plugin console_setup failed with code 126
Sep 24 03:35:47 ubuntu plugininstall.py:

[Brian Murray (brian-murray)]

It appears that there is an issue communicating with one of your disks:

Sep 24 03:27:25 ubuntu kernel: [ 852.365943] ata2.00: exception Emask 0x10 SAct 0x1 SErr 0x400000 action 0x6 frozen
Sep 24 03:27:25 ubuntu kernel: [ 852.365951] ata2.00: irq_stat 0x08000000, interface fatal error
Sep 24 03:27:25 ubuntu kernel: [ 852.365954] ata2: SError: { Handshk }
Sep 24 03:27:25 ubuntu kernel: [ 852.365958] ata2.00: failed command: WRITE FPDMA QUEUED
Sep 24 03:27:25 ubuntu kernel: [ 852.365963] ata2.00: cmd 61/00:00:3f:5c:13/04:00:00:00:00/40 tag 0 ncq 524288 out
Sep 24 03:27:25 ubuntu kernel: [ 852.365964] res 40/00:00:3f:5c:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep 24 03:27:25 ubuntu kernel: [ 852.365967] ata2.00: status: { DRDY }
Sep 24 03:27:25 ubuntu kernel: [ 852.365975] ata2: hard resetting link
Sep 24 03:27:25 ubuntu kernel: [ 852.688058] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 24 03:27:25 ubuntu ubiquity[5268]: switched to page console_setup
Sep 24 03:27:25 ubuntu kernel: [ 853.268604] ata2.00: configured for UDMA/33
Sep 24 03:27:25 ubuntu kernel: [ 853.268677] ata2: EH complete
Sep 24 03:27:26 ubuntu kernel: [ 853.870070] ata2.00: exception Emask 0x10 SAct 0x3ff SErr 0x400000 action 0x6 frozen
Sep 24 03:27:26 ubuntu kernel: [ 853.870075] ata2.00: irq_stat 0x08000000, interface fatal error
Sep 24 03:27:26 ubuntu kernel: [ 853.870078] ata2: SError: { Handshk }
Sep 24 03:27:26 ubuntu kernel: [ 853.870081] ata2.00: failed command: WRITE FPDMA QUEUED

[Brian Murray (brian-murray)]

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 the disk to which you are trying to install Ubuntu. I'd recommend performing a back up of your existing operating system and then investigating the situation. Measures you might take include checking cable connections for your disks and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck!