From: Edward Muller <emuller@learningpatterns.com>
To: chris.lo@corp.sunday.com
Cc: linux-kernel@vger.kernel.org
Subject: RE: Problems booting 2.4.17
Date: 01 Jan 2002 13:07:41 -0500 [thread overview]
Message-ID: <1009908461.12587.3.camel@cc234543-a> (raw)
In-Reply-To: <3C31405E.6030209@corp.sunday.com>
In-Reply-To: <3C31405E.6030209@corp.sunday.com>
For now I've moved back to 2.4.16, which boots without a problem. I had
lots of work to do to get those systems up and configured so I haven't
had time to play.
I'm not sure what is causing the problem. I know how to make an initrd
image and it's there. It may be a problem with devfs because I remember
that Mandrake based their devfs scripts on some very very very old stuff
from the devfs ditribution (which is being removed IIRC).
It's probably not fs based as you are using reiserfs and I'm using ext3.
Anyway ... For now I've gone back to 2.4.16, but I'd like to try 2.4.17.
So if you happen to have some time and figure it out, please let me
know.
On Mon, 2001-12-31 at 23:51, Chris Lo wrote:
> Good Morning,
>
> I had the same problem, with resierfs. Any workaround
> found?
>
> Have a happy new year!!
>
> Regards,
> Chris
>
>
>
>
> Hello all.
>
> I'm having problems booting 2.4.17 on a Mandrake 8.1 system (with all
> current updates).
>
> When I boot 2.4.17 (with an initrd image) I get the following...
>
> kernel boots ...
> Creating root device
> mkrootdev: mknod failed: 17
> Mounting root filesyste with flags data=ordered
> Mount: error 16 mounting ext3 flags data=ordered
> ...Tried to remount without flags and fails with the same error...
> Kernel Panic: No initrd found ...
>
> I am using ext3 / /boot /usr /var & /home filesystems
>
> 2.4.8-34.1mdk boots fine however.
>
> I'm about to go try 2.4.16 (it was working with reiserfs partitions
> before).
>
> The machine is an AMD Athalon 1.3 Ghz on an EPOC board with a 3ware 7800
> series RAID card, with three 75/80 GB drives in a RAID 5 array.
>
> Anyone else run into something like this?
>
> I'll report back about 2.4.16 and if anyone would like more info, just
> shout.
>
>
> --
> -------------------------------
> Edward Muller
> Director of IS
>
> 973-715-0230 (cell)
> 212-487-9064 x115 (NYC)
>
> http://www.learningpatterns.com
> -------------------------------
>
--
-------------------------------
Edward Muller
Director of IS
973-715-0230 (cell)
212-487-9064 x115 (NYC)
http://www.learningpatterns.com
-------------------------------
next parent reply other threads:[~2002-01-01 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C31405E.6030209@corp.sunday.com>
2002-01-01 18:07 ` Edward Muller [this message]
2002-01-02 1:20 Chris, Lo Cheuk Kong
2002-01-02 4:03 ` Edward Muller
-- strict thread matches above, loose matches on Subject: below --
2001-12-27 17:58 Edward Muller
2001-12-27 18:30 ` Edward Muller
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=1009908461.12587.3.camel@cc234543-a \
--to=emuller@learningpatterns.com \
--cc=chris.lo@corp.sunday.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
all inboxes | Powered by JetHome®