Your message dated Mon, 18 Oct 2004 13:08:20 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#272597: kernel-image-2.4.27-1-k7: Kernel Panic after
moving / from SCSI to IDE
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; 20 Sep 2004 23:08:14 +0000
>From [EMAIL PROTECTED] Mon Sep 20 16:08:14 2004
Return-path: <[EMAIL PROTECTED]>
Received: from edoras.nas.com [66.114.32.34]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C9XGX-0007XG-00; Mon, 20 Sep 2004 16:08:13 -0700
Received: from localhost (localhost [127.0.0.1])
by edoras.nas.com (Postfix) with ESMTP
id B14EDEB416; Mon, 20 Sep 2004 16:08:09 -0700 (PDT)
Received: from edoras.nas.com ([127.0.0.1])
by localhost (edoras.nas.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 54357-09; Mon, 20 Sep 2004 16:08:09 -0700 (PDT)
Received: from debian1.loaner.com (dsl-47-134.nas.com [66.114.47.134])
by edoras.nas.com (Postfix) with ESMTP
id 14BBFEB3E7; Mon, 20 Sep 2004 16:08:09 -0700 (PDT)
Received: from kingsley by debian1.loaner.com with local (Exim 3.36 #1 (Debian))
id 1C9XGW-0003dH-00; Mon, 20 Sep 2004 16:08:12 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Kingsley G. Morse Jr." <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-image-2.4.27-1-k7: Kernel Panic after moving / from SCSI to IDE
X-Mailer: reportbug 2.43
Date: Mon, 20 Sep 2004 16:08:12 -0700
Message-Id: <[EMAIL PROTECTED]>
Sender: "Kingsley G. Morse Jr." <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new at nas.com
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: kernel-image-2.4.27-1-k7
Version: 2.4.27-1
Severity: important
Thanks for maintaining Debian's kernel-image-2.4.27-1-k7 package.
It makes upgrading pretty easy.
The main reason I'm writing is to report that
after replacing a bad SCSI root hard drive with the
box's first IDE, these error messages appeared at
boot time:
modprobe : modprobe: can't locate module block-major-3
modprobe : modprobe: can't locate module block-major-3
modprobe : modprobe: can't locate module block-major-3
modprobe : modprobe: can't locate module block-major-3
modprobe : modprobe: can't locate module block-major-3
modprobe : modprobe: can't locate module block-major-3
pivot_root: No such file or directory
/sbin/init: cannot open dev/console: No such file
Kernel panic: Attempted to kill init
After spending way too much time debugging this,
it seems to me that the kernel couldn't access the
new IDE hard drive on /.
It also seems to me that the reason why it
couldn't access the new IDE hard drive is that
when kernel-image-2.4.27-1-k7 was installed, it
ran mkinitrd with:
ROOT=probe
in
/etc/mkinitrd/mkinitrd.conf
which didn't know about the new IDE hard drive
when it was originally run and thus didn't include
the right stuff in initrd to access the new IDE
hard drive.
I doubt that this is related to bug #266510, (very
very important ide-probe.c patch) because other
versions of the kernel are affected too, although
they return slightly different error messages,
like:
modprobe: modprobe: Can't locate module sysfs
or
ds: no socket drivers loaded!
kmod: failed to exe /sbin/modprobe -s -k block-major-3, errno = 2
VFS: Cannot open root device "hda2" or 03:02
Please append a correct "root=" boot option
I seem to have solved the problem by:
1.) Booting with a rescue disk (knoppix)
2.) becoming the root user
3.) mounting the new IDE hard drive
$ mount /dev/hda2 /mnt/hda2
4.) working in a familiar environment
$ chroot /mnt/hda2
5.) if I recall correctly, I needed to
$ mount /proc /proc -t proc
6.) using the package's install script(s) to
generate an up to date initrd file
$ kernel-reconfigure kernel-image-2.4.27-1-k7
7.) shutdown
8.) reboot
However, it took a long time to solve and made
recovering from a failed root drive harder than it
already is.
Having said that, I'm not sure how to spare other
people from having to go through the same ordeal,
and can only offer some suggestions and trust your
considerable experience in these matters.
One option would be to just keep this bug report
open, let google index it and some people will
eventually stumble across my solution of using
$ kernel-reconfigure kernel-image-2.4.27-1-k7
Another option would be to suggest to mkinitrd's
maintainer that root=probe always check for IDE
hard drives at run time.
Finally, I suppose this behavior could be
documented in all kernel image packages.
Thanks for your consideration,
Kingsley
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-k7
Locale: LANG=C, LC_CTYPE=C
Versions of packages kernel-image-2.4.27-1-k7 depends on:
ii coreutils [fileutils] 5.0.91-2 The GNU core utilities
ii fileutils 4.5.1-2 GNU file management utilities
ii initrd-tools 0.1.73 tools to create initrd image for p
ii modutils 2.4.25-3 Linux module utilities
-- no debconf information
---------------------------------------
Received: (at 272597-done) by bugs.debian.org; 18 Oct 2004 05:47:17 +0000
>From [EMAIL PROTECTED] Sun Oct 17 22:47:17 2004
Return-path: <[EMAIL PROTECTED]>
Received: from koto.vergenet.net [210.128.90.7]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1CJQMW-0004YO-00; Sun, 17 Oct 2004 22:47:17 -0700
Received: (qmail 8221 invoked by uid 7100); 18 Oct 2004 05:34:15 -0000
Date: Mon, 18 Oct 2004 13:08:20 +0900
From: Horms <[EMAIL PROTECTED]>
To: "Kingsley G. Morse Jr." <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#272597: kernel-image-2.4.27-1-k7: Kernel Panic after moving /
from SCSI to IDE
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
X-Cluestick: seven
User-Agent: Mutt/1.5.6+20040907i
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
This isn't really a bug as the package is behaving as expected.
However, I agree that it is a very tedious path to have to go down.
I think that the best approach here would be to document the problem,
perhaps in README.Debian. Would you like to contribute a write up of
how to upgrade an IDE system safely? I would be more than happy to
consider it for inclusion in upcoming kernel-image packages.
--
Horms
