[Bug 1552539] Re: Ubiquity Erase Disk and Install Fails to create Swap Space
Martin Pitt
martin.pitt at ubuntu.com
Wed Apr 20 12:46:25 UTC 2016
So according to the traces, these are the commands that ubiquity calls:
swapoff /dev/sda3
grep "^/dev/sda3 " /proc/swaps
log-output -t partman --pass-stdout mkswap /dev/sda3
and the latter fails with
open("/dev/sda3", O_RDONLY|O_EXCL|O_CLOEXEC) = -1 EBUSY (Device or
resource busy
I tried to reproduce this with just
swapoff /dev/sda3; grep "^/dev/sda3 " /proc/swaps; sleep 0.5; mkswap
/dev/sda3; swapon /dev/sda3
for varying values in the sleep (or no sleep at all), so far not
successfully yet. I also don't believe that this is generally broken as
it is quite hard to reproduce. Slower machines/hard disks do seem to
help, though.
Another theory is that something else has the swap device open; ubiquity
(or some called programs) open it quite a lot, things like blkid; but
mkswap works fine while the device is opened read-only (tail -f
/dev/sda3) or even write-only (dd of=/dev/sda3) and I also let blkid
race against mkswap:
while blkid -p /dev/sda3; do true; done # in one shell
while mkswap /dev/sda3; do true; done # in another
on Dave's machine, and all of these work.
I also put systemd into debug mode (systemd-analyze set-log-level debug)
and watched journalctl -f to verify that there is no automatic
activation of the new swap partition after mkswap. It just tracks
swapoff and swapon via the uevents.
Thus so far I'm none the wiser yet.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/1552539
Title:
Ubiquity Erase Disk and Install Fails to create Swap Space
Status in Release Notes for Ubuntu:
Fix Released
Status in casper package in Ubuntu:
Fix Released
Status in ubiquity package in Ubuntu:
Confirmed
Bug description:
Daily Build of Gnome 16.04 using installation option to Erase Disk and Install fails with following message:
"The creation of swap space in Partition #5 of SCSi3(0,0,0) (sda) failed.
This is a Virtualbox based install using virtual disks that had a prior installation of a daily build.
The installation process does not fail when I delete and recreate the Virtual Machine.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.47
ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
Uname: Linux 4.4.0-9-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CasperVersion: 1.367
Date: Thu Mar 3 04:26:59 2016
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160302)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1552539/+subscriptions
More information about the foundations-bugs
mailing list