Installer fails to format DASD during installation using Guided Setup methods
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| partman-partitioning (Ubuntu) |
Fix Released
|
High
|
Dimitri John Ledkov | ||
Bug Description
== Comment: #0 - Michael Roesch <email address hidden> - 2016-01-15 06:46:01 ==
---Problem Description---
When using the "Guided" installation methods, the installer fails to format a DASD correctly. Those error messages are shown when using the respective methods:
- Guided - use entire disk
Error:
Failed to create a swap space ?
The creation of swap space in partition #5 of DASD 0.0.e285 (ECKD) failed.
- Guided - use entire disk and set up LVM
Error:
Unexpected error while creating volume group ?
Autopartitioning using LVM failed because an error occurred while creating the volume group.
Check /var/log/syslog or see virtual console 4 for the details.
- Guided - use entire disk and set up encrypted LVM
Failed to create a file system ?
The ext2 file system creation in partition #1 of DASD 0.0.e285 (ECKD) failed.
For whatever reason, the method "Guided - use the largest continuous free space" does format the DASD correctly.
I have attached syslogs for the failing 3 Guided installation methods and an output of "/proc/partitions" for each test inside the syslog files.
There seems to be a related bug for this but I'm not 100 sure it is the same problem: https:/
Contact Information = <email address hidden>
Machine Type = zVM
---boot type---
VM Reader
---Install repository type---
Local repository
---Install repository Location---
servant.
---Point of failure---
Other failure during installation (stage 1)
== Comment: #3 - Viktor Mihajlovski <email address hidden> - 2016-01-15 07:16:37 ==
Looking at the logs, it seems that for some reason, the DASD is handled as if it was a SCSI disk (e.g. there's an attempt to create a partition #5). I haven't used guided so far, so maybe there's some wrong logic in there which results in writing an MBR to the first track of the DASD. This can also explain the I/O errors in the log.
Related branches
| bugproxy (bugproxy) wrote Syslog for LVM method | #1 |
| tags: | added: architecture-s39064 bugnameltc-135429 severity-medium targetmilestone-inin--- |
| bugproxy (bugproxy) wrote Syslog for Entire Disk method | #2 |
| bugproxy (bugproxy) wrote Syslog for Encrypted LVM method | #3 |
| Changed in ubuntu: | |
| assignee: | nobody → Taco Screen team (taco-screen-team) |
| tags: |
added: targetmilestone-inin1604 removed: targetmilestone-inin--- |
| Ubuntu Foundations Team Bug Bot (crichton) wrote | #4 |
| tags: | added: bot-comment |
| affects: | ubuntu → debian-installer (Ubuntu) |
| Changed in debian-installer (Ubuntu): | |
| assignee: | Taco Screen team (taco-screen-team) → Dimitri John Ledkov (xnox) |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in debian-installer (Ubuntu): | |
| status: | Triaged → In Progress |
| affects: | debian-installer (Ubuntu) → partman-partitioning (Ubuntu) |
| tags: | added: block-proposed |
| tags: | removed: block-proposed |
| bugproxy (bugproxy) wrote Syslog for Entire Disk method | #5 |
| bugproxy (bugproxy) wrote Syslog for Encrypted LVM method | #6 |
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in partman-partitioning (Ubuntu): | |
| status: | In Progress → Fix Released |
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #8 |
Default Comment by Bridge