[Bug 1743643] Re: Install to dirty disk with swap fails
Ryan Harper
1743643 at bugs.launchpad.net
Wed Feb 21 17:08:12 UTC 2018
Can you:
journalctl -b | grep -i "curtin: Installation started."
That should dump the curtin version that was used; This is fixed in trunk
but not yet uploaded to bionic.
It's not clear how the live image obtains curtin, whether via the subiquity
snap
or using curtin from deb.
On Wed, Feb 21, 2018 at 10:46 AM, Andreas Hasenack <andreas at canonical.com>
wrote:
> I'm still seeing this in yesterday's (feb 21st) image, fwiw.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1743643
>
> Title:
> Install to dirty disk with swap fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1743643/+subscriptions
>
--
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/1743643
Title:
Install to dirty disk with swap fails
Status in curtin:
Fix Committed
Status in subiquity:
Won't Fix
Status in casper package in Ubuntu:
Confirmed
Bug description:
Description:
Complete an install with a custom disk setup including swap and on a 2nd install the install fails.
Steps to reproduce:
1. Install to disk with following custom disk partitions:
* 3G ext4 /
* 1G ext4 /boot
* 1G ext4 /home
* 1G swap
2. Reboot
3. Install again with default options
4. Install fails
Logs:
Subiquity: https://paste.ubuntu.com/26399863/
Curtin: https://paste.ubuntu.com/26399862/
I also saw this with:
* 17gb ext4 /
* 1gb swap
Logs:
Subiquity: https://paste.ubuntu.com/26399883/
Curtin: https://paste.ubuntu.com/26399884/
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1743643/+subscriptions
More information about the foundations-bugs
mailing list