Comment 2 for bug 1842625

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

Sep 4 08:07:13 lubuntu kernel: [ 1536.192279] EXT4-fs error (device sda1): ext4_find_dest_de:1799: inode #1711270: block 6824844: comm install.py: bad entry in directory: inode out of bounds - offset=1144, inode=270147603, rec_len=20, name_len=10, size=4084
Sep 4 08:07:13 lubuntu kernel: [ 1536.207365] Aborting journal on device sda1-8.
Sep 4 08:07:13 lubuntu kernel: [ 1536.223595] EXT4-fs (sda1): Remounting filesystem read-only
Sep 4 08:07:13 lubuntu kernel: [ 1536.223619] EXT4-fs error (device sda1) in ext4_evict_inode:258: Journal has aborted
Sep 4 08:07:13 lubuntu kernel: [ 1536.240652] EXT4-fs error (device sda1) in ext4_create:2460: IO failure

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. If you're unfamiliar with these, I suggest seeking looking up refer to https://discourse.ubuntu.com/t/finding-help/709