[Bug 1992978] Re: Clean install, crash followed 'error removing initramfs-tools'

Chris Guiver 1992978 at bugs.launchpad.net
Sat Oct 15 01:53:29 UTC 2022


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

Oct 14 13:28:29 ubuntu kernel: [ 2299.126246] blk_update_request: I/O error, dev nvme0n1, sector 488144792 op 0x1:(WRITE) flags 0x4800 phys_seg 127 prio class 0
Oct 14 13:28:29 ubuntu kernel: [ 2299.126271] Buffer I/O error on dev nvme0n1p4, logical block 121527007, async page read
Oct 14 13:28:29 ubuntu kernel: [ 2299.126279] blk_update_request: I/O error, dev nvme0n1, sector 488142712 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
Oct 14 13:28:29 ubuntu kernel: [ 2299.126316] blk_update_request: I/O error, dev nvme0n1, sector 488142696 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
Oct 14 13:28:29 ubuntu kernel: [ 2299.126332] blk_update_request: I/O error, dev nvme0n1, sector 488142680 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
Oct 14 13:28:29 ubuntu kernel: [ 2299.126346] blk_update_request: I/O error, dev nvme0n1, sector 488142656 op 0x1:(WRITE) flags 0x800 phys_seg 3 prio class 0
Oct 14 13:28:29 ubuntu kernel: [ 2299.126374] blk_update_request: I/O error, dev nvme0n1, sector 902368168 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Oct 14 13:28:29 ubuntu kernel: [ 2299.126385] EXT4-fs warning (device dm-1): ext4_end_bio:344: I/O error 10 writing to inode 29753979 starting block 112222325)
Oct 14 13:28:29 ubuntu kernel: [ 2299.126401] blk_update_request: I/O error, dev nvme0n1, sector 488142648 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Oct 14 13:28:29 ubuntu kernel: [ 2299.126409] Buffer I/O error on dev dm-1, logical block 60444135, lost sync page write
Oct 14 13:28:29 ubuntu kernel: [ 2299.126417] blk_update_request: I/O error, dev nvme0n1, sector 2666432 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0
Oct 14 13:28:29 ubuntu kernel: [ 2299.126434] blk_update_request: I/O error, dev nvme0n1, sector 488142752 op 0x1:(WRITE) flags 0x800 phys_seg 3 prio class 0
Oct 14 13:28:29 ubuntu kernel: [ 2299.126439] EXT4-fs error (device dm-1): ext4_check_bdev_write_error:217: comm kworker/u12:3: Error while async write back metadata
Oct 14 13:28:29 ubuntu kernel: [ 2299.126454] Aborting journal on device dm-1-8.
..
Oct 14 13:28:29 ubuntu kernel: [ 2299.544977] EXT4-fs error (device nvme0n1p3): ext4_journal_check_start:83: comm rm: Detected aborted journal
Oct 14 13:28:29 ubuntu kernel: [ 2299.544983] EXT4-fs (nvme0n1p3): 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
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1992978

Title:
  Clean install, crash followed 'error removing initramfs-tools'

Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Attempting clean install after computer failed to boot.  
  Unsure how to attach requested log files, attempting copy & paste seems to give only filenames (unless content is hidden beneath); both included in the hope they're useful.  (I am a very basic, unskilled user, really don't much know my way around the internals... any guidance would be welcome.  If possible to copy messages to keithjbmobile at gmail.com it will help, that is my emergency backup email.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity 22.04.17
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  Date: Fri Oct 14 14:30:46 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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




More information about the foundations-bugs mailing list