Bug#310522: marked as done (kernel-image-2.6.11-1-k7: fails to boot)
Your message dated Mon, 23 May 2005 21:47:30 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#310522: kernel-image-2.6.11-1-k7: fails to boot has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 24 May 2005 04:32:07 + >From [EMAIL PROTECTED] Mon May 23 21:32:07 2005 Return-path: <[EMAIL PROTECTED]> Received: from pyramid-01.kattare.com [69.59.195.20] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DaR5L-0007VK-00; Mon, 23 May 2005 21:32:07 -0700 Received: from [192.168.1.154] (ip68-2-196-182.ph.ph.cox.net [68.2.196.182]) (authenticated bits=0) by pyramid-01.kattare.com (8.12.11/8.12.11) with ESMTP id j4O4W53h000363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <[EMAIL PROTECTED]>; Mon, 23 May 2005 21:32:06 -0700 Message-ID: <[EMAIL PROTECTED]> Date: Mon, 23 May 2005 21:32:05 -0700 From: Craig Condit <[EMAIL PROTECTED]> User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: kernel-image-2.6.11-1-k7: fails to boot Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6.11-1-k7 Version: 2.6.11-3 Severity: critical Justification: breaks the whole system kernel-image-2.6.11-1-k7-2.6.11-5 fails to boot. I receive continuous messages as follows: initrd-tools: 0.1.80 /sbin/init: 360 cannot open bin/root: No such file umount: bin: not mounted /sbin/init: 362 cannot create proc/sys/kernel/real-root-dev: Directory non-existent cat: proc/cmdline: No such file or directory umount: proc: not mounted Kernel can not convert a name into device number. Check your 'root=' argument passed on boot by bootloader Downgrading to 2.6.11-3 fixes the problem. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kernel-image-2.6.11-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.81 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information --- Received: (at 310522-done) by bugs.debian.org; 24 May 2005 04:47:32 + >From [EMAIL PROTECTED] Mon May 23 21:47:32 2005 Return-path: <[EMAIL PROTECTED]> Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (mauritius.dodds.net) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DaRKF-0001e0-00; Mon, 23 May 2005 21:47:31 -0700 Received: by mauritius.dodds.net (Postfix, from userid 1000) id EF2D0171D29; Mon, 23 May 2005 21:47:30 -0700 (PDT) Date: Mon, 23 May 2005 21:47:30 -0700 From: Steve Langasek <[EMAIL PROTECTED]> To: Craig Condit <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Bug#310522: kernel-image-2.6.11-1-k7: fails to boot Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X78YbkCBd9ye7Cvs" Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.9i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --X78YbkCBd9ye7Cvs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 23, 2005 at 09:32:05PM -0700, Craig Condit wrote: > Package: kernel-image-2.6.11-1-k7 > Version: 2.6.11-3 > Severity: critical > Justification: breaks the whole system > kernel-image-2.6.11-1-k7-2.6.11-5 fails to boot. I receive continuous > messages as follows: > initrd-tools: 0.1.80 > /sbin/init: 360 cannot
Bug#310522: kernel-image-2.6.11-1-k7: fails to boot
On Mon, 23 May 2005, Craig Condit wrote: Package: kernel-image-2.6.11-1-k7 Version: 2.6.11-3 Severity: critical Justification: breaks the whole system kernel-image-2.6.11-1-k7-2.6.11-5 fails to boot. I receive continuous messages as follows: initrd-tools: 0.1.80 /sbin/init: 360 cannot open bin/root: No such file umount: bin: not mounted /sbin/init: 362 cannot create proc/sys/kernel/real-root-dev: Directory non-existent cat: proc/cmdline: No such file or directory umount: proc: not mounted Kernel can not convert a name into device number. Check your 'root=' argument passed on boot by bootloader Downgrading to 2.6.11-3 fixes the problem. This is caused by broken initrd-tools. Please install the 0.1.81 version, which is currently available in instable, then run dpkg-reconfigure kernel-image-2.6.11-1-k7 to regenerate the initrd. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310522: kernel-image-2.6.11-1-k7: fails to boot
Package: kernel-image-2.6.11-1-k7 Version: 2.6.11-3 Severity: critical Justification: breaks the whole system kernel-image-2.6.11-1-k7-2.6.11-5 fails to boot. I receive continuous messages as follows: initrd-tools: 0.1.80 /sbin/init: 360 cannot open bin/root: No such file umount: bin: not mounted /sbin/init: 362 cannot create proc/sys/kernel/real-root-dev: Directory non-existent cat: proc/cmdline: No such file or directory umount: proc: not mounted Kernel can not convert a name into device number. Check your 'root=' argument passed on boot by bootloader Downgrading to 2.6.11-3 fixes the problem. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kernel-image-2.6.11-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.81 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kernel-image-2.6.8-i386_2.6.8-16_i386.changes ACCEPTED
Accepted: kernel-headers-2.6.8-2-386_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-386_2.6.8-16_i386.deb kernel-headers-2.6.8-2-686-smp_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-686-smp_2.6.8-16_i386.deb kernel-headers-2.6.8-2-686_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-686_2.6.8-16_i386.deb kernel-headers-2.6.8-2-k7-smp_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-k7-smp_2.6.8-16_i386.deb kernel-headers-2.6.8-2-k7_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-k7_2.6.8-16_i386.deb kernel-headers-2.6.8-2_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2_2.6.8-16_i386.deb kernel-image-2.6.8-2-386_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-386_2.6.8-16_i386.deb kernel-image-2.6.8-2-686-smp_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-686-smp_2.6.8-16_i386.deb kernel-image-2.6.8-2-686_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-686_2.6.8-16_i386.deb kernel-image-2.6.8-2-k7-smp_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-k7-smp_2.6.8-16_i386.deb kernel-image-2.6.8-2-k7_2.6.8-16_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-k7_2.6.8-16_i386.deb kernel-image-2.6.8-i386_2.6.8-16.dsc to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-16.dsc kernel-image-2.6.8-i386_2.6.8-16.tar.gz to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-16.tar.gz Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of kernel-image-2.6.8-i386_2.6.8-16_i386.changes
kernel-image-2.6.8-i386_2.6.8-16_i386.changes uploaded successfully to localhost along with the files: kernel-image-2.6.8-i386_2.6.8-16.dsc kernel-image-2.6.8-i386_2.6.8-16.tar.gz kernel-headers-2.6.8-2_2.6.8-16_i386.deb kernel-headers-2.6.8-2-686-smp_2.6.8-16_i386.deb kernel-image-2.6.8-2-686-smp_2.6.8-16_i386.deb kernel-headers-2.6.8-2-386_2.6.8-16_i386.deb kernel-image-2.6.8-2-386_2.6.8-16_i386.deb kernel-headers-2.6.8-2-686_2.6.8-16_i386.deb kernel-image-2.6.8-2-686_2.6.8-16_i386.deb kernel-headers-2.6.8-2-k7_2.6.8-16_i386.deb kernel-image-2.6.8-2-k7_2.6.8-16_i386.deb kernel-headers-2.6.8-2-k7-smp_2.6.8-16_i386.deb kernel-image-2.6.8-2-k7-smp_2.6.8-16_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kernel-image-2.6.11-ia64_2.6.11-4_ia64.changes ACCEPTED
Accepted: kernel-headers-2.6.11-1-itanium-smp_2.6.11-4_ia64.deb to pool/main/k/kernel-image-2.6.11-ia64/kernel-headers-2.6.11-1-itanium-smp_2.6.11-4_ia64.deb kernel-headers-2.6.11-1-itanium_2.6.11-4_ia64.deb to pool/main/k/kernel-image-2.6.11-ia64/kernel-headers-2.6.11-1-itanium_2.6.11-4_ia64.deb kernel-headers-2.6.11-1-mckinley-smp_2.6.11-4_ia64.deb to pool/main/k/kernel-image-2.6.11-ia64/kernel-headers-2.6.11-1-mckinley-smp_2.6.11-4_ia64.deb kernel-headers-2.6.11-1-mckinley_2.6.11-4_ia64.deb to pool/main/k/kernel-image-2.6.11-ia64/kernel-headers-2.6.11-1-mckinley_2.6.11-4_ia64.deb kernel-headers-2.6.11-1_2.6.11-4_ia64.deb to pool/main/k/kernel-image-2.6.11-ia64/kernel-headers-2.6.11-1_2.6.11-4_ia64.deb kernel-image-2.6.11-1-itanium-smp_2.6.11-4_ia64.deb to pool/main/k/kernel-image-2.6.11-ia64/kernel-image-2.6.11-1-itanium-smp_2.6.11-4_ia64.deb kernel-image-2.6.11-1-itanium_2.6.11-4_ia64.deb to pool/main/k/kernel-image-2.6.11-ia64/kernel-image-2.6.11-1-itanium_2.6.11-4_ia64.deb kernel-image-2.6.11-1-mckinley-smp_2.6.11-4_ia64.deb to pool/main/k/kernel-image-2.6.11-ia64/kernel-image-2.6.11-1-mckinley-smp_2.6.11-4_ia64.deb kernel-image-2.6.11-1-mckinley_2.6.11-4_ia64.deb to pool/main/k/kernel-image-2.6.11-ia64/kernel-image-2.6.11-1-mckinley_2.6.11-4_ia64.deb kernel-image-2.6.11-ia64_2.6.11-4.dsc to pool/main/k/kernel-image-2.6.11-ia64/kernel-image-2.6.11-ia64_2.6.11-4.dsc kernel-image-2.6.11-ia64_2.6.11-4.tar.gz to pool/main/k/kernel-image-2.6.11-ia64/kernel-image-2.6.11-ia64_2.6.11-4.tar.gz Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of kernel-image-2.6.11-ia64_2.6.11-4_ia64.changes
kernel-image-2.6.11-ia64_2.6.11-4_ia64.changes uploaded successfully to localhost along with the files: kernel-image-2.6.11-ia64_2.6.11-4.dsc kernel-image-2.6.11-ia64_2.6.11-4.tar.gz kernel-headers-2.6.11-1_2.6.11-4_ia64.deb kernel-headers-2.6.11-1-itanium-smp_2.6.11-4_ia64.deb kernel-image-2.6.11-1-itanium-smp_2.6.11-4_ia64.deb kernel-headers-2.6.11-1-itanium_2.6.11-4_ia64.deb kernel-image-2.6.11-1-itanium_2.6.11-4_ia64.deb kernel-headers-2.6.11-1-mckinley-smp_2.6.11-4_ia64.deb kernel-image-2.6.11-1-mckinley-smp_2.6.11-4_ia64.deb kernel-headers-2.6.11-1-mckinley_2.6.11-4_ia64.deb kernel-image-2.6.11-1-mckinley_2.6.11-4_ia64.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#307471: Remove fixed tag
tag 307471 - fixed thanks The fix for #310316 was to revert this change(amoungst others)... so I have removed the "fixed" tag! Hope that is the right thing to do... perhaps the "pending" tag should go too? - I'll let someone more knowledgeable do that though! I still hope that this patch will go into etch early in the testing life cycle! ... we shall see! Alex OWen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Remove fixed tag
Processing commands for [EMAIL PROTECTED]: > tag 307471 - fixed Bug#307471: initrd-tools: wish init would not run mount_root if rootdev=255 (ie nfs root). Tags were: fixed pending patch Tags removed: fixed > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
promise sx8 sata controller?
I am trying to learn more about the promise sx8 driver in the current 2.6-series kernel, and I'm wondering if any of you have had any experience with it. I'm currently running debian-sarge with a custom 2.6.11.10 kernel. The sx8 driver does not use libata, and it is a separate block device, outside of the scsi and ata hierarchies. If I compile the driver into my kernel, I end up with /dev/sx8/0 and /dev/sx8/0p1, etc. However, no scsi disk devices are created, and grub does not recognize that /dev/sx8/ devices are disks. There's no indication in /proc/scsi/ that they are being registered with the scsi subsystem; this is clearly different from every other sata controller I've used. I've been googling this for days, with no real luck. I have found changelogs for grub that suggest that my version (0.95) should support booting from the sx8. So my question is, how does one use this driver for sata disks? Is my problem a grub problem, or does it have something to do with the fact that this is a separate block device from the ata/scsi subsystems? There is a different open source driver directly available from promise, which seems to work better for my needs; however, I would like to be able to have the driver built directly into the kernel rather than modularized. When I insert the SATAIIS150.ko kernel module from this driver, dmesg immediately shows my disks; they are assigned standard scsi device nodes (sda, sdb, etc); and they are recognized by grub. What is the relationship between the promise driver and the one included in the kernel? Why does one work differently from the other? Is there something else I need to activate in my kernel configuration to get the standard 2.6 kernel driver to work the way I expect? I hope someone can shed some light. I can't seem to find any documentation or info anywhere. Many thanks, -C- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC: New uniform packaging scheme
On Mon, May 23, 2005 at 05:20:06PM +0200, Christoph Hellwig wrote: > On Thu, May 19, 2005 at 02:04:33PM -0400, Jurij Smakov wrote: > > Kernel packages are uniquely identified by their architecture, > > subarchitecture and flavour. For most arches the kernel images are > > built from the same source (upstream source with all-arch Debian > > patches), using different configuration files corresponding to > > different flavours. Subarch level is only required when specific > > unmerged patches need to be applied to the common source to support > > a particular class of hardware. As these patches potentially modify > > the headers, each subarch has to have its own kernel-headers package. > > I think it's a very bad idea to have different source bases and if > possible we should implement it in the packaging - that would encourage not -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC: New uniform packaging scheme
On Thu, May 19, 2005 at 02:04:33PM -0400, Jurij Smakov wrote:
> Kernel packages are uniquely identified by their architecture,
> subarchitecture and flavour. For most arches the kernel images are
> built from the same source (upstream source with all-arch Debian
> patches), using different configuration files corresponding to
> different flavours. Subarch level is only required when specific
> unmerged patches need to be applied to the common source to support
> a particular class of hardware. As these patches potentially modify
> the headers, each subarch has to have its own kernel-headers package.
I think it's a very bad idea to have different source bases and if
possible we should implement it in the packaging - that would encourage
people to use the facility instead of fixing things up properly. And
doing that is always possible. I managed to fix the big mess that ia64
was in the 2.5 series, and Al Viro managed to fix m68k easily for 2.6.12
or 2.6.13 - the fix was mostly trivial the only problem was political
unwillingness from the m68k maintainers.
> Packaging scheme
>
> To accomodate all the possibilities, the following packaging scheme
> (to be implemented by the common source package) is proposed:
>
> kernel-headers-$(version)-$(abiname)
>
> A common headers package for an architecture without subarches.
> It will contain all the common header files required to build the
> 3rd party modules, including the scripts subdirectory (currently
> packaged as kernel-kbuild). It should contain only the includes
> for this particular arch, i.e. include/{asm-generic,asm-$(arch)}
> Unpacks to /usr/src/kernel-headers-$(version)-$(abiname).
>
> kernel-headers-$(version)-$(abiname)-$(subarch)
>
> A common headers package for an architecture with subarches.
> Same purpose and contents as the one above.
>
> kernel-headers-$(version)-$(abiname)-$(flavour)
>
> Flavour-specific kernel headers package, containing mostly the
> configuration files. It will have the same name for both cases
> (subarch or no subarch). As a result there is a restriction that
> all flavour names across all arches/subarches have to be unique,
> but that does not seem too problematic. This package must unpack
> to /usr/src/kernel-headers-$(version)-$(abiname)-$(flavour),
> depend on an appropriate common kernel-headers package, set up
> the symbolic links into it to provide a complete build-tree, and
> supply the /lib/modules/$(version)-$(abiname)-$(flavour)/build
> symlink to that tree.
I think we should only have a single kernel-headers-$(version)-$(abiname)
package. There's quite a bit of cross including of asm- headers,
and having the full set available makes getting this right much easier.
It's not a lot of space used anyway.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310352: marked as done (kernel-image-2.6.11-1-k7: cannot reboot after upgrade)
Your message dated Mon, 23 May 2005 10:02:13 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#310316: fixed in initrd-tools 0.1.81 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 23 May 2005 07:14:04 + >From [EMAIL PROTECTED] Mon May 23 00:14:04 2005 Return-path: <[EMAIL PROTECTED]> Received: from lns-p19-28f-81-56-208-77.adsl.proxad.net (localhost.localdomain) [81.56.208.77] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Da78W-0002lN-00; Mon, 23 May 2005 00:14:04 -0700 Received: from alex by localhost.localdomain with local (Exim 4.50) id 1Da78T-z2-J3; Mon, 23 May 2005 09:14:01 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Modesto Alexandre <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-image-2.6.11-1-k7: cannot reboot after upgrade X-Mailer: reportbug 3.12 Date: Mon, 23 May 2005 09:14:01 +0200 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6.11-1-k7 Version: 2.6.11-5 Severity: critical Justification: breaks the whole system after an apt-get upgrade four of my servers didn't reboot, message on the screen is : "kernel can not convert a name into device number" /sbin/init 360 cannot.. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-image-2.6.11-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.80 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information --- Received: (at 310316-close) by bugs.debian.org; 23 May 2005 14:08:06 + >From [EMAIL PROTECTED] Mon May 23 07:08:06 2005 Return-path: <[EMAIL PROTECTED]> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DaDbB-Or-00; Mon, 23 May 2005 07:08:05 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1DaDVV-0005is-00; Mon, 23 May 2005 10:02:13 -0400 From: Steve Langasek <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.55 $ Subject: Bug#310316: fixed in initrd-tools 0.1.81 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Mon, 23 May 2005 10:02:13 -0400 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Source: initrd-tools Source-Version: 0.1.81 We believe that the bug you reported is fixed in the latest version of initrd-tools, which is due to be installed in the Debian FTP archive: initrd-tools_0.1.81.dsc to pool/main/i/initrd-tools/initrd-tools_0.1.81.dsc initrd-tools_0.1.81.tar.gz to pool/main/i/initrd-tools/initrd-tools_0.1.81.tar.gz initrd-tools_0.1.81_all.deb to pool/main/i/initrd-tools/initrd-tools_0.1.81_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek <[EMAIL PROTECTED]> (supplier of updated initrd-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 23 May 2005 01:22:48 -0700 Source: initrd-tools Binary: initrd-tools Architecture: source all Version: 0.1.81 Distribution: unstable Urgency: high
Bug#310316: marked as done (initrd-tools)
Your message dated Mon, 23 May 2005 10:02:13 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#310316: fixed in initrd-tools 0.1.81 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 23 May 2005 02:02:14 + >From [EMAIL PROTECTED] Sun May 22 19:02:14 2005 Return-path: <[EMAIL PROTECTED]> Received: from fmmailgate04.web.de [217.72.192.242] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Da2Gk-0006RQ-00; Sun, 22 May 2005 19:02:14 -0700 Received: by fmmailgate04.web.de (8.12.10/8.12.10/webde Linux 0.7) with SMTP id j4N1xQO7011882 for [EMAIL PROTECTED]; Mon, 23 May 2005 04:01:43 +0200 Received: from [84.170.82.143] by freemailng0202.web.de with HTTP; Mon, 23 May 2005 04:01:40 +0200 Date: Mon, 23 May 2005 04:01:40 +0200 Message-Id: <[EMAIL PROTECTED]> MIME-Version: 1.0 From: "Heldt Chrisitian" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: initrd-tools Precedence: fm-user Organization: http://freemail.web.de/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: initrd-tools Version: 0.1.80 just installed fresh sarge netinstall (only base system/packages with standard 2.6.8 kernel) after upgrading to sid initrd-tools is unable to find bin/root output at bootup initrd-tools: 0.1.80 /sbin/init: 360: cannot open bin/root: No such file after i set initrd-tools to hold it works with previous version __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 --- Received: (at 310316-close) by bugs.debian.org; 23 May 2005 14:08:06 + >From [EMAIL PROTECTED] Mon May 23 07:08:06 2005 Return-path: <[EMAIL PROTECTED]> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DaDbB-Or-00; Mon, 23 May 2005 07:08:05 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1DaDVV-0005is-00; Mon, 23 May 2005 10:02:13 -0400 From: Steve Langasek <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.55 $ Subject: Bug#310316: fixed in initrd-tools 0.1.81 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Mon, 23 May 2005 10:02:13 -0400 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Source: initrd-tools Source-Version: 0.1.81 We believe that the bug you reported is fixed in the latest version of initrd-tools, which is due to be installed in the Debian FTP archive: initrd-tools_0.1.81.dsc to pool/main/i/initrd-tools/initrd-tools_0.1.81.dsc initrd-tools_0.1.81.tar.gz to pool/main/i/initrd-tools/initrd-tools_0.1.81.tar.gz initrd-tools_0.1.81_all.deb to pool/main/i/initrd-tools/initrd-tools_0.1.81_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek <[EMAIL PROTECTED]> (supplier of updated initrd-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 23 May 2005 01:22:48 -0700 Source: initrd-tools Binary: initrd-tools Architecture: source all Version: 0.1.81 Distribution: unstable Urgency: high Maintainer: Debian kernel team Changed-By: Steve Langasek <[EMAIL PROTECTED]> Description: initrd-tools - tools to create initrd image for prepackaged Linux kernel Closes: 310316 Changes: initrd-tools (0.1.81) unstable; urgency=high . * Rever
Bug#310420: marked as done (kernel-image-2.6.11-1-686: does not boot (fails in init) after upgrading from 2.6.11-3)
Your message dated Mon, 23 May 2005 10:02:13 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#310316: fixed in initrd-tools 0.1.81 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 23 May 2005 13:19:41 + >From [EMAIL PROTECTED] Mon May 23 06:19:41 2005 Return-path: <[EMAIL PROTECTED]> Received: from mx3.netapp.com [217.70.210.9] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DaCqK-0001hc-00; Mon, 23 May 2005 06:19:40 -0700 Received: from smtp2.corp.netapp.com (10.57.159.114) by mx3.netapp.com with ESMTP; 23 May 2005 06:19:08 -0700 X-IronPort-AV: i="3.93,128,1115017200"; d="scan'208"; a="11699668:sNHT18016316" Received: from appaji.hq.netapp.com ([10.72.11.45]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id j4NDJ5xF020983; Mon, 23 May 2005 06:19:06 -0700 (PDT) Received: from giridhar by appaji.hq.netapp.com with local (Exim 3.36 #1 (Debian)) id 1DaCpk-0001dM-00; Mon, 23 May 2005 18:49:04 +0530 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Y Giridhar Appaji Nag <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> X-Debbugs-No-Ack: true X-Website: http://www.appaji.net/ Subject: kernel-image-2.6.11-1-686: does not boot (fails in init) after upgrading from 2.6.11-3 Reply-To: Y Giridhar Appaji Nag <[EMAIL PROTECTED]> X-Mailer: reportbug 3.12 Date: Mon, 23 May 2005 18:49:04 +0530 X-Debbugs-Cc: Y Giridhar Appaji Nag <[EMAIL PROTECTED]> Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-14.0 required=4.0 tests=BAYES_00,HAS_PACKAGE, X_DEBBUGS_CC,X_DEBBUGS_NO_ACK autolearn=ham version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6.11-1-686 Version: 2.6.11-5 Severity: grave Justification: renders package unusable I upgraded from 2.6.11-3 to 2.6.11-5 (dist-upgrade) and the kernel fails to boot with error messages indicating that a few files cannot be found. The transcripts of upgrade sessions and the error messages while booting follow: $ agdu Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done The following packages will be upgraded: kernel-image-2.6.11-1-686 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/15.9MB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 90899 files and directories currently installed.) Preparing to replace kernel-image-2.6.11-1-686 2.6.11-3 (using .../kernel-image-2.6.11-1-686_2.6.11-5_i386.deb) ... The directory /lib/modules/2.6.11-1-686 still exists. Continuing as directed. Unpacking replacement kernel-image-2.6.11-1-686 ... Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /vmlinuz-2.6.11-1-686 Found kernel: /vmlinuz-2.6.10-1-686 Found kernel: /vmlinuz-2.4.18-bf2.4 Found kernel: /memtest86.bin Found kernel: /memtest86+.bin Updating /boot/grub/menu.lst ... done Setting up kernel-image-2.6.11-1-686 (2.6.11-5) ... dpkg: warning, architecture `i686-pc-linux-gnu' not in remapping table <=== is this ok? dpkg: warning, architecture `i686-pc-linux-gnu' not in remapping table <=== is this ok? Not touching initrd symlinks since we are being reinstalled (2.6.11-3) Not updating image symbolic links since we are being updated (2.6.11-3) Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /vmlinuz-2.6.11-1-686 Found kernel: /vmlinuz-2.6.10-1-686 Found kernel: /vmlinuz-2.4.18-bf2.4 Found kernel: /memtest86.bin Found kernel: /memtest86+.bin Updating /boot/grub/menu.lst ... done While booting (messages hand typed - I did not find a way to capture these as the boot process failed): [snip] hda: Host Protected Area disabled. hda: 78156288 sectors (40016 MB) w/1821KiB Cache, CHS=16383/255/63, UDMA(100) /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 > Kernel can not convert a name into desc number Check your 'ro
initrd-tools_0.1.81_i386.changes ACCEPTED
Accepted: initrd-tools_0.1.81.dsc to pool/main/i/initrd-tools/initrd-tools_0.1.81.dsc initrd-tools_0.1.81.tar.gz to pool/main/i/initrd-tools/initrd-tools_0.1.81.tar.gz initrd-tools_0.1.81_all.deb to pool/main/i/initrd-tools/initrd-tools_0.1.81_all.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 310316 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of initrd-tools_0.1.81_i386.changes
initrd-tools_0.1.81_i386.changes uploaded successfully to localhost along with the files: initrd-tools_0.1.81.dsc initrd-tools_0.1.81.tar.gz initrd-tools_0.1.81_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310420: kernel-image-2.6.11-1-686: does not boot (fails in init) after upgrading from 2.6.11-3
On 05/05/23 18:49 +0530, Giridhar - Debian said ... > > [snip] > hda: Host Protected Area disabled. > hda: 78156288 sectors (40016 MB) w/1821KiB Cache, CHS=16383/255/63, UDMA(100) > /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 > p13 p14 p15 > > Kernel can not convert a name into desc number > Check your 'root=' argument passed on boot by bootloader. > initrd-tools: 0.1.80 > /sbin/init: 360: cannot open bin/root: no such file > umount: bin: not mounted > /sbin/init: 362: cannot create proc/sys/kernel/real-root-dev: Directory non > existant > cat: proc/cmdline: No such file or directory > umount: proc not mounted > [snip] I don't know the complete boot process and how initrd works, but I have included some more information related to the initrd.img in the and the above error messages: $ sudo mount /boot/initrd.img-2.6.11-1-686 -o loop /mnt/c $ pwd /mnt/c $ ls bin/root ls: bin/root: No such file or directory $ ls proc/sys/kernel/real-root-dev ls: proc/sys/kernel/real-root-dev: No such file or directory $ ls proc/cmdline ls: proc/cmdline: No such file or directory Giridhar -- Y Giridhar Appaji Nag | http://www.appaji.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 310420 to initrd-tools, merging 310316 310420
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.14 > reassign 310420 initrd-tools Bug#310420: kernel-image-2.6.11-1-686: does not boot (fails in init) after upgrading from 2.6.11-3 Bug reassigned from package `kernel-image-2.6.11-1-686' to `initrd-tools'. > merge 310316 310420 Bug#310316: initrd-tools Bug#310420: kernel-image-2.6.11-1-686: does not boot (fails in init) after upgrading from 2.6.11-3 Bug#310352: kernel-image-2.6.11-1-k7: cannot reboot after upgrade Merged 310316 310352 310420. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310420: kernel-image-2.6.11-1-686: does not boot (fails in init) after upgrading from 2.6.11-3
Package: kernel-image-2.6.11-1-686 Version: 2.6.11-5 Severity: grave Justification: renders package unusable I upgraded from 2.6.11-3 to 2.6.11-5 (dist-upgrade) and the kernel fails to boot with error messages indicating that a few files cannot be found. The transcripts of upgrade sessions and the error messages while booting follow: $ agdu Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done The following packages will be upgraded: kernel-image-2.6.11-1-686 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/15.9MB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 90899 files and directories currently installed.) Preparing to replace kernel-image-2.6.11-1-686 2.6.11-3 (using .../kernel-image-2.6.11-1-686_2.6.11-5_i386.deb) ... The directory /lib/modules/2.6.11-1-686 still exists. Continuing as directed. Unpacking replacement kernel-image-2.6.11-1-686 ... Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /vmlinuz-2.6.11-1-686 Found kernel: /vmlinuz-2.6.10-1-686 Found kernel: /vmlinuz-2.4.18-bf2.4 Found kernel: /memtest86.bin Found kernel: /memtest86+.bin Updating /boot/grub/menu.lst ... done Setting up kernel-image-2.6.11-1-686 (2.6.11-5) ... dpkg: warning, architecture `i686-pc-linux-gnu' not in remapping table <=== is this ok? dpkg: warning, architecture `i686-pc-linux-gnu' not in remapping table <=== is this ok? Not touching initrd symlinks since we are being reinstalled (2.6.11-3) Not updating image symbolic links since we are being updated (2.6.11-3) Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /vmlinuz-2.6.11-1-686 Found kernel: /vmlinuz-2.6.10-1-686 Found kernel: /vmlinuz-2.4.18-bf2.4 Found kernel: /memtest86.bin Found kernel: /memtest86+.bin Updating /boot/grub/menu.lst ... done While booting (messages hand typed - I did not find a way to capture these as the boot process failed): [snip] hda: Host Protected Area disabled. hda: 78156288 sectors (40016 MB) w/1821KiB Cache, CHS=16383/255/63, UDMA(100) /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 > Kernel can not convert a name into desc number Check your 'root=' argument passed on boot by bootloader. initrd-tools: 0.1.80 /sbin/init: 360: cannot open bin/root: no such file umount: bin: not mounted /sbin/init: 362: cannot create proc/sys/kernel/real-root-dev: Directory non existant cat: proc/cmdline: No such file or directory umount: proc not mounted [snip] After this, the messages from 'Kernel can not...' are repeated in a loop. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages kernel-image-2.6.11-1-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.80 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310415: kernel-image-2.6.11-1-686: debsums warnings about mismatching checksum on 2.6.11-5 after upgrading from 2.6.11-3
Package: kernel-image-2.6.11-1-686 Version: 2.6.11-5 Severity: normal I did a dist-upgrade, because of which the kernel-image-2.6.11-1-686 was upgraded from version 2.6.11-3 to 2.6.11-5. But looks like there is a problem with the checksums on module.* files in lib/modules/2.6.11-1-686/ $ reportbug Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. > kernel-image-2.6.11-1-686 Using 'Y Giridhar Appaji Nag <[EMAIL PROTECTED]>' as your from address. Detected character set: UTF-8 Please change your locale if this is incorrect. Getting status for kernel-image-2.6.11-1-686... Verifying package integrity... There may be a problem with your installation of kernel-image-2.6.11-1-686; the following files appear to be missing or changed: debsums: checksum mismatch kernel-image-2.6.11-1-686 file /lib/modules/2.6.11-1-686/modules.pcimap debsums: checksum mismatch kernel-image-2.6.11-1-686 file /lib/modules/2.6.11-1-686/modules.dep debsums: checksum mismatch kernel-image-2.6.11-1-686 file /lib/modules/2.6.11-1-686/modules.ieee1394map debsums: checksum mismatch kernel-image-2.6.11-1-686 file /lib/modules/2.6.11-1-686/modules.usbmap debsums: checksum mismatch kernel-image-2.6.11-1-686 file /lib/modules/2.6.11-1-686/modules.isapnpmap debsums: checksum mismatch kernel-image-2.6.11-1-686 file /lib/modules/2.6.11-1-686/modules.alias debsums: checksum mismatch kernel-image-2.6.11-1-686 file /lib/modules/2.6.11-1-686/modules.symbols Do you still want to file a report [y|N|q|?]? y [snip] Giridhar -- Y Giridhar Appaji Nag | http://www.appaji.net/ -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages kernel-image-2.6.11-1-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.80 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#264839: marked as done (initrd-tools: mkinitrd should include keyboard modules (i8042, atkbd) in case an early fsck interaction is needed)
Your message dated Mon, 23 May 2005 03:38:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in NMU of initrd-tools 0.1.80 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 10 Aug 2004 16:24:28 + >From [EMAIL PROTECTED] Tue Aug 10 09:24:28 2004 Return-path: <[EMAIL PROTECTED]> Received: from smtp2.wanadoo.fr (mwinf0212.wanadoo.fr) [193.252.22.29] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BuZQK-0007Wu-00; Tue, 10 Aug 2004 09:24:28 -0700 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0212.wanadoo.fr (SMTP Server) with SMTP id E9E9A18000FD; Tue, 10 Aug 2004 18:23:56 +0200 (CEST) Received: from pegasos (AStrasbourg-251-1-45-145.w82-126.abo.wanadoo.fr [82.126.154.145]) by mwinf0212.wanadoo.fr (SMTP Server) with ESMTP id BEDB0180019F; Tue, 10 Aug 2004 18:23:56 +0200 (CEST) Received: from luther by pegasos with local (Exim 4.34) id 1BuZVr-0002oT-9A; Tue, 10 Aug 2004 18:30:11 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Sven Luther <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: initrd-tools: mkinitrd should include keyboard modules (i8042, atkbd) in case an early fsck interaction is needed X-Mailer: reportbug 2.63 Date: Tue, 10 Aug 2004 18:30:10 +0200 Message-Id: <[EMAIL PROTECTED]> Sender: Sven Luther <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: initrd-tools Version: 0.1.72 Severity: normal On powerpc/pegasos, and possibly also on prep and chrp-rs6k boxes, the at kbd drivers are built modular. This is no major problem since debian-installer fills the needed modules (i8042, serio, atkbd) in the /etc/modules. But, as i recently noticed, these modules are not loaded yet if there is a fsck that needs user interaction on the root filesystem. So, i believe that in this cases, it would be best to always include them in the initrd. No idea how to search for them though, as i feel that on x86 and other such arches, those drivers are builtin the kernel. Maybe it would be best to check for arch/subarch like it is done in the earlt d-i initrd, and add the modules accordyingly. Friendly, Sven Luther -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.4.25-powerpc Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] --- Received: (at 264839-done) by bugs.debian.org; 23 May 2005 10:38:52 + >From [EMAIL PROTECTED] Mon May 23 03:38:51 2005 Return-path: <[EMAIL PROTECTED]> Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (mauritius.dodds.net) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DaAKe-0002EM-00; Mon, 23 May 2005 03:38:48 -0700 Received: by mauritius.dodds.net (Postfix, from userid 1000) id 9E9BBA3BF1; Mon, 23 May 2005 03:38:47 -0700 (PDT) Date: Mon, 23 May 2005 03:38:47 -0700 From: Steve Langasek <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Processed: Fixed in NMU of initrd-tools 0.1.80 Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ABTtc+pdwF7KHXCz" Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.9i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --ABTtc+pdwF7KHXCz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable These bugs are fixed in initrd-tools, but were not closed because the previous upload was listed as an NMU. The changelog of the upload in question was as follows: initrd-tools (0.1.80) unstable; urg
Bug#310395: initrd-tools: outfile option -o can not handle relative file declaration
Package: initrd-tools Version: 0.1.80 Severity: important I've called mkinitrd -o initrd.img in /boot directory and no initrd.img is created there. I've seen with mkinitrd -k ... that the image file is created in the mkinitrd working directory /tmp/mkinitrd.../initrd/ With absolut outfile definition -o /boot/initrd.img everything seems to be fine. cu -- System Information: Debian Release: sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages initrd-tools depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii cpio 2.5-1.2GNU cpio -- a program to manage ar ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F ii dash 0.5.2-5The Debian Almquist Shell ii fileutils 5.2.1-2The GNU file management utilities ii util-linux2.12p-4Miscellaneous system utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#269726: marked as done (Software RAID: if kernel compiled without devfs , software raid boot failed)
Your message dated Mon, 23 May 2005 03:38:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in NMU of initrd-tools 0.1.80 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 3 Sep 2004 06:48:38 + >From [EMAIL PROTECTED] Thu Sep 02 23:48:38 2004 Return-path: <[EMAIL PROTECTED]> Received: from kz-gw.david.bg (office.kz.david.bg) [213.91.189.33] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1C37sD-Tr-00; Thu, 02 Sep 2004 23:48:37 -0700 Received: (qmail 16357 invoked from network); 3 Sep 2004 06:48:33 - Received: from unknown (HELO jsoft) (193.68.150.13) by debian.localnet with SMTP; 3 Sep 2004 06:48:33 - Message-ID: <[EMAIL PROTECTED]> Reply-To: "Ilian Jovchev" <[EMAIL PROTECTED]> From: "Ilian Jovchev" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: Software RAID: if kernel compiled without devfs , software raid boot failed Date: Fri, 3 Sep 2004 09:48:05 +0300 Organization: DAVID Holding Co. MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.1 required=4.0 tests=BAYES_44,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: initrd-tools Version: 0.1.74 Severity: normal Hi, There is a problem, when mkinitrd built initrd image, and use mdadm to mount root md device and kernel compiled without devfs support. I found folowing mount code in initrd image script file: > ROOT=/dev/md0 > mdadm -A /devfs/md/0 -R -u fc9ec4c7:ffc8c975:942ec4de:4f5bc296 /dev/sdb2 /dev/sda2 script trying to mount root device /devfs/md/0, but it is not exists, because devfs is not supported. DEVFS is deprecated in 2.6 kernel, and I think that issue described above is very confused for people, who decides to build kernels without devfs support. Is it possible, to solve this problem ??? Best Regards: Ilian Jovchev --- Received: (at 269726-done) by bugs.debian.org; 23 May 2005 10:38:51 + >From [EMAIL PROTECTED] Mon May 23 03:38:51 2005 Return-path: <[EMAIL PROTECTED]> Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (mauritius.dodds.net) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DaAKe-0002EM-00; Mon, 23 May 2005 03:38:48 -0700 Received: by mauritius.dodds.net (Postfix, from userid 1000) id 9E9BBA3BF1; Mon, 23 May 2005 03:38:47 -0700 (PDT) Date: Mon, 23 May 2005 03:38:47 -0700 From: Steve Langasek <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Processed: Fixed in NMU of initrd-tools 0.1.80 Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ABTtc+pdwF7KHXCz" Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.9i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 2 --ABTtc+pdwF7KHXCz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable These bugs are fixed in initrd-tools, but were not closed because the previous upload was listed as an NMU. The changelog of the upload in question was as follows: initrd-tools (0.1.80) unstable; urgency=3Dhigh * Sven Luther - Let's add the keyboard input modules on powerpc. (Closes: #264839) * Maximilian Attems - Be less noisy when unloading modules. The errors are harmless, beside initrd shouldn't load that bunch of modules. Fix makes bootup less "scary" for kernels > 2.6.8. - Fix boot when using raid root with non devfs kernels. Closes: #284763, #269726, #305145, #299103 - Warn if root device is not fo
Bug#305145: marked as done (initrd-tools: Unable to automatically build initrd.img when using partition over RAID device)
Your message dated Mon, 23 May 2005 03:38:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in NMU of initrd-tools 0.1.80 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 18 Apr 2005 08:54:42 + >From [EMAIL PROTECTED] Mon Apr 18 01:54:42 2005 Return-path: <[EMAIL PROTECTED]> Received: from osiris.lip6.fr [132.227.60.30] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DNS1i-0004t9-00; Mon, 18 Apr 2005 01:54:42 -0700 Received: from localhost.localdomain (mist.pepiniere.jussieu.fr [132.227.161.1]) by osiris.lip6.fr (8.13.1/jtpda-5.4+victor) with ESMTP id j3I8sb38007220 for <[EMAIL PROTECTED]>; Mon, 18 Apr 2005 10:54:37 +0200 X-pt: osiris.lip6.fr Received: from bhamet by localhost.localdomain with local (Exim 4.50) id 1DNQ9m-0001cA-0k for [EMAIL PROTECTED]; Mon, 18 Apr 2005 08:54:54 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" From: Benoit Hamet <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: initrd-tools: Unable to automatically build initrd.img when using partition over RAID device X-Mailer: reportbug 3.8 Date: Mon, 18 Apr 2005 08:54:53 +0200 Message-Id: <[EMAIL PROTECTED]> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0b2 (osiris.lip6.fr [132.227.60.30]); Mon, 18 Apr 2005 10:54:37 +0200 (CEST) X-Scanned-By: osiris.lip6.fr Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by osiris.lip6.fr id j3I8sb38007220 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: initrd-tools Version: 0.1.78 Severity: important I get the following configuration : 2 SATA drives /dev/sd[ab]1 =3D=3D /boot (but not a real RAID) /dev/sd[ab]2 =3D=3D swap (not in RAID) /dev/sda3 =3D=3D / (temporary install system due to big problems with the= =20 debian-installer :)) /dev/sdb3 =3D=3D /tmp (temporary install) /dev/sd[ab]4 =3D=3D One big partition for RAID translated into /dev/mdp0 = or=20 /dev/md/mdp0 (not using or using devfs) then in this configuration I get, /dev/mdp0p[1234] with /dev/mdp0p1 =3D=3D= =20 future /, 2=3D/usr, 3=3D/var, 4=3D/home Under a chrooted environnement (the future tree is mounted) I try to use=20 mkinitrd to build a RAID enabled initrd image. As you can see I don't=20 use devfs and the name of the drive is not "really" choosen by me.=20 mkinitrd fails to generate the image because it don't know how to handle=20 this root device ... I try to look in mkinitrd script and see that most=20 things are "harcoded" in it. But in the case of mdadm an array could be=20 called /dev/home0 for example with /dev/home0p1 for first partition etc=20 ... (man mdadm IIRC). So can I suggest to add something like MDBASE=3D/dev/md[p]$minor which=20 could be settled in the mkinitrd.conf ? This will not solve my problem,=20 but at least, should help me a little. I will try to build a patch in a=20 near future. Regards, Beno=EEt -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=3DISO-8859-15) Versions of packages initrd-tools depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii cpio 2.5-1.2GNU cpio -- a program to man= age ar ii cramfsprogs 1.1-6 Tools for CramFs (Compressed= ROM F ii dash 0.5.2-4The Debian Almquist Shell ii util-linux2.12-10Miscellaneous system utiliti= es -- no debconf information --- Received: (at 305145-done) by bugs.debian.org; 23 May 2005 10:38:49 + >From [EMAIL PROTECTED] Mon May 23 03:38:49 2005 Return-path: <[EMAIL PROTECTED]> Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (mauritius.dodds.net) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DaAKe-0002EM-00; Mon, 23 May 2005 03:38:48 -0700 Received: by mauritius.dodds.net (Postfix, from userid 1000) id 9E9BBA3BF1; Mon, 23 May 2005 03:38:47 -0700 (PDT) Date: Mon, 23 M
Bug#284763: marked as done (initrd-tools: md and devfs)
Your message dated Mon, 23 May 2005 03:38:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in NMU of initrd-tools 0.1.80 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 8 Dec 2004 16:02:00 + >From [EMAIL PROTECTED] Wed Dec 08 08:02:00 2004 Return-path: <[EMAIL PROTECTED]> Received: from egg.hpc2n.umu.se [130.239.45.244] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Cc4GN-00014C-00; Wed, 08 Dec 2004 08:02:00 -0800 Received: from m192.hpc2n.umu.se (m192.hpc2n.umu.se [130.239.78.193]) by egg.hpc2n.umu.se (Postfix) with ESMTP id 3AB1A28DB; Wed, 8 Dec 2004 17:01:55 +0100 (MET) Received: from torkel by m192.hpc2n.umu.se with local (Exim 3.36 #1 (Debian)) id 1Cc4GJ-0007qR-00; Wed, 08 Dec 2004 17:01:55 +0100 Content-Type: multipart/mixed; boundary="===0973099918036161290==" MIME-Version: 1.0 From: =?iso-8859-1?q?Bj=C3rn_Torkelsson?= <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: initrd-tools: md and devfs X-Mailer: reportbug 2.64 Date: Wed, 08 Dec 2004 17:01:55 +0100 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: This is a multi-part MIME message sent by reportbug. --===0973099918036161290== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Package: initrd-tools Version: 0.1.74 Severity: normal Tags: patch Hi, I had to apply the attached (dirty, quickfix) patch to be able to get initrd-tools to work with mdadm on a 2.6.9 kernel compiled without devfs support. /torkel -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.8-hpc2n-amd64-k8-smp Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages initrd-tools depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii cpio 2.5-1.1GNU cpio -- a program to manage ar ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F ii dash 0.5.1-2The Debian Almquist Shell ii util-linux2.12-7.1 Miscellaneous system utilities -- no debconf information --===0973099918036161290== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="mkinitrd.diff" --- mkinitrd.orig 2004-12-08 11:26:35.437843697 +0100 +++ mkinitrd2004-12-08 11:26:10.337842457 +0100 @@ -175,7 +175,9 @@ )" printf '%s\n' $devices > getroot - echo mdadm -A /devfs/md/$minor -R -u $uuid $devices \ + echo /dev/md$minor >&4 + echo '[ -c /dev/md$minor ] || mknod /dev/md$minor b 9 $minor' >&5 + echo mdadm -A /dev/md$minor -R -u $uuid $devices \ > md$minor-script echo /sbin/mdadm >&6 } --===0973099918036161290==-- --- Received: (at 284763-done) by bugs.debian.org; 23 May 2005 10:38:51 + >From [EMAIL PROTECTED] Mon May 23 03:38:49 2005 Return-path: <[EMAIL PROTECTED]> Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (mauritius.dodds.net) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DaAKe-0002EM-00; Mon, 23 May 2005 03:38:48 -0700 Received: by mauritius.dodds.net (Postfix, from userid 1000) id 9E9BBA3BF1; Mon, 23 May 2005 03:38:47 -0700 (PDT) Date: Mon, 23 May 2005 03:38:47 -0700 From: Steve Langasek <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Processed: Fixed in NMU of initrd-tools 0.1.80 Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ABTtc+pdwF7KHXCz" Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.9i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-S
Bug#299103: marked as done (initrd-tools: mkinitrd tries to use devfs in 2.6 series kernel)
Your message dated Mon, 23 May 2005 03:38:47 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Processed: Fixed in NMU of initrd-tools 0.1.80
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
Received: (at submit) by bugs.debian.org; 11 Mar 2005 20:07:34 +
>From [EMAIL PROTECTED] Fri Mar 11 12:07:34 2005
Return-path: <[EMAIL PROTECTED]>
Received: from (localhost.localdomain) [138.4.10.230]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D9qQ1-0006E4-00; Fri, 11 Mar 2005 12:07:33 -0800
Received: from jrojo by localhost.localdomain with local (Exim 4.44)
id 1D9qPU-0001pp-WC
for [EMAIL PROTECTED]; Fri, 11 Mar 2005 21:07:01 +0100
Content-Type: multipart/mixed; boundary="===0452105401=="
MIME-Version: 1.0
From: =?iso-8859-15?q?Jes=FAs_Rojo_Mart=EDnez?= <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: initrd-tools: mkinitrd tries to use devfs in 2.6 series kernel
X-Mailer: reportbug 3.8
Date: Fri, 11 Mar 2005 21:07:00 +0100
X-Debbugs-Cc: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===0452105401==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: initrd-tools
Version: 0.1.77
Severity: important
Tags: patch
I use RAID disks, including the root partition. Thus I used and initrd image to
boot correctly.
However, when I use mkinitrd from the initrd-tools, it fails to boot because it
doesn't find the root partition,
because mkinitrd uses devfs (and obviusly, I don't have devfs in the 2.6
kernel).
I send a patch that works fine for me (and it should work for everybody). The
patch could be better, concretaly
the part that detects other RAID partitions:
- Don't copy /etc/mdadm/mdadm.conf, just generate it with some like:
echo "DEVICES partitions" > $INITRD/$MDADMCONF
mdadm -D --scan >> $INITRD/$MDADMCONF
- Moreover, with the information generated with those commands, read the
devices needed for
"automatic" adition to the initrd (echoes them to >&4).
Thanks a lot and sorry about my poor english.
P.D.: The patch:
--- mkinitrd.orig 2005-03-11 18:00:47.0 +0100
+++ mkinitrd.new2005-03-11 20:18:20.575264864 +0100
@@ -175,9 +175,17 @@
)"
printf '%s\n' $devices > getroot
- echo mdadm -A /devfs/md/$minor -R -u $uuid $devices \
- > md$minor-script
echo /sbin/mdadm >&6
+ echo /dev/md$minor >&4
+ echo mdadm -A /dev/md$minor -R -u $uuid $devices \
+ >> md$minor-script
+
+ echo -e "\n # If other RAID disks (and its components) are explicity
added in /etc/mkinitrd/files,\n"\
+ "# It is posible to detect and initiate them all:" \
+ >> md$minor-script
+ echo mdadm -A --scan \
+ >> md$minor-script
+ echo /etc/mdadm/mdadm.conf >&4
}
getraid_raidtools() {
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored:
LC_ALL set to [EMAIL PROTECTED])
Versions of packages initrd-tools depends on:
ii coreutils [fileutils] 5.2.1-2The GNU core utilities
ii cpio 2.5-1.2GNU cpio -- a program to manage ar
ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F
ii dash 0.5.2-1The Debian Almquist Shell
ii util-linux2.12-10Miscellaneous system utilities
-- no debconf information
--===0452105401==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="mkinitrd.patch"
--- mkinitrd.orig 2005-03-11 18:00:47.0 +0100
+++ mkinitrd.new2005-03-11 20:18:20.575264864 +0100
@@ -175,9 +175,17 @@
)"
printf '%s\n' $devi
Processed: reassign 310382 to kernel
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.14 > reassign 310382 kernel Bug#310382: cannot install debian with kernel 2.6.8 on DELL D810 laptop Warning: Unknown package 'kernel-image-2.6.8-2' Bug reassigned from package `kernel-image-2.6.8-2' to `kernel'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 310352 to initrd-tools, severity of 310352 is grave, merging 310352 310316
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.14 > reassign 310352 initrd-tools Bug#310352: kernel-image-2.6.11-1-k7: cannot reboot after upgrade Bug reassigned from package `kernel-image-2.6.11-1-k7' to `initrd-tools'. > severity 310352 grave Bug#310352: kernel-image-2.6.11-1-k7: cannot reboot after upgrade Severity set to `grave'. > merge 310352 310316 Bug#310316: initrd-tools Bug#310352: kernel-image-2.6.11-1-k7: cannot reboot after upgrade Merged 310316 310352. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310352: kernel-image-2.6.11-1-k7: cannot reboot after upgrade
Package: kernel-image-2.6.11-1-k7 Version: 2.6.11-5 Severity: critical Justification: breaks the whole system after an apt-get upgrade four of my servers didn't reboot, message on the screen is : "kernel can not convert a name into device number" /sbin/init 360 cannot.. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-image-2.6.11-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.80 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
