Fail to install the proposed grub-ieee1275 package (2.02~beta2-9)

Bug #1641567 reported by Po-Hsu Lin
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Expired
High
Unassigned
Trusty
Expired
High
Unassigned
Xenial
Expired
High
Unassigned
Yakkety
Won't Fix
High
Unassigned

Bug Description

When running dist-upgrade from 3.13.0-101 to 3.13.0-102 on a ppc64le system (proposed enabled), it will try to upgrade the grub-ieee1275 package. And it will fail with:

Setting up grub2-common (2.02~beta2-9ubuntu1.13) ...
Setting up grub-ieee1275-bin (2.02~beta2-9ubuntu1.13) ...
Setting up grub-ieee1275 (2.02~beta2-9ubuntu1.13) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC33900000000A0 failed: No such device or address
device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC3390000000020 failed: No such device or address
device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC33900000000C0 failed: No such device or address
device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC3390000000040 failed: No such device or address
device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC3390000000060 failed: No such device or address
Installing for powerpc-ieee1275 platform.
grub-install: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
dpkg: error processing package grub-ieee1275 (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up dmsetup (2:1.02.77-6ubuntu3) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
Processing triggers for initramfs-tools (0.103ubuntu4.4) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-102-generic
Errors were encountered while processing:
 grub-ieee1275
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: grub-ieee1275 2.02~beta2-9ubuntu1.13
ProcVersionSignature: User Name 3.13.0-101.148-generic 3.13.11-ckt39
Uname: Linux 3.13.0-101-generic ppc64le
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: ppc64el
Date: Mon Nov 14 09:59:49 2016
ProcLoadAvg: 0.09 0.11 0.06 1/1069 30236
ProcLocks:
 1: POSIX ADVISORY WRITE 3306 00:11:57402 0 EOF
 2: FLOCK ADVISORY WRITE 3224 00:11:66565 0 EOF
 3: POSIX ADVISORY WRITE 3163 00:11:57383 0 EOF
 4: POSIX ADVISORY WRITE 3299 00:11:64543 0 EOF
ProcSwaps:
 Filename Type Size Used Priority
 /swap.img file 8388544 0 -1
ProcVersion: Linux version 3.13.0-101-generic (buildd@bos01-ppc64el-026) (gcc version 4.8.4 (User Name 4.8.4-2ubuntu1~14.04.3) ) #148-User Name SMP Thu Oct 20 22:07:50 UTC 2016
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)
cpu_cores: Number of cores present = 20
cpu_coreson: Number of cores online = 20
cpu_smt: SMT=8

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

> device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC3390000000060 failed: No such device or address
> Installing for powerpc-ieee1275 platform.
> grub-install: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.

This is unlikely to be a bug introduced by the latest SRU, since there were no POWER-related changes in that version of grub. However, if there is a latent problem on some ppc64el installs which means that *any* upgrade of grub will trigger an upgrade failure, that's something we should assess as part of the SRU.

Changed in grub2 (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Changed in grub2 (Ubuntu Trusty):
status: New → In Progress
Changed in grub2 (Ubuntu Xenial):
status: New → In Progress
Changed in grub2 (Ubuntu Yakkety):
status: New → In Progress
Changed in grub2 (Ubuntu Trusty):
importance: Undecided → High
Changed in grub2 (Ubuntu Xenial):
importance: Undecided → High
Changed in grub2 (Ubuntu Yakkety):
importance: Undecided → High
tags: added: bot-stop-nagging
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

For the record,

I can see this issue with Trusty upgrading from 3.13.0-125 to 3.13.0-126.

This issue cannot be reproduced in other releases. Only specific to Trusty.

Setting up grub-ieee1275-bin (2.02~beta2-9ubuntu1.14) ...
Setting up grub-ieee1275 (2.02~beta2-9ubuntu1.14) ...
device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC33900000000A0 failed: No such device or address
device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC33900000000C0 failed: No such device or address
device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC3390000000020 failed: No such device or address
device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC3390000000040 failed: No such device or address
device-mapper: deps ioctl on 1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC3390000000060 failed: No such device or address
Installing for powerpc-ieee1275 platform.
grub-install: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
dpkg: error processing package grub-ieee1275 (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up linux-image-extra-3.13.0-126-generic (3.13.0-126.175) ...

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue can be found on 4.4.0-93.116~14.04.1 as well.

Po-Hsu Lin (cypressyew)
Changed in grub2 (Ubuntu Yakkety):
status: In Progress → Won't Fix
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue just happened again, bug 1792948

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This is a transient bug (as per bug 1792948, rebooting the system appears to let it work). I think this would put in pretty clearly as not a grub bug, but rather some issue with firmware/ kernel, or even multipath-tools. Reassigning to multipath-tools; but I'm setting it to Incomplete: either we'll get a new report that it failed again, or this bug can expire.

I have been unable to reproduce this issue in testing at all.

Changed in grub2 (Ubuntu):
assignee: Mathieu Trudel-Lapierre (cyphermox) → nobody
status: In Progress → Incomplete
Changed in grub2 (Ubuntu Trusty):
status: In Progress → Incomplete
Changed in grub2 (Ubuntu Xenial):
status: In Progress → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]

Changed in grub2 (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for grub2 (Ubuntu Xenial) because there has been no activity for 60 days.]

Changed in grub2 (Ubuntu Xenial):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for grub2 (Ubuntu Trusty) because there has been no activity for 60 days.]

Changed in grub2 (Ubuntu Trusty):
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.