package linux-image-3.19.0-32-generic 3.19.0-32.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 10

Bug #1510563 reported by deadking01
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
grub (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

update system .
the it pop a error

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-32-generic 3.19.0-32.37
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: wuqf 2086 F...m pulseaudio
 /dev/snd/controlC0: wuqf 2086 F.... pulseaudio
Date: Tue Oct 27 22:17:46 2015
DuplicateSignature: package:linux-image-3.19.0-32-generic:3.19.0-32.37:run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 10
ErrorMessage: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 10
HibernationDevice: RESUME=UUID=97273224-2cb9-4455-aa43-c024bdeb9b3e
InstallationDate: Installed on 2015-01-13 (286 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic.efi.signed root=UUID=7988b9e8-1129-4270-8b10-0863bce907c9 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
RfKill:

SourcePackage: grub
Title: package linux-image-3.19.0-32-generic 3.19.0-32.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 10
UpgradeStatus: Upgraded to vivid on 2015-04-24 (186 days ago)
dmi.bios.date: 06/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-D2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: B85M-D2V
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
deadking01 (wuqingfeng234) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel Convissor (convissor) wrote :

"apt-get dist-upgrade" hung for me with the /etc/kernel/postinst.d/zz-update-grub step. Here's the output of rerunning the upgrade:

dpkg --configure -a

Setting up linux-headers-3.19.0-32 (3.19.0-32.37~14.04.1) ...
Setting up linux-image-3.19.0-32-generic (3.19.0-32.37~14.04.1) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
initrd.img(/boot/initrd.img-3.19.0-32-generic
) points to /boot/initrd.img-3.19.0-32-generic
 (/boot/initrd.img-3.19.0-32-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-3.19.0-32-generic.postinst line 491.
vmlinuz(/boot/vmlinuz-3.19.0-32-generic
) points to /boot/vmlinuz-3.19.0-32-generic
 (/boot/vmlinuz-3.19.0-32-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-3.19.0-32-generic.postinst line 491.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.19.0-32-generic /boot/vmlinuz-3.19.0-32-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.19.0-32-generic /boot/vmlinuz-3.19.0-32-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-dkms.0.crash'
Error! Bad return status for module build on kernel: 3.19.0-32-generic (x86_64)
Consult /var/lib/dkms/virtualbox/4.3.10/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.19.0-32-generic /boot/vmlinuz-3.19.0-32-generic
update-initramfs: Generating /boot/initrd.img-3.19.0-32-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.19.0-32-generic /boot/vmlinuz-3.19.0-32-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.19.0-32-generic /boot/vmlinuz-3.19.0-32-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.19.0-32-generic /boot/vmlinuz-3.19.0-32-generic

At which point the terminal is locked up. Hitting CTRL+C does nothing.

Revision history for this message
Daniel Convissor (convissor) wrote :

In case it's related, here's the crash dump from the virtualbox error in my output, above.

Revision history for this message
Daniel Convissor (convissor) wrote :

The virtualbox-dkms crash is not related.

FYI, broke out of the hung upgrade process and recurring cycle this way:

CTRL+Z

kill -9 $(pgrep 'dpkg|apt-get')
rm /var/lib/dpkg/info/*3.19.0-32*
dpkg --configure -a

After that, I was able to uninstall virtualbox and dkms:

apt-get remove virtualbox dkms

Revision history for this message
Phillip Susi (psusi) wrote :

Please post the output of the following command:

apt-cache policy grub grub-pc grub-efi

Changed in grub (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Daniel Convissor (convissor) wrote :

apt-cache policy grub grub-pc grub-efi

grub:
  Installed: (none)
  Candidate: 0.97-29ubuntu66
  Version table:
     0.97-29ubuntu66 0
        500 http://mirror.pnl.gov/ubuntu/ trusty/main amd64 Packages

grub-pc:
  Installed: 2.02~beta2-9ubuntu1.3
  Candidate: 2.02~beta2-9ubuntu1.3
  Version table:
 *** 2.02~beta2-9ubuntu1.3 0
        500 http://mirror.pnl.gov/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.02~beta2-9 0
        500 http://mirror.pnl.gov/ubuntu/ trusty/main amd64 Packages

grub-efi:
  Installed: (none)
  Candidate: 2.02~beta2-9ubuntu1.3
  Version table:
     2.02~beta2-9ubuntu1.3 0
        500 http://mirror.pnl.gov/ubuntu/ trusty-updates/main amd64 Packages
     2.02~beta2-9 0
        500 http://mirror.pnl.gov/ubuntu/ trusty/main amd64 Packages

Changed in grub (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Phillip Susi (psusi) wrote :

Did you run this command on the same system? Because it says you are running trusty, yet your logs before said you were running vivid.

Changed in grub (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Daniel Convissor (convissor) wrote :

Looks like that was the original poster. I'm on straight up Trusty, installed about a month ago.

uname -a
Linux x250 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:21:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

grep VERSION= /etc/os-release
VERSION="14.04.3 LTS, Trusty Tahr"

Changed in grub (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Phillip Susi (psusi) wrote :

Ahh, we would need to see your logs to see if it is the same issue or not. Best to let it file your own bug report.

Changed in grub (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Daniel Convissor (convissor) wrote :

@psusi I posted some logs earlier. Which logs do you want? I put the stuff here rather than open a duplicate. Perhaps it's a separate issue, but it sure seems the same. (Famous last words. :)

Revision history for this message
Phillip Susi (psusi) wrote :

You posted a log of trying to compile virtualbox from source, which is entirely different from what this original bug report was about.

Revision history for this message
Daniel Convissor (convissor) wrote :

The virtualbox-dkms.0.crash attachment arose from a post install step while upgrading to the new kernel. (See the reference to /var/crash/virtualbox-dkms.0.crash in the output I posted.) I initially suspected a conflict with dkms was the source of the zz-update-grub hang. Turns out it's not.

Revision history for this message
Daniel Convissor (convissor) wrote :

FYI: unattended upgrade ran on my box a moment ago. It upgraded grub to 2.02~beta2-9ubuntu1.4 and kernel 3.19.0-33. Everything ran fine, including the zz-update-grub postinst.d step.

Revision history for this message
Daniel Convissor (convissor) wrote :

@deadking01: does upgrading to the latest code work for you too?

Revision history for this message
Daniel Convissor (convissor) wrote :

I just opened bug #1527645, which I suspect is related to this.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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