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 (sda6). I notice in the logs Feb 5 02:46:35 ubuntu ubiquity: Error reading device /dev/sda6 at 0 length 4096. Feb 5 02:46:35 ubuntu kernel: [27830.148187] EXT4-fs error (device sda10): ext4_journal_check_start:83: Detected aborted journal Feb 5 02:46:35 ubuntu kernel: [27830.148191] EXT4-fs (sda10): Remounting filesystem read-only Feb 5 02:46:35 ubuntu ubiquity: mkdir: cannot create directory ‘/target/media’ Feb 5 02:46:35 ubuntu ubiquity: : Read-only file system 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/1914731 Title: [Errno 30] Read-only file system 'usr/bin' -> 'target/bin' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1914731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
