Ubuntu 18.04-Crashed installation

Bug #1767465 reported by Radu Axente
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Tried to install Ubuntu MATE 18.04 (release) while connected via WLAN to the Internet.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
Date: Fri Apr 27 20:15:43 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Radu Axente (radax05) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Phillip Susi (psusi) wrote :

Your installation medium is corrupt; you will need to recreate it and may want to verify it using the check disc option at the boot menu.

Changed in ubiquity (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Radu Axente (radax05) wrote :

Same installation medium USB-Stick (SANDisk 4GB USB2) has been used on 3 (three) different PCs...

If I decide to connect to the Internet (WLAN) when starting the installation and install updates while installing the system, the installation crashes on all 3 (three) PCs.

If I decide to not connect to the Internet (WLAN) when starting the installation and do not install updates while installing the system, the installation finishes without a crash on all 3 (three) PCs.

I've installed the updates after rebooting the PCs for the first time after installation.

This is not a new bug, I suppose.

I've encountered the same behaviour on all 3 PCs when installing Ubuntu MATE 16.10, 17.04 and 17.10 and not 18.04.

And the same happened when I tried to install Linux Mint 18.1 some months ago.

Thank you for taking these facts into consideration.

I do not mind if nothing happens, perhaps I'm a "unique" case, but... really ? On 3 different PCs with Samsung SSDs while connected via WLAN (Intel WLAN/Bluetooth modules) ?

Anyway, as long as the system can be installed correctly and updated afterwards, everything is OK for me.

Changed in ubiquity (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Radu Axente (radax05) wrote :

Correction: "I've encountered the same behaviour on all 3 PCs when installing Ubuntu MATE 16.10, 17.04 and 17.10 and now 18.04."

Revision history for this message
Phillip Susi (psusi) wrote :

That is very strange. From your log:

Apr 27 18:15:30 ubuntu-mate kernel: [ 368.540825] SQUASHFS error: zlib decompression failed, data probably corrupt
Apr 27 18:15:30 ubuntu-mate kernel: [ 368.540829] SQUASHFS error: squashfs_read_data failed to read block 0xf166f3a
Apr 27 18:15:30 ubuntu-mate kernel: [ 368.541798] SQUASHFS error: zlib decompression failed, data probably corrupt
Apr 27 18:15:30 ubuntu-mate kernel: [ 368.541799] SQUASHFS error: squashfs_read_data failed to read block 0xf166f3a

This means the squashfs image is corrupt. If it is not corrupt on disk ( run the check disc to see ), then it must have become corrupt in memory. Try running the memtest option from the boot menu for at least 15 minutes and see if that is ok. The only other way I can think of for this to happen in relation to the network updates is if the network adapter somehow is corrupting memory.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.