This was due to an error on your hard disk:
Sep 20 15:04:01 ubuntu kernel: [17183083.50] hda: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
Sep 20 15:04:02 ubuntu kernel: [17183083.50] hda: dma_intr: error=0x01 {
AddrMarkNotFound }, LBAsect=5756374, sector=5756367
Sep 20 15:04:02 ubuntu kernel: [17183083.50] ide: failed opcode was: unknown
Sep 20 15:04:02 ubuntu kernel: [17183084.60] hda: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
Sep 20 15:04:02 ubuntu kernel: [17183084.60] hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=5756374, sector=5756367
Sep 20 15:04:02 ubuntu kernel: [17183084.60] ide: failed opcode was: unknown
Sep 20 15:04:02 ubuntu kernel: [17183084.60] end_request: I/O error, dev
hda, sector 5756367
Sep 20 15:04:02 ubuntu kernel: [17183084.60] EXT3-fs error (device hda1):
ext3_find_entry: reading directory #339912 offset 0
Sep 20 15:04:02 ubuntu kernel: [17183084.60] Aborting journal on device
hda1.
Sep 20 15:04:02 ubuntu kernel: [17183084.648000] ext3_abort called.
Sep 20 15:04:02 ubuntu kernel: [17183084.648000] EXT3-fs error (device hda1):
ext3_journal_start_sb: Detected aborted journal
Sep 20 15:04:02 ubuntu kernel: [17183084.648000] Remounting filesystem read-only
Thus, the kernel saw too many errors from the drive, and remounted that
filesystem read-only in an attempt to prevent further damage, but this
of course made it rather hard to install anything more to it. If the
disk is at all old, it may be worth looking into a replacement.
(I already have a note in the source code to display a better message
when this happens, if possible.)
** Changed in: ubiquity (Ubuntu)
Status: Unconfirmed => Rejected
--
Installer crashes after copying files
https://launchpad.net/bugs/61454
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
