[Bug 1921661] Re: Simply crashed when installing to a preformatted disk. thats ery unusual. Regards, RL

[Chris Guiver]

Thank you for taking the time to report this issue and helping to make
Ubuntu better.

This problem appears to be related to hardware errors. I notice in the
logs

Mar 29 00:47:53 ubuntu kernel: [ 1585.461476] sd 2:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Mar 29 00:47:53 ubuntu kernel: [ 1585.461518] sd 2:0:0:0: [sdb] tag#9 Sense Key : Illegal Request [current] 
Mar 29 00:47:53 ubuntu kernel: [ 1585.461531] sd 2:0:0:0: [sdb] tag#9 Add. Sense: Invalid field in cdb
Mar 29 00:47:53 ubuntu kernel: [ 1585.461543] sd 2:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 08 0e 9a cd 60 00 00 08 00
Mar 29 00:47:53 ubuntu kernel: [ 1585.461557] blk_update_request: critical target error, dev sdb, sector 245026144 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
Mar 29 00:47:53 ubuntu kernel: [ 1585.461607] blk_update_request: critical target error, dev sdb, sector 245026144 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
Mar 29 00:47:53 ubuntu kernel: [ 1585.461741] Aborting journal on device sdb4-8.
Mar 29 00:47:53 ubuntu kernel: [ 1585.464411] EXT4-fs error (device sdb4): ext4_journal_check_start:83: Detected aborted journal
Mar 29 00:47:53 ubuntu kernel: [ 1585.464421] EXT4-fs (sdb4): Remounting filesystem read-only
Mar 29 00:47:53 ubuntu kernel: [ 1585.464720] EXT4-fs error (device sdb4): ext4_journal_check_start:83: Detected aborted journal

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: ubuntu
       Status: New => Incomplete

** Package changed: ubuntu => ubiquity (Ubuntu)

-- 
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/1921661

Title:
  Simply crashed when installing to a preformatted disk. thats ery
  unusual. Regards,RL

Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Tried to install Ubuntu 20 Desktop from an USB Stick to an external USB disk with reformatting
  existing partitions (/boot 500M ext3, /boot/efi 200M Efi (=FAT), 32GB / ext3, no swap as ample RAM
  16GB at hand) So no /var/log or else.just CRASH. uNTIL NOW, DONT LIKE fEDORA/bsd, posasibly have
  to reconsider.
  Regards, RL

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity 20.10.13
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 29 03:01:27 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   LC_NUMERIC=C.UTF-8
  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/1921661/+subscriptions