From: "Mike Black" <mblack@csihq.com>
To: "linux-kernel@vger.kernel.or" <linux-kernel@vger.kernel.org>
Subject: 2.2.18aa2 weird problem
Date: Tue, 19 Dec 2000 10:08:27 -0500 [thread overview]
Message-ID: <03a001c069cd$8a593c50$e1de11cc@csihq.com> (raw)
I've got three machines -- two are identical motherboards. I've been using
the same kernel binary on all three machines for over a year thru all the
upgrades since 2.2.15 (16, 17, and now 18aa2).
Now that I've compiled 2.2.18aa2 it only works on two of the machines. Both
of these use RAID1/IDE for boot drives. The machine that doesn't work uses
a boot floppy as the root drive is RAID5.
When the "bad" machine boots a "df" that has been inserted in rc.inet2 shows
the correct root drive having been mounted. But, it seems as though the
system cannot see most of the RAID5 mount. Booting complains about
/etc/mtab~ not being a directory, /lib/modules/2.2.18aa2 not existing (even
though it IS there), and several other files missing. Executable binaries
seem to work though (i.e. all daemons try to start up).
The end results is that I can't login to the console (typing doesn't even
echo any characters). So, I'm somewhat restricted on what I can debug.
Remote telnet doesn't work either. Can't reboot either, have to alt-sysrq-U
and hit the reset key.
Rebooting this machine to 2.2.17-RAID works just fine
Might there be a problem with RAID5 as root?
________________________________________
Michael D. Black Principal Engineer
mblack@csihq.com 321-676-2923,x203
http://www.csihq.com Computer Science Innovations
http://www.csihq.com/~mike My home page
FAX 321-676-2355
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-19 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-19 15:08 Mike Black [this message]
2000-12-19 16:43 ` 2.2.18aa2 weird problem Andrea Arcangeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='03a001c069cd$8a593c50$e1de11cc@csihq.com' \
--to=mblack@csihq.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox