[Bug 1841310] Re: Installed new SSD - initialised as Ext4 - installation proceeded o.k until it came to wrire 'grub' then failed.

[Chris Guiver]

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

This package failure looks like it was caused by a corrupted file
system, or device failure. eg. look in the logs and you'll see messages
like these :-

Aug 24 11:13:17 ubuntu ubiquity: mount: /tmp/tmp.sv4y22q1DF: can't read superblock on /dev/sda1.
Aug 24 11:13:17 ubuntu kernel: [  131.667033] EXT4-fs (sda1): unable to read superblock
Aug 24 11:13:17 ubuntu kernel: [  131.667252] EXT4-fs (sda1): unable to read superblock
Aug 24 11:13:17 ubuntu kernel: [  131.667462] EXT4-fs (sda1): unable to read superblock
Aug 24 11:13:17 ubuntu kernel: [  131.667589] SQUASHFS error: squashfs_read_data failed to read block 0x0
Aug 24 11:13:17 ubuntu kernel: [  131.667592] squashfs: SQUASHFS error: unable to read squashfs_super_block

Examining the information you have given us, this does not appear to be
a useful bug report so I am closing it, as it appears to be a faulty
device (or bad write-to-device). If you believe I'm in error, please
leave a comment explaining why and change the status back to 'new'. I
suggest you use the 'check disc for defects' option to validate your
media before install to ensure a good download & write.

** Changed in: ubiquity (Ubuntu)
       Status: New => Invalid

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

Title:
  Installed new SSD - initialised as Ext4 - installation proceeded o.k
  until it came to wrire 'grub' then failed.

Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  At the point of failure - looked at drives available - all seem o.k.
  Do not understand why it was unable to create grub. Have done a
  similar thing recently [multiple SSDs in desktop, and installed Linux
  Mint telling it to place grub on same device as installed system. This
  keeps all of the OS's [Windows 10, Cloudready, Mint, or Ubuntu ?]
  separate and avoids complications. Just switch 'boot' drive using BIOS
  key.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.9
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CasperVersion: 1.405
  Date: Sat Aug 24 12:26:34 2019
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1841310/+subscriptions