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

Bug#551733: marked as done (linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686)

Your message dated Thu, 8 Apr 2010 21:11:59 +0200
with message-id <20100408191159.GN6427@baikonur.stro.at>
and subject line Re: Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
has caused the Debian Bug report #551733,
regarding linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
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.)


-- 
551733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551733
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.26-2-686
Version: 2.6.26-19
Severity: important

Kernel image 2.6.26-1-686 is no problem. 2.6.26-2-686 drops me to a shell titled (initramfs) shortly after issuing the message:
 "Booting the kernel."
It never gets to "Loading, please wait ..."

Before I get control there are a (large) number of screen messages of the form:
 /init: line1:  /bin/sleep:  not found
and then
 "Gave up waiting for root device"
and
 "ALERT! /dev/disk/by-label/D5root does not exist. Dropping to a shell!

At this stage, looking at the filesystem available in initramfs:
 there is no /dev/disk/ directory although /dev exists,
 /proc/modules contains only thermal_sys, fan, processor, and thermal,
 /lib/modules/2.6.26-2-686/ appears well-populated,
 /sbin contains only 7 files  (depmod, modprobe, resume, rmmod, udevadm, udevd, udevsettle),
 /bin/sleep exists so the multiple /init errors are not looking for /bin/sleep.

I am using GRUB (legacy) and root=LABEL statements identical to the ones which boot 2.6.26-1-686 without any problem. I have regenerated the initrd-img a number of times to no effect.


-- Package-specific info:

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

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-2-686 depends on:
ii  debconf [debconf-2.0]         1.5.26     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93.2     tools for generating an initramfs
ii  module-init-tools             3.7-pre9-1 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.26-2-686 recommends:
ii  libc6-i686                    2.7-18     GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.26-2-686 suggests:
ii  grub                       0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.26           <none>        (no description available)

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

--- End Message ---
--- Begin Message --- 
On Thu, Apr 08, 2010 at 09:10:59PM +1200, Bruce Ward wrote:
> 
> I would be quite happy for you to close this bug now. We know it was 
> something to do with my environment and no others, and I intend to 
> reinstall with 5.04 soon.
> 
> I really appreciate the effort that has been made to solve this problem 
> but I am sure there are more pressing matters.
> 
> Many thanks, Bruce

thanks for the feedback. if you ever can reproduce, please shout
we can reopen and see to nail it down.

closing as suggested.

sunny greetings.

--- End Message ---
Reply to: