Ubuntu
grub2 package

package grub-pc 1.99~rc1-4ubuntu1 failed to install/upgrade: underprocess installerade post-installation-skript gav felkod 1

Bug #736480 reported by Gustaf on 2011-03-16

This bug report is a duplicate of: Bug #495123: grub-probe: error: not a directory. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	grub2 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: grub2

Couldn't install grub to either /dev/sda nor /dev/sda1 after last update although grub is previously installed. This is a pretty default ubuntu although with a kernel from the kernel-ppa

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: grub-pc 1.99~rc1-4ubuntu1
Uname: Linux 2.6.38-020638rc8-generic x86_64
Architecture: amd64
Date: Wed Mar 16 23:40:44 2011
ErrorMessage: underprocess installerade post-installation-skript gav felkod 1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-020638rc8-generic root=UUID=3a5e9aae-075e-4be9-9ae2-f856bb1835c5 ro vga=769 quiet splash vt.handoff=7
SourcePackage: grub2
Title: package grub-pc 1.99~rc1-4ubuntu1 failed to install/upgrade: underprocess installerade post-installation-skript gav felkod 1
UpgradeStatus: Upgraded to natty on 2011-03-13 (3 days ago)

Tags:

Revision history for this message

Gustaf (g-rantila) wrote on 2011-03-16:

AptOrdering.txt Edit (9.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Df.txt Edit (474 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (74.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (28.5 KiB, text/plain; charset="utf-8")
EtcDefaultGrub.txt Edit (1.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-06-22:

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 495123, 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.