Installer crash with unformatted partition
Closed, ResolvedPublic

Description

Mustafa Muhammad wrote on 30. June 2015 17:56:

Package: calamares

Before I boot Tanglu, I created an unformatted partition, in the installer I chose to format it ext4 and mount it as /
The installer crashed because of this.

importbot added a subscriber: importbot.

Matthias Klumpp wrote on 30. June 2015 22:31:

Hi!
Which version of the installer did you try?
What does apt-cache policy calamares show you? You should have Calamares 1.1 installed, which shouldn't show this issue...
Cheers,

Matthias

Mustafa Muhammad wrote on 03. July 2015 00:12:

root@tanglu-os:~# apt-cache policy calamares
calamares:

Installed: 1.1-0tanglu1
Candidate: 1.1-0tanglu1
Version table:

1.1-0tanglu1 0
500 http://archive.tanglu.org/tanglu/ chromodoris/main amd64 Packages
100 /var/lib/dpkg/status

The message from Calamares says:
Failed to unpack image /lib/live/mount/medium/live/filesystem.squashfs
rsync failed with error code 11.

But I noticed that the partition is still unformatted

Matthias Klumpp wrote on 03. July 2015 23:46:

Okay, this is highly likely an issue with your installation media.
Could you maybe verify the checksums of the downloaded iso image, and also ideally verify the integrity of the files on your installation medium, and, in case it's an USB-stick, verify that the stick is not damaged?

Mustafa Muhammad wrote on 04. July 2015 14:45:

Matthias Klumpp wrote:

Okay, this is highly likely an issue with your installation media.
Could you maybe verify the checksums of the downloaded iso image, and also ideally verify the integrity of the files on your installation medium, and, in case it's an USB-stick, verify that the stick is not damaged?

Not likely, after formatting the partition before the installation, everything went fine, I tried this two times.

Matthias Klumpp wrote on 07. July 2015 20:47:

Really strange, I tried multiple things to reproduce this, but I never got this failure...
Could you maybe give me the output of fdisk -l on the "broken" configuration?

Mustafa Muhammad wrote on 08. July 2015 15:42:

root@mustafa-pc:/home/mustafa# fdisk -l
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5B46572E-E0A0-4A47-A81D-95A537FC8DB9

Device Start End Sectors Size Type
/dev/sda1 202752 204799 2048 1M BIOS boot
/dev/sda2 204800 409599 204800 100M Linux filesystem
/dev/sda3 409600 8798207 8388608 4G Microsoft basic data
/dev/sda4 8798208 218513407 209715200 100G Microsoft basic data
/dev/sda5 218513408 428228607 209715200 100G Linux filesystem
/dev/sda6 428228608 533086207 104857600 50G Linux filesystem
/dev/sda7 533086208 604170239 71084032 33.9G Linux filesystem
root@mustafa-pc:/home/mustafa# parted
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: ATA WDC WD3200AAJS-0 (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 104MB 105MB 1049kB bios_grub
2 105MB 210MB 105MB
3 210MB 4505MB 4295MB linux-swap(v1) msftdata
4 4505MB 112GB 107GB ext4 msftdata
5 112GB 219GB 107GB ext4
6 219GB 273GB 53.7GB btrfs
7 273GB 309GB 36.4GB

The partition is sda7, parted result is more accurate.

ximion raised the priority of this task from "High" to "Unbreak Now!". · Mon, Jul 13, 8:47 PM

ximion added a comment. · Mon, Jul 13, 8:54 PM
I wonder if this is (related to) this Calamares bug: https://calamares.io/bugs/browse/CALAPM-3 - looks pretty similar.

ximion added a comment.Edited · · Mon, Jul 13, 9:00 PM
Still, a backtrace of this crash with calamares-dbg installed would be very helpful!

ximion lowered the priority of this task from "Unbreak Now!" to "High". · Mon, Jul 13, 9:57 PM

Yofel added a subscriber: Yofel. · Mon, Jul 13, 10:31 PM
Found out what happens:

If you create an unformatted partition before running calamares and select manual partitioning, calamares will detect the FS type as "unknown". When telling it to format the partition it will try to preserve the FS type (as you can't select it) which results in a new unformatted partition which it then fails to mount and copy the files to.

Yofel changed the task status from "Incomplete" to "Confirmed". · Mon, Jul 13, 10:31 PM
Yofel edited the task description. (Show Details)

· Mon, Jul 13, 10:40 PM

ximion raised the priority of this task from "High" to "Unbreak Now!". · Tue, Jul 14, 6:01 PM
Marking this issue as release-critical.

ximion set External Issue to https://calamares.io/bugs/browse/CALAPM-6. · Tue, Jul 14, 6:20 PM

ximion closed this task as "Resolved". · Wed, Jul 15, 5:58 PM
ximion claimed this task.
This is fixed with the latest upload of Calamares to Tanglu 3.0 (Chromodoris willani), version 1.1.1+git20150715.afe4d34-0tanglu1. It should be in todays nightly builds too.
Please verify that this has been resolved, and that there are no regressions.

mustafa added a subscriber: mustafa. · Wed, Jul 15, 9:09 PM

mustafa added a comment. · Thu, Jul 16, 8:28 AM
I tested in a VM and it is resolved, thank you.

importbot closed this task as "Resolved".Jul 28 2015, 11:32 AM