Hi Chris Thanks for getting back. I'm no expert at deciphering logs but from the bit you mentioned in looks like the errors were to do with sda1 which I don't think was the SSD to which I was attempting to install Ubuntu, I'm pretty sure it is the one containing the stand alone Cloudready software.
As I had no reason to suspect the new SSD to be faulty [because it had initialised o.k. - formatted the Ext4 partition, followed by a copy of a test file] I decided to try again. This time I physically disconnected the power to other 2 SSDs [Cloudready and Windows 10] before booting up from the USB drive with the install file for 19.04. This time [due to only one SSD being present] when the system loaded from USB and I was able to install 19.04 to the new SSD without any issues. It looks to me [although I don't no why and can't prove anything] that the earlier failed attempts were down to the fact that the other SSDs were present even though I had elected to install the grub data on the same volume / partition as the Ubuntu software. Don't know if this helps you any but as everything is running o.k. I'm happy just to leave the ticket closed off. Cheers Phil On Sat, 24 Aug 2019 at 13:15, Chris Guiver <guiv...@gmail.com> wrote: > 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 subscribed to the bug > report. > 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. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1841310/+subscriptions > -- Cheers, Phil Visit Help Index 4 You <https://sites.google.com/view/helpindex4you> to relieve your technical headaches Go to Dropbox <http://db.tt/DzTFBWg2> for your FREE Cloud Storage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1841310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
