kernel-image-2.6.8-1-686: unable to install kernel image because of failure with mkinitrd

[Debian Bug Importer]

Automatically imported from Debian bug report #266540 http://bugs.debian.org/266540

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #266540 http://bugs.debian.org/266540

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 18 Aug 2004 10:28:13 +0200
From: Igor Genibel <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: kernel-image-2.6.8-1-686: unable to install kernel image because of failure
 with mkinitrd

Package: kernel-image-2.6.8-1-686
Version: 2.6.8-1
Severity: grave
Justification: renders package unusable

Hi all,

here is the report:
root@tass:~ ->dpkg --configure -a
Setting up kernel-image-2.6.8-1-686 (2.6.8-1) ...
Unknown DM device 254:0
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.8-1-686 (--configure):
 subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
 kernel-image-2.6.8-1-686

The package is uninstallable that's why I put this severity.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro

Versions of packages kernel-image-2.6.8-1-686 depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii initrd-tools 0.1.73 tools to create initrd image for p
ii module-init-tools 3.1-pre5-3 tools for managing Linux kernel mo

-- no debconf information

[Matt Zimmerman (mdz)]

2.6.8 isn't in Warty yet

[terpstra (wesley-terpstra)]

Oh, btw the release critical bug #266540 which is holding up
kernel-image-2.6.8-1-686 from testing is caused b/c this patch is not
applied.

On Sun, Aug 29, 2004 at 03:16:00PM +0200, Wesley W. Terpstra wrote:
> Hello, bug #247054 has been open forever.
>
> The previous maintainer and I had prepared it some time ago, and it really
> should be applied. It was labelled wishlist when it was first opened because
> it was experimental. However, many people are now manually patching their
> mkinitrd because the patch is still not merged. This patch has been tested
> by many people since then, and has proven to be quite stable.
>
> This is becoming critical, because without the patch, every upgrade of
> mkinitrd and the kernel renders the system unbootable! (for people using
> cryptoroot) This just happened to me, ... again.
>
> Also, there is a regression in the lvm handling which Herbert Xu fixed
> months ago. It now again spews error messages during vgchange. They are
> non-fatal, but extremely amature looking.
>
> What is going on?
>
> --
> Wesley W. Terpstra

--
Wesley W. Terpstra

[terpstra (wesley-terpstra)]

Actually I'm not certain about #266540.

Certainly #266591 is caused by it though.

Possibly also #264339.

On Sun, Aug 29, 2004 at 03:26:24PM +0200, Wesley W. Terpstra wrote:
> Oh, btw the release critical bug #266540 which is holding up
> kernel-image-2.6.8-1-686 from testing is caused b/c this patch is not
> applied.
>
> On Sun, Aug 29, 2004 at 03:16:00PM +0200, Wesley W. Terpstra wrote:
> > Hello, bug #247054 has been open forever.

--
Wesley W. Terpstra

[Martin Michlmayr (tbm)]

reassign 266540 initrd-tools
severity 266540 important
thanks

* Igor Genibel <email address hidden> [2004-08-18 10:28]:
> root@tass:~ ->dpkg --configure -a
> Setting up kernel-image-2.6.8-1-686 (2.6.8-1) ...
> Unknown DM device 254:0

Is this in a chroot where the real system uses LVM?

Or otherwise, what are your partitions (especially) root on (df -h,
mount) and what does /proc/partitions say?
--
Martin Michlmayr
<email address hidden>

[Debian Bug Importer (debzilla)]

Message-ID: <20040829132621.GA11068@muffin>
Date: Sun, 29 Aug 2004 15:26:24 +0200
From: "Wesley W. Terpstra" <email address hidden>
To: Debian kernel team <email address hidden>
Cc: <email address hidden>
Subject: Re: Please apply the crypto patch!

Oh, btw the release critical bug #266540 which is holding up
kernel-image-2.6.8-1-686 from testing is caused b/c this patch is not
applied.

On Sun, Aug 29, 2004 at 03:16:00PM +0200, Wesley W. Terpstra wrote:
> Hello, bug #247054 has been open forever.
>
> The previous maintainer and I had prepared it some time ago, and it really
> should be applied. It was labelled wishlist when it was first opened because
> it was experimental. However, many people are now manually patching their
> mkinitrd because the patch is still not merged. This patch has been tested
> by many people since then, and has proven to be quite stable.
>
> This is becoming critical, because without the patch, every upgrade of
> mkinitrd and the kernel renders the system unbootable! (for people using
> cryptoroot) This just happened to me, ... again.
>
> Also, there is a regression in the lvm handling which Herbert Xu fixed
> months ago. It now again spews error messages during vgchange. They are
> non-fatal, but extremely amature looking.
>
> What is going on?
>
> --
> Wesley W. Terpstra

--
Wesley W. Terpstra

[Debian Bug Importer (debzilla)]

Message-ID: <20040829133232.GB11068@muffin>
Date: Sun, 29 Aug 2004 15:32:34 +0200
From: "Wesley W. Terpstra" <email address hidden>
To: Debian kernel team <email address hidden>
Cc: <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: Re: Please apply the crypto patch!

Actually I'm not certain about #266540.

Certainly #266591 is caused by it though.

Possibly also #264339.

On Sun, Aug 29, 2004 at 03:26:24PM +0200, Wesley W. Terpstra wrote:
> Oh, btw the release critical bug #266540 which is holding up
> kernel-image-2.6.8-1-686 from testing is caused b/c this patch is not
> applied.
>
> On Sun, Aug 29, 2004 at 03:16:00PM +0200, Wesley W. Terpstra wrote:
> > Hello, bug #247054 has been open forever.

--
Wesley W. Terpstra

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 29 Aug 2004 15:14:45 +0100
From: Martin Michlmayr <email address hidden>
To: Igor Genibel <email address hidden>
Cc: Debian Bug Tracking System <email address hidden>
Subject: Re: kernel-image-2.6.8-1-686: unable to install kernel image because of failure with
 mkinitrd

reassign 266540 initrd-tools
severity 266540 important
thanks

* Igor Genibel <email address hidden> [2004-08-18 10:28]:
> root@tass:~ ->dpkg --configure -a
> Setting up kernel-image-2.6.8-1-686 (2.6.8-1) ...
> Unknown DM device 254:0

Is this in a chroot where the real system uses LVM?

Or otherwise, what are your partitions (especially) root on (df -h,
mount) and what does /proc/partitions say?
--
Martin Michlmayr
<email address hidden>

[Igor Genibel (igenibel)]

On Sunday 29 August 2004 16:14, Martin Michlmayr wrote:
> * Igor Genibel <email address hidden> [2004-08-18 10:28]:
> > root@tass:~ ->dpkg --configure -a
> > Setting up kernel-image-2.6.8-1-686 (2.6.8-1) ...
> > Unknown DM device 254:0
>
> Is this in a chroot where the real system uses LVM?

No this is not a chroot

> Or otherwise, what are your partitions (especially) root on (df -h,
> mount) and what does /proc/partitions say?

igor@tass:~ ->cat /proc/partitions
major minor #blocks name

   3 0 19535040 hda
   3 1 5855661 hda1
   3 2 498015 hda2
   3 3 13181332 hda3
 254 0 498015 dm-0

igor@tass:~ ->mount
/dev/hda3 on / type ext3 (rw,errors=remount-ro,acl,commit=0)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda1 on /org type ext3 (rw,acl,commit=0)
usbfs on /proc/bus/usb type usbfs (rw)

--
Igor Genibel
«Non bene pro toto libertas venditur auro»
Freedom is not sold for all the gold in the world.
Dubrovnik motto

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sat, 4 Sep 2004 10:29:43 +0200
From: Igor Genibel <email address hidden>
To: Martin Michlmayr <email address hidden>
Cc: Debian Bug Tracking System <email address hidden>
Subject: Re: kernel-image-2.6.8-1-686: unable to install kernel image because of failure with
 mkinitrd

--Boundary-02=_J7XOBj/khUC7XmX
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 29 August 2004 16:14, Martin Michlmayr wrote:
> * Igor Genibel <email address hidden> [2004-08-18 10:28]:
> > root@tass:~ ->dpkg --configure -a
> > Setting up kernel-image-2.6.8-1-686 (2.6.8-1) ...
> > Unknown DM device 254:0
>
> Is this in a chroot where the real system uses LVM?

No this is not a chroot

> Or otherwise, what are your partitions (especially) root on (df -h,
> mount) and what does /proc/partitions say?

igor@tass:~ ->cat /proc/partitions
major minor #blocks name

   3 0 19535040 hda
   3 1 5855661 hda1
   3 2 498015 hda2
   3 3 13181332 hda3
 254 0 498015 dm-0

igor@tass:~ ->mount
/dev/hda3 on / type ext3 (rw,errors=3Dremount-ro,acl,commit=3D0)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=3D5,mode=3D620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda1 on /org type ext3 (rw,acl,commit=3D0)
usbfs on /proc/bus/usb type usbfs (rw)

=2D-=20
Igor Genibel
=ABNon bene pro toto libertas venditur auro=BB
=46reedom is not sold for all the gold in the world.
Dubrovnik motto

--Boundary-02=_J7XOBj/khUC7XmX
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBOX7J+xgdMBZI9sgRAnodAJ4q5crbFIQH9jmpzabD4m7ajffk4ACfR6T8
iviwlF/7nYMXVZTjTE1vFwQ=
=gRwI
-----END PGP SIGNATURE-----

--Boundary-02=_J7XOBj/khUC7XmX--

[Maks Attems (debian-sternwelten)]

tags 266540 moreinfo
thanks

On Wed, 18 Aug 2004, Igor Genibel wrote:

> Hi all,
>
> here is the report:
> root@tass:~ ->dpkg --configure -a
> Setting up kernel-image-2.6.8-1-686 (2.6.8-1) ...
> Unknown DM device 254:0
> Failed to create initrd image.
> dpkg: error processing kernel-image-2.6.8-1-686 (--configure):
> subprocess post-installation script returned error exit status 9
> Errors were encountered while processing:
> kernel-image-2.6.8-1-686
>
> The package is uninstallable that's why I put this severity.
>

does this pain still subsist?
described bug should have been fixed in initrd-tools (0.1.76).

can you please confirm?

--
maks

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 28 Apr 2005 10:40:46 +0200
From: maximilian attems <email address hidden>
To: Igor Genibel <email address hidden>, <email address hidden>
Subject: Re: Bug#266540: kernel-image-2.6.8-1-686: unable to install kernel image because of failure
 with mkinitrd

tags 266540 moreinfo
thanks

On Wed, 18 Aug 2004, Igor Genibel wrote:

> Hi all,
>
> here is the report:
> root@tass:~ ->dpkg --configure -a
> Setting up kernel-image-2.6.8-1-686 (2.6.8-1) ...
> Unknown DM device 254:0
> Failed to create initrd image.
> dpkg: error processing kernel-image-2.6.8-1-686 (--configure):
> subprocess post-installation script returned error exit status 9
> Errors were encountered while processing:
> kernel-image-2.6.8-1-686
>
> The package is uninstallable that's why I put this severity.
>

does this pain still subsist?
described bug should have been fixed in initrd-tools (0.1.76).

can you please confirm?

--
maks

[maximilian attems (maks-debian)]

Version: 0.1.76

On Thu, 28 Apr 2005, maximilian attems wrote:

> tags 266540 moreinfo
> thanks

that is some time back without feedback.

> > kernel-image-2.6.8-1-686
> >
> > The package is uninstallable that's why I put this severity.
> >
>
> does this pain still subsist?
> described bug should have been fixed in initrd-tools (0.1.76).

closing with that version info.

--
maks