zesty lvm install hangs while creating device mapper device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debian-installer (Ubuntu) |
Invalid
|
Critical
|
Mathieu Trudel-Lapierre | ||
Zesty |
Invalid
|
Critical
|
Mathieu Trudel-Lapierre | ||
os-prober (Debian) |
Fix Released
|
Unknown
|
|||
os-prober (Ubuntu) |
Fix Released
|
Critical
|
Mathieu Trudel-Lapierre | ||
Zesty |
Fix Released
|
Critical
|
Mathieu Trudel-Lapierre |
Bug Description
Using the ISO dated 20170214, the install appears to hang while 'Running "update-grub"...'. Changing to console 4 the last message is:
50mounted-tests: debug: creating device mapper device /dev/mapper/
During a successful install the following messages are printed and the install completes:
50mounted-tests: debug: creating device mapper device /dev/mapper/
50mounted-tests: debug: mounting /dev/mapper/
50mounted-tests: debug: remove device mapper device /dev/mapper/
os-prober: debug: /dev/mapper/
On a recent instance of this I killed the dmsetup job and the install completed successfully. Something during the create is causing the
lockup.
The preseed used is available [1], however you should be able to do a default install using the ppc64el ISO to reproduce this as LVM is now the default. The server LVM ISO tests [2] have been failing consistently on ppc64el and intermittently on i386 and amd64.
[1] https:/
[2] https:/
description: | updated |
description: | updated |
tags: | added: zesty |
Changed in debian-installer (Ubuntu): | |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
Changed in os-prober (Debian): | |
status: | Unknown → Fix Released |
Changed in debian-installer (Ubuntu Zesty): | |
status: | New → In Progress |
status: | In Progress → Invalid |
Changed in os-prober (Ubuntu Zesty): | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
milestone: | none → ubuntu-17.03 |
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here: iso.qa. ubuntu. com/qatracker/ reports/ bugs/1664731
http://