[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#544461: marked as done (linux-image-2.6.30-1-486: kernel failed to start : raid45: unknown target type)

Your message dated Sat, 13 Feb 2010 12:04:52 +0100
with message-id <20100213110452.GK2821@stro.at>
and subject line Re: Bug#544461: linux-image-2.6.30-1-486: kernel failed to start : raid45: unknown target type
has caused the Debian Bug report #544461,
regarding linux-image-2.6.30-1-486: kernel failed to start : raid45: unknown target type
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
544461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544461
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.30-1-486
Version: 2.6.30-6
Severity: critical
Justification: breaks the whole system

Hi,  I wasn't able to get full log because I had to restart my computer
with Ctl-Alt-Del.

I still available for test purposes.

Best regards,
Franck.

-- Package-specific info:

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-486
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6.30-1-486 depends on:
ii  debconf [debconf-2.0]         1.5.27     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93.4     tools for generating an initramfs
ii  module-init-tools             3.9-2      tools for managing Linux kernel mo

linux-image-2.6.30-1-486 recommends no packages.

Versions of packages linux-image-2.6.30-1-486 suggests:
ii  grub                          0.97-56    GRand Unified Bootloader (dummy pa
ii  grub-legacy [grub]            0.97-56    GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.30              <none>     (no description available)

-- debconf information:
  linux-image-2.6.30-1-486/preinst/failed-to-move-modules-2.6.30-1-486:
  linux-image-2.6.30-1-486/preinst/elilo-initrd-2.6.30-1-486: true
  linux-image-2.6.30-1-486/preinst/overwriting-modules-2.6.30-1-486: true
  linux-image-2.6.30-1-486/postinst/bootloader-test-error-2.6.30-1-486:
  linux-image-2.6.30-1-486/preinst/abort-install-2.6.30-1-486:
  linux-image-2.6.30-1-486/preinst/lilo-has-ramdisk:
  linux-image-2.6.30-1-486/postinst/old-dir-initrd-link-2.6.30-1-486: true
  linux-image-2.6.30-1-486/postinst/depmod-error-2.6.30-1-486: false
  linux-image-2.6.30-1-486/postinst/old-initrd-link-2.6.30-1-486: true
  linux-image-2.6.30-1-486/preinst/initrd-2.6.30-1-486:
  linux-image-2.6.30-1-486/preinst/abort-overwrite-2.6.30-1-486:
  linux-image-2.6.30-1-486/prerm/would-invalidate-boot-loader-2.6.30-1-486: true
  linux-image-2.6.30-1-486/preinst/bootloader-initrd-2.6.30-1-486: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.30-1-486/postinst/depmod-error-initrd-2.6.30-1-486: false
  linux-image-2.6.30-1-486/postinst/kimage-is-a-directory:
  linux-image-2.6.30-1-486/postinst/create-kimage-link-2.6.30-1-486: true
  linux-image-2.6.30-1-486/postinst/old-system-map-link-2.6.30-1-486: true
  linux-image-2.6.30-1-486/preinst/lilo-initrd-2.6.30-1-486: true
  linux-image-2.6.30-1-486/prerm/removing-running-kernel-2.6.30-1-486: true
  linux-image-2.6.30-1-486/postinst/bootloader-error-2.6.30-1-486:

--- End Message ---
--- Begin Message --- 
On Tue, 06 Oct 2009, Ben Hutchings wrote:

> Please don't just mail me; keep 544461@bugs.debian.org in the Cc line.
> 
> On Mon, 2009-10-05 at 21:24 +0200, Franck wrote:
> > Hi,
> > 
> >   It seems to be corrected with the last dmraid module update.
> 
> What do you mean by that?  The log shows the same kernel version as you
> originally reported.

closing as no more follow-up. bug assumed fixed.

if you can reproduce with latest 2.6.32 then please shout.
thanks for your report.

--- End Message ---
Reply to: