package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to install/upgrade: exit status 17 - Failed to symbolic-link boot/initrd.img-2.6.31-20-generic to initrd.img: File exists

Bug #540620 reported by franklin
126
This bug affects 14 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

I had previously created a new kernel. I suspect that the existence of my customized kernel may be the problem. I created this custom kernel to accomodate VMware Server v1.0.10 which did not run on Ubuntu 9.10 without this customized kernel. Details of what I did can be followed from the how-to at URL: <http://www.howtoforge.com/how-to-install-vmware-server-1.0.x-on-an-ubuntu-9.10-desktop> which I followed exactly.

ProblemType: Package
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: franklin 1498 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with AD1980 at irq 23'
   Mixer name : 'Analog Devices AD1980'
   Components : 'AC97a:41445370'
   Controls : 40
   Simple ctrls : 29
Date: Wed Mar 17 09:13:28 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 17
HibernationDevice: RESUME=UUID=a24e2c37-2a80-47d0-9738-26e37ccee30d
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Dell Inc. Dimension 4700
NonfreeKernelModules: vmnet vmmon
Package: linux-image-2.6.31-20-generic 2.6.31-20.58
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31.9custom root=UUID=187aa622-41dd-4a35-8bb7-91aa133388c2 ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
RelatedPackageVersions: linux-firmware 1.26
RfKill:

SourcePackage: linux
Title: package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
Uname: Linux 2.6.31.9custom i686
dmi.bios.date: 11/23/2004
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0M3918
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/23/2004:svnDellInc.:pnDimension4700:pvr:rvnDellInc.:rn0M3918:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: Dimension 4700
dmi.sys.vendor: Dell Inc.

Revision history for this message
franklin (franklin-degraaf) wrote :
tags: added: karmic
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report.

The relevant error is
---
Setting up linux-image-2.6.31-20-generic (2.6.31-20.58) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.31-20-generic
Failed to symbolic-link boot/initrd.img-2.6.31-20-generic to initrd.img: File exists
dpkg: error processing linux-image-2.6.31-20-generic (--configure):
 subprocess installed post-installation script returned error exit status 17

It is probably because you used the same name for your custom kernel than the official one. When you create a custom kernel it is recommended to use a custom extension to avoid conflicts between packages.

I'm closing this report because it is not a bug with Ubuntu. Don't hesitate to reopen if you're still experiencing this issue after (re)moving your custom package.

Thanks.

Changed in linux (Ubuntu):
status: New → Invalid
Revision history for this message
franklin (franklin-degraaf) wrote : Re: [Bug 540620] Re: package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
Download full text (4.2 KiB)

The custom kernel that I built does have a different name and should in
itself not be in conflict. I have attached logs with my original bug report.
From that you could see what name I have given the kernel and why simply the
kernel does not account for this problem.

On Thu, Mar 18, 2010 at 6:45 AM, Jean-Baptiste Lallement <
<email address hidden>> wrote:

> Thanks for your report.
>
> The relevant error is
> ---
> Setting up linux-image-2.6.31-20-generic (2.6.31-20.58) ...
> Running depmod.
> update-initramfs: Generating /boot/initrd.img-2.6.31-20-generic
> Failed to symbolic-link boot/initrd.img-2.6.31-20-generic to initrd.img:
> File exists
> dpkg: error processing linux-image-2.6.31-20-generic (--configure):
> subprocess installed post-installation script returned error exit status
> 17
>
> It is probably because you used the same name for your custom kernel
> than the official one. When you create a custom kernel it is recommended
> to use a custom extension to avoid conflicts between packages.
>
> I'm closing this report because it is not a bug with Ubuntu. Don't
> hesitate to reopen if you're still experiencing this issue after
> (re)moving your custom package.
>
> Thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Invalid
>
> --
> package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to
> install/upgrade: subprocess installed post-installation script returned
> error exit status 17
> https://bugs.launchpad.net/bugs/540620
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Invalid
>
> Bug description:
> package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to
> install/upgrade: subprocess installed post-installation script returned
> error exit status 17
>
> I had previously created a new kernel. I suspect that the existence of my
> customized kernel may be the problem. I created this custom kernel to
> accomodate VMware Server v1.0.10 which did not run on Ubuntu 9.10 without
> this customized kernel. Details of what I did can be followed from the
> how-to at URL: <
> http://www.howtoforge.com/how-to-install-vmware-server-1.0.x-on-an-ubuntu-9.10-desktop>
> which I followed exactly.
>
> ProblemType: Package
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: franklin 1498 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'ICH6'/'Intel ICH6 with AD1980 at irq 23'
> Mixer name : 'Analog Devices AD1980'
> Components : 'AC97a:41445370'
> Controls : 40
> Simple ctrls : 29
> Date: Wed Mar 17 09:13:28 2010
> DistroRelease: Ubuntu 9.10
> ErrorMessage: subprocess installed post-installation script returned error
> exit status 17
> HibernationDevice: RESUME=UUID=a24e2c37-2a80-47d0-9738-26e37ccee30d
> InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
> IwConfig:
> lo no wireless extensions.
>
> eth0 no wireless extensions.
> MachineType: Dell Inc. Dimension 4700
> NonfreeKernelModules: vmnet vmmon
> Package: linux-image-2.6.31-20-generic 2.6.31-20.58
> ProcCmdLine: BOOT_IMAGE=/vmlinu...

Read more...

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote : Re: package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

reopening for further investigation.

Changed in linux (Ubuntu):
status: Invalid → New
summary: package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to
- install/upgrade: subprocess installed post-installation script returned
- error exit status 17
+ install/upgrade: exit status 17 - Failed to symbolic-link
+ boot/initrd.img-2.6.31-20-generic to initrd.img: File exists
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

confirmed by duplicate case.

Changed in linux (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
GrahamT (graham-travis) wrote :

As the duplicate case reporter, I would like to confirm that I do not have a custom kernel and have no VMware currently installed on this Acer Aspire laptop.

Revision history for this message
GrahamT (graham-travis) wrote :

In addition I am running Lucid Beta 1, whereas this is tagged Karmic. Beta installation was OK. Error appeared when updating packages 2 days later.

tags: added: lucid
removed: karmic
Revision history for this message
沈欢 (shenhuan007) wrote :

Error appeared when updating packages 1 week later

Revision history for this message
George H Finn (ghfinn) wrote :

Is there a layman's description to dealing with this issue, such as not having to do some coding and recompiling to get this system installed?

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
George H Finn (ghfinn) wrote : Re: [Bug 540620] Re: package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to install/upgrade: exit status 17 - Failed to symbolic-link boot/initrd.img-2.6.31-20-generic to initrd.img: File exists
Download full text (3.6 KiB)

At this rate maybe I'll try again when I hit 70, I gave up on this OS 8
month's ago.

On Fri, Jul 15, 2011 at 2:33 AM, Brad Figg <email address hidden> wrote:

> This bug was filed against a series that is no longer supported and so
> is being marked as Won't Fix. If this issue still exists in a supported
> series, please file a new bug.
>
> This change has been made by an automated script, maintained by the
> Ubuntu Kernel Team.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Won't Fix
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (668702).
> https://bugs.launchpad.net/bugs/540620
>
> Title:
> package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to
> install/upgrade: exit status 17 - Failed to symbolic-link
> boot/initrd.img-2.6.31-20-generic to initrd.img: File exists
>
> Status in “linux” package in Ubuntu:
> Won't Fix
>
> Bug description:
> package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to
> install/upgrade: subprocess installed post-installation script
> returned error exit status 17
>
> I had previously created a new kernel. I suspect that the existence of
> my customized kernel may be the problem. I created this custom kernel
> to accomodate VMware Server v1.0.10 which did not run on Ubuntu 9.10
> without this customized kernel. Details of what I did can be followed
> from the how-to at URL: <http://www.howtoforge.com/how-to-install-
> vmware-server-1.0.x-on-an-ubuntu-9.10-desktop> which I followed
> exactly.
>
> ProblemType: Package
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: franklin 1498 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'ICH6'/'Intel ICH6 with AD1980 at irq 23'
> Mixer name : 'Analog Devices AD1980'
> Components : 'AC97a:41445370'
> Controls : 40
> Simple ctrls : 29
> Date: Wed Mar 17 09:13:28 2010
> DistroRelease: Ubuntu 9.10
> ErrorMessage: subprocess installed post-installation script returned error
> exit status 17
> HibernationDevice: RESUME=UUID=a24e2c37-2a80-47d0-9738-26e37ccee30d
> InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
> IwConfig:
> lo no wireless extensions.
>
> eth0 no wireless extensions.
> MachineType: Dell Inc. Dimension 4700
> NonfreeKernelModules: vmnet vmmon
> Package: linux-image-2.6.31-20-generic 2.6.31-20.58
> ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31.9custom
> root=UUID=187aa622-41dd-4a35-8bb7-91aa133388c2 ro
> crashkernel=384M-2G:64M,2G-:128M quiet splash
> ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
> RelatedPackageVersions: linux-firmware 1.26
> RfKill:
>
> SourcePackage: linux
> Title: package linux-image-2.6.31-20-generic 2.6.31-20.58 failed to
> install/upgrade: subprocess installed post-installation script returned
> error exit status 17
> Uname: Linux 2.6.31.9custom i686
> dmi.bios.date: 11/23/2004
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: A05
> dmi.board.name: 0M3918
> dmi.board.vendor: Dell Inc.
> dmi.chassis.type: 6
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:...

Read more...

To post a comment you must log in.