Your message dated Mon, 2 Mar 2009 23:12:00 +0100
with message-id <20090302221200.gc29...@stro.at>
and subject line Re: Bug#517473: linux-image-2.6.28-1-686 fails to boot, no
/dev/md0, no /dev/sd[ab]*
has caused the Debian Bug report #517473,
regarding linux-image-2.6.28-1-686 fails to boot, no /dev/md0, no /dev/sd[ab]*
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 ow...@bugs.debian.org
immediately.)
--
517473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.28-1-686
Version: 2.6.28-1
Severity: important
New 2.6.28 fails to boot as it finds no md0 (for root dev). mdadm
complains it is unable to assemble it. With the provided shell it is
clear sd[ab]* devices are missing at the point of boot sequence.
OTOH, /sys/bus/scsi/ shows the SCSI controller (aic79xx) and the two
disks. mdadm.conf in the initrd.img has the /dev/ paths and UUIDs to
identify the md devices, fstab uses /dev/md0 though. 2.6.26 boots
fine.
-- Package-specific info:
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.28-1-686 depends on:
ii debconf [debconf-2.0] 1.5.25 Debian configuration management sy
ii initramfs-tools [linux-initra 0.93 tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.28-1-686 recommends:
ii libc6-i686 2.9-3 GNU C Library: Shared libraries [i
Versions of packages linux-image-2.6.28-1-686 suggests:
ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v
ii linux-doc-2.6.28 2.6.28-1 Linux kernel specific documentatio
-- debconf information:
linux-image-2.6.28-1-686/postinst/old-system-map-link-2.6.28-1-686: true
linux-image-2.6.28-1-686/prerm/would-invalidate-boot-loader-2.6.28-1-686: true
linux-image-2.6.28-1-686/preinst/initrd-2.6.28-1-686:
linux-image-2.6.28-1-686/preinst/failed-to-move-modules-2.6.28-1-686:
linux-image-2.6.28-1-686/postinst/create-kimage-link-2.6.28-1-686: true
linux-image-2.6.28-1-686/preinst/elilo-initrd-2.6.28-1-686: true
linux-image-2.6.28-1-686/postinst/depmod-error-initrd-2.6.28-1-686: false
linux-image-2.6.28-1-686/postinst/old-dir-initrd-link-2.6.28-1-686: true
linux-image-2.6.28-1-686/preinst/lilo-has-ramdisk:
linux-image-2.6.28-1-686/postinst/depmod-error-2.6.28-1-686: false
linux-image-2.6.28-1-686/postinst/old-initrd-link-2.6.28-1-686: true
linux-image-2.6.28-1-686/prerm/removing-running-kernel-2.6.28-1-686: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.28-1-686/postinst/bootloader-test-error-2.6.28-1-686:
linux-image-2.6.28-1-686/preinst/abort-overwrite-2.6.28-1-686:
linux-image-2.6.28-1-686/postinst/kimage-is-a-directory:
linux-image-2.6.28-1-686/preinst/lilo-initrd-2.6.28-1-686: true
linux-image-2.6.28-1-686/preinst/abort-install-2.6.28-1-686:
linux-image-2.6.28-1-686/preinst/overwriting-modules-2.6.28-1-686: true
linux-image-2.6.28-1-686/preinst/bootloader-initrd-2.6.28-1-686: true
linux-image-2.6.28-1-686/postinst/bootloader-error-2.6.28-1-686:
--- End Message ---
--- Begin Message ---
On Sat, 28 Feb 2009, GSR wrote:
> Package: linux-image-2.6.28-1-686
> Version: 2.6.28-1
> Severity: important
>
> New 2.6.28 fails to boot as it finds no md0 (for root dev). mdadm
> complains it is unable to assemble it. With the provided shell it is
> clear sd[ab]* devices are missing at the point of boot sequence.
>
> OTOH, /sys/bus/scsi/ shows the SCSI controller (aic79xx) and the two
> disks. mdadm.conf in the initrd.img has the /dev/ paths and UUIDs to
> identify the md devices, fstab uses /dev/md0 though. 2.6.26 boots
> fine.
>
use rootdelay=X bootparam.
--- End Message ---
