Your message dated Sun, 28 Dec 2008 22:21:14 +0100
with message-id <20081228212114.ga4...@galadriel.inutil.org>
and subject line Re: Bug#427514: linux-image-2.6.21-1-amd64: System does not
boot with 2.6.21-4
has caused the Debian Bug report #427514,
regarding linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4
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.)
--
427514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4
Package: linux-image-2.6.21-1-amd64
Version: 2.6.21-5~snapshot.8808
Severity: critical
Justification: breaks the whole system
*** Please type your report below this line ***
Hi there,
since I have installed 2.6.21-4 from unstable I cannot boot my system
anymore.
First my configuration: an Asus A8N-E (nforce4) motherboard with two
SATA disks.
The disks are configured in a software RAID1 using mdadm:
/dev/md0 is my /
/dev/md1 is my swap
/dev/md2 is my /home
If I start the system with 2.6.20 it boots fine. Here's a picture of the
end of the initramfs and the start of the normal boot:
http://www.flickr.com/photos/90819...@n00/530049031/
The system reaches /sbin/init and it boots just fine.
Here is what happens with 2.6.21:
http://www.flickr.com/photos/90819...@n00/530049047/
Something goes wrong in the initramfs, and despite /dev/md0 is started,
it can't be mounted.
At this point I have tried to toy around in the initramfs, read
the /scripts directory but couldn't understand how to make the system
move along. (btw, I could really use a pager in there... I hate vi :D)
It should be noted that I can start my other two RAID arrays without
problems!
Please ignore the fact that my 2.6.21 is now a snapshot from the Debian
Kernel Team (btw, I have tried also 2.6.22rc3 but the problem is still
there) as the problem arised with the upgrade from 2.6.21-3 and -4 from
unstable.
I don't recall any udev or initramfs-tools upgrade that could have
broken the system, especially since 2.6.20 works just fine. Additionally
the changelog between -3 and -4 is extremely short so no luck there.
Thanks for any help you might give me.
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.20-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.21-1-amd64 depends on:
ii e2fsprog 1.39+1.40-WIP-2007.04.07+dfsg-2 ext2 file system utilities
and lib
ii initramf 0.88 tools for generating an
initramfs
ii module-i 3.3-pre11-1 tools for managing Linux
kernel mo
ii yaird [l 0.0.12-20 Yet Another mkInitRD
linux-image-2.6.21-1-amd64 recommends no packages.
-- debconf information:
linux-image-2.6.21-1-amd64/prerm/removing-running-kernel-2.6.21-1-amd64:
true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.21-1-amd64/postinst/bootloader-error-2.6.21-1-amd64:
linux-image-2.6.21-1-amd64/preinst/abort-install-2.6.21-1-amd64:
linux-image-2.6.21-1-amd64/prerm/would-invalidate-boot-loader-2.6.21-1-amd64:
true
linux-image-2.6.21-1-amd64/preinst/abort-overwrite-2.6.21-1-amd64:
linux-image-2.6.21-1-amd64/preinst/overwriting-modules-2.6.21-1-amd64:
true
linux-image-2.6.21-1-amd64/postinst/create-kimage-link-2.6.21-1-amd64:
true
linux-image-2.6.21-1-amd64/preinst/lilo-initrd-2.6.21-1-amd64: true
linux-image-2.6.21-1-amd64/postinst/old-initrd-link-2.6.21-1-amd64:
true
linux-image-2.6.21-1-amd64/postinst/old-system-map-link-2.6.21-1-amd64:
true
linux-image-2.6.21-1-amd64/postinst/old-dir-initrd-link-2.6.21-1-amd64:
true
linux-image-2.6.21-1-amd64/preinst/elilo-initrd-2.6.21-1-amd64: true
linux-image-2.6.21-1-amd64/postinst/depmod-error-2.6.21-1-amd64: false
linux-image-2.6.21-1-amd64/preinst/failed-to-move-modules-2.6.21-1-amd64:
linux-image-2.6.21-1-amd64/preinst/lilo-has-ramdisk:
linux-image-2.6.21-1-amd64/preinst/bootloader-initrd-2.6.21-1-amd64:
true
linux-image-2.6.21-1-amd64/preinst/initrd-2.6.21-1-amd64:
linux-image-2.6.21-1-amd64/postinst/kimage-is-a-directory:
*
linux-image-2.6.21-1-amd64/preinst/already-running-this-2.6.21-1-amd64:
linux-image-2.6.21-1-amd64/postinst/depmod-error-initrd-2.6.21-1-amd64:
false
linux-image-2.6.21-1-amd64/postinst/bootloader-test-error-2.6.21-1-amd64:
--
BOFH excuse #38: secretary plugged hairdryer into UPS
--- End Message ---
--- Begin Message ---
On Tue, Jun 26, 2007 at 12:29:18PM +0200, Michael Ritzert wrote:
> On Mon, 25 Jun 2007 17:11:05 +0200, maximilian attems <m...@stro.at> wrote:
>> pretty sure that your partition is not properly formated,
>> check it with:
>> /lib/udev/vol_id -t /dev/hda8
>> see bugs.debian.org/427972 of how to fix it.
>
> For the record: I saw the same problem with 2.6.21.
> The above was the correct hint to find what was wrong:
> ID_FS_TYPE=LVM2_member
> The dd command from 427972 will not work here, so I booted 2.6.21 and let
> it drop to the emergency shell.
> /dev/hda3 is my root partition, so I did
>
> mount -t ext3 /dev/hda3 /root
> cp /root/sbin/pvremove /sbin
> umount /root
> /sbin/pvremove /dev/hda3
>
> 2.6.21 boots just fine now.
Closing that bug.
Cheers,
Moritz
--- End Message ---
