package memtest86+ 1.70-2ubuntu2 failed to install/upgrade: Package is in a very bad inconsistent state - you should

Bug #129614 reported by Brian J. Murrell
50
This bug affects 5 people
Affects Status Importance Assigned to Milestone
memtest86+ (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: memtest86+

fails to install when /boot/grub is present i.e. grub not installed.

ProblemType: Package
Architecture: i386
Date: Wed Aug 1 01:01:33 2007
Dependencies:

DistroRelease: Ubuntu 7.10
ErrorMessage: Package is in a very bad inconsistent state - you should
NonfreeKernelModules: nvidia vmnet vmmon via82cxxx
Package: memtest86+ 1.70-2ubuntu2
PackageArchitecture: i386
SourcePackage: memtest86+
Title: package memtest86+ 1.70-2ubuntu2 failed to install/upgrade: Package is in a very bad inconsistent state - you should
Uname: Linux pc 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux

Related branches

Revision history for this message
Elliot Murphy (statik) wrote :

I'm experiencing this bug on an amd64 machine running gutsy:
emurphy@scared@:~/src/bzr-webserve/docs>sudo apt-get install memtest86+
[sudo] password for emurphy:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  hwtools kernel-patch-badram mtools
The following packages will be upgraded:
  memtest86+
1 upgraded, 0 newly installed, 0 to remove and 120 not upgraded.
2 not fully installed or removed.
Need to get 0B/65.1kB of archives.
After unpacking 0B of additional disk space will be used.
(Reading database ... 474534 files and directories currently installed.)
Preparing to replace memtest86+ 1.70-2ubuntu1 (using .../memtest86+_1.70-2ubuntu2_amd64.deb) ...
Unpacking replacement memtest86+ ...
Searching for GRUB installation directory ...
No GRUB directory found. To create a template run 'mkdir /boot/grub' first. To install grub, install it manually or try the 'grub-install' command. ### Warning, grub-install is used to change your MBR. ###

dpkg: warning - old post-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
Searching for GRUB installation directory ...
No GRUB directory found. To create a template run 'mkdir /boot/grub' first. To install grub, install it manually or try the 'grub-install' command. ### Warning, grub-install is used to change your MBR. ###

dpkg: error processing /var/cache/apt/archives/memtest86+_1.70-2ubuntu2_amd64.deb (--unpack):
 subprocess new post-removal script returned error exit status 1
Searching for GRUB installation directory ...
No GRUB directory found. To create a template run 'mkdir /boot/grub' first. To install grub, install it manually or try the 'grub-install' command. ### Warning, grub-install is used to change your MBR. ###

dpkg: error while cleaning up:
 subprocess post-removal script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/memtest86+_1.70-2ubuntu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
Elliot Murphy (statik) wrote :

After looking at this further, I don't know that this is actually a problem with memtest86+. My system seems to be in sad shape, and grub is mysteriously not installed. I was able to 'sudo mkdir /boot/grub', then reinstall memtest86+, and answered yes to the prompts about installing grub. Now I'm installing the rest of the updates that had been blocked, and hopefully the system will be able to reboot.

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote : Re: [Bug 129614] Re: package memtest86+ 1.70-2ubuntu2 failed to install/upgrade: Package is in a very bad inconsistent state - you should

On Wed, 2007-08-01 at 15:01 +0000, Elliot Murphy wrote:
> After looking at this further, I don't know that this is actually a
> problem with memtest86+.

It is.

> My system seems to be in sad shape, and grub is
> mysteriously not installed.

I don't have grub installed either, but that was a conscious decision on
my part. I use lilo.

> I was able to 'sudo mkdir /boot/grub', then
> reinstall memtest86+, and answered yes to the prompts about installing
> grub.

Indeed, so was I. But we should not have had to do that.

b.

--
My other computer is your Microsoft Windows server.

Brian J. Murrell

Revision history for this message
Achim Bohnet (allee) wrote :

Same error msg on a system installed with FAI 3.2.1. memtest86+ is installed before
grub and therefore memtest86+ postinst fails, because there no /boot/grub directory.

memtest86 in debian tests for /boot/grub/grub.cfg before running update-grub,
but this file seem to be a new feature of grub, not used/available on (k)ubuntu/Gutsy
beta

   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425221

Revision history for this message
Reinhard Tartler (siretart) wrote :

memtest86+ (1.70-3ubuntu1) gutsy; urgency=low

  * Merge from debian unstable, remaining changes:
    - debian/control: Add lpia as supported architecture.
    - Makefile: Add -fno-stack-protector to CFLAGS, since this package does
      not link against libc.
  * Check for /boot/grub/menu.lst rather than /boot/grub/menu.lst in
    post{inst,rm}, LP: #129614

memtest86+ (1.70-3) unstable; urgency=low

  * Build-depend on gcc-multilib on amd64 (Closes: #426239).
  * Check for existence of /boot/grub/grub.cfg before running update-grub
    (Closes: #425221).
  * Take into account in make-memtest86+-boot-floppy path changes in
    grub-legacy (Justin B Rye, Closes: #412255). Does not support grub2,
    however.

 -- Reinhard Tartler <email address hidden> Wed, 26 Sep 2007 22:43:24 +0200

Changed in memtest86+:
status: New → Fix Released
Revision history for this message
Shawn Peterson (shawnpeterson77) wrote :

My machine is stalling while trying to upgrade from 9.10 to 10.04 alpha 3. It is getting stuck on the memtest86+. It is via wubi, so I have tried a couple of times, and same result.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.