Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This installation looks like it was caused by a corrupted file system,
or device problems (sda1). I notice in the logs
Mar 4 23:05:56 ubuntu kernel: [ 795.961000] blk_update_request: I/O error,
dev sda, sector 672209160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Mar 4 23:05:56 ubuntu kernel: [ 795.961014] ata2: EH complete
Mar 4 23:05:56 ubuntu kernel: [ 795.961046] EXT4-fs error (device sda5):
__ext4_find_entry:1535: inode #20972209: comm dpkg: reading directory lblock 0
Mar 4 23:05:56 ubuntu kernel: [ 796.019180] Aborting journal on device sda5-8.
Mar 4 23:05:56 ubuntu kernel: [ 796.034363] EXT4-fs (sda5): Remounting
filesystem read-only
I've marked this bug as incomplete (due hardware issues), if you believe
I'm in error please leave a comment as to why, and you can return the
status to "New".
I suggest you validate the health of your hardware (esp. disk by
checking it's SMART status using `smartctl`, `gnome-disks` or whichever
tool you prefer), and possibly the integrity of your partition table
(https://help.ubuntu.com/community/Smartmontools). If you're unfamiliar
with these, I suggest seeking support, options available can be seen at
https://discourse.ubuntu.com/t/finding-help/709
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917814
Title:
Install crashed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1917814/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
