package linux-image-2.6.32-24-generic 2.6.32-24.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[William Berzoff]

????

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-generic 2.6.32-24.39
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SIS966'/'HDA SIS966 at 0xfddf4000 irq 18'
   Mixer name : 'Realtek ALC660-VD'
   Components : 'HDA:10ec0660,1631c10b,00100001'
   Controls : 11
   Simple ctrls : 8
Card1.Amixer.info:
 Card hw:1 'default'/'Microsoft LifeChat LX-3000 at usb-0000:00:03.0-3, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB045e:070f'
   Controls : 7
   Simple ctrls : 3
Date: Wed Aug 18 17:06:22 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 2
Frequency: This has only happened once.
LiveMediaBuild: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
MachineType: Packard Bell BV EasyNote_MX37-U-023
ProcCmdLine: locale=us_us bootkbd=us console-setup/layoutcode=en_US console-setup/variantcode=nodeadkeys noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/xhostname.seed boot=casper initrd=/casper/initrd.lz splash-- BOOT_IMAGE=/casper/vmlinuz
RelatedPackageVersions: linux-firmware 1.34.1
SourcePackage: linux
Title: package linux-image-2.6.32-24-generic 2.6.32-24.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
dmi.bios.date: 02/29/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: T12C
dmi.board.vendor: PACKARD BELL BV
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: PACKARD BELL BV
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr214:bd02/29/2008:svnPackardBellBV:pnEasyNote_MX37-U-023:pvrPC10E01786:rvnPACKARDBELLBV:rnT12C:rvr1.0:cvnPACKARDBELLBV:ct10:cvr:
dmi.product.name: EasyNote_MX37-U-023
dmi.product.version: PC10E01786
dmi.sys.vendor: Packard Bell BV

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error caused by a corrupted archive. Please execute the following commands, as it will clear your package cache, in a terminal ( Applications -> Accessories -> Terminal ) :

sudo apt-get clean
sudo apt-get update

Then try performing the update again. This will likely resolve your issue. If so please set the bug's status to Invalid. Thanks in advance!

The failure appears to have started at this point in the DpkgTerminalLog.txt :

Setting up grub-pc (1.98-1ubuntu7) ...
grub-probe: error: cannot find a device for / (is /dev mounted?).
grub-probe: error: cannot find a device for /boot (is /dev mounted?).
grub-probe: error: cannot find a device for /boot/grub (is /dev mounted?).
/usr/sbin/grub-probe: error: cannot find a device for /boot/grub (is /dev mounted?).
No path or device is specified.
Try `/usr/sbin/grub-probe --help' for more information.
Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.

Setting up linux-image-2.6.32-24-generic (2.6.32-24.39) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.32-24-generic
gzip: /initrd.img.gz: No such file or directory
cp: cannot stat `/vmlinuz': No such file or directory
Failed to create initrd image.
dpkg: error processing linux-image-2.6.32-24-generic (--configure):
 subprocess installed post-installation script returned error exit status 2

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 557023, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.