Jan 1 18:23:57 ubuntu kernel: [17180452.688000] EXT3-fs error (device sda2):
ext3_new_block: Allocating block in system zone - blocks from 458754, length 1
Jan 1 18:23:57 ubuntu kernel: [17180452.688000] Aborting journal on device sda2.
Jan 1 18:23:57 ubuntu kernel: [17180452.792000] ext3_abort called.
Jan 1 18:23:57 ubuntu kernel: [17180452.792000] EXT3-fs error (device sda2):
ext3_journal_start_sb: Detected aborted journal
Jan 1 18:23:57 ubuntu kernel: [17180452.792000] Remounting filesystem read-only
Jan 1 18:23:57 ubuntu kernel: [17180452.792000] EXT3-fs error (device sda2):
ext3_free_blocks: Freeing blocks in system zones - Block = 458754, count = 1
Jan 1 18:23:57 ubuntu kernel: [17180452.792000] EXT3-fs error (device sda2) in
ext3_free_blocks_sb: Journal has aborted
This probably indicates a problem with your disk. As part of the fix for
bug 67598 I've made Ubiquity in Feisty report this more sensibly, but
that's only a workaround and the real fix will probably have to be with
hardware on your end.
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Colin Watson
Status: Unconfirmed => Fix Released
--
Installer crashed
https://launchpad.net/bugs/77608
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
