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 (sdb5). I notice in the logs

Jan 31 16:59:12 ubuntu kernel: [ 5700.165980] EXT4-fs error (device sdb5): 
ext4_lookup:1697: inode #278331: comm dpkg: iget: checksum invalid
Jan 31 16:59:12 ubuntu kernel: [ 5700.165987] Aborting journal on device sdb5-8.
Jan 31 16:59:13 ubuntu ubiquity: dpkg: error processing package 
libreoffice-common (--remove):#015
Jan 31 16:59:13 ubuntu ubiquity:  cannot remove 
'/target/usr/share/icons/hicolor/scalable/apps/libreoffice-writer.svg': 
Read-only file system#015
Jan 31 16:59:13 ubuntu ubiquity: dpkg: too many errors, stopping#015
Jan 31 16:59:13 ubuntu ubiquity: dpkg: error: unable to create new file 
'/target//var/lib/dpkg/status-new': Read-only file system#015
Jan 31 16:59:13 ubuntu kernel: [ 5700.822899] EXT4-fs (sdb5): 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. If
you're unfamiliar with these, I suggest seeking looking up  refer to
https://discourse.ubuntu.com/t/finding-help/709  Note: USB media is
usually built to price; so doesn't include error checking like SMART

** 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/1959605

Title:
  Install fail onto USB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1959605/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to