Installer mistakenly mounts Btrfs root filesystem at /target/home, and crashes afterwards

Bug #1634102 reported by Grey Seeker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This is a simple install on an SSD, with EFI system partition as sda2 and Btrfs root partition as sda8. When I ran lsblk I noted that sda8 was mounted as /target/home, although I had specifically told the installer to mount it at /. The installer crashed with:

 [Errno 28] No space left on the device

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.14 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CasperVersion: 1.379
Date: Mon Oct 17 13:03:35 2016
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 TERM=unknown
 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
Grey Seeker (greyseek3r) wrote :
Revision history for this message
Grey Seeker (greyseek3r) wrote :

The error message makes sense, if /target does not lie on a separate partition it would be on the live system, and thus showing the error.

Revision history for this message
Jesus Delgado (talpio) wrote :

Simple, your root partition is full (at 100% utilized). You need to free up some space. Fastest way to get breathing room is to remove old log files in /var/log, then look around and see what's taking up so much space. You can easily see the size of individual directories with:

cd /
du -chs *

Other reason is that your Oracle database auditing is turned on, so after you remove all the audit files from the audit directory,then it's OKay.
Regards.

Changed in ubiquity (Ubuntu):
assignee: nobody → Jesus Delgado (talpio)
status: New → In Progress
Revision history for this message
Phillip Susi (psusi) wrote :

It should have the @ subvolume mounted in /target, and the @home subvolume mounted in /target/home. In other words, you should see /dev/sda8 mounted in both places. Are you sure that df or findmnt showed nothing mounted in /home? Did you have the installer format the volume?

Changed in ubiquity (Ubuntu):
assignee: Jesus Delgado (talpio) → nobody
status: In Progress → Incomplete
Revision history for this message
Grey Seeker (greyseek3r) wrote :

I formatted the partition so no data was present. And the only mount point was for /home, and somehow the / wasn't mounted on /target. I checked with df and mount.

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

So you set it to mount sda8 as /, and nothing for /home? Can you post the exact output of df or findmnt?

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.