public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Walt H <waltabbyh@comcast.net>
To: Nicklas Bondesson <nikomail@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)
Date: Sun, 21 Dec 2003 17:35:42 -0800	[thread overview]
Message-ID: <3FE64A6E.2020506@comcast.net> (raw)
In-Reply-To: <BAY8-DAV35IMKT7Fvnj0000fb07@hotmail.com>

Nicklas Bondesson wrote:
> Now I'm sucessfully booting my system with the 2.4.23 kernel using only one
> of the drives (hde). There is not a single line in the logs that says
> anything about the Promise ATARAID driver is beeing fired up, so my guess is
> that it doesn't load if no one is calling on it. When I try to boot from the
> RAID it dies right after the "NET4: Unix domain sockets 1.0/SMP for Linux"
> message. I think it's when the ATARAID driver is about to fire up. I have no
> idea at all what to do now. It must have something to do with the hard
> drives since this is the only thing that has changed. Maybee I'm missing
> some important kernel setting option or so? (I don't think so, but one never
> know for sure). Also what have changed in the Promise / ATARAID since
> 2.4.18?.
> 
> /Nicke

Not sure what else to tell you. If the pdcraid driver is compiled into the
kernel, you'll get a message about it during boot, even if it can't find all the
drives. I no longer use the 2.4 kernel series (or pdcraid), so I'm afraid I'm
out of ideas. Maybe somebody else on the list has some other things to try. Sorry.

-Walt




  reply	other threads:[~2003-12-22  1:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-20 19:44 Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271) Walt H
2003-12-20 23:54 ` Nicklas Bondesson
2003-12-21  1:01   ` Walt H
2003-12-21 14:54     ` Nicklas Bondesson
2003-12-21 16:32       ` Walt H
2003-12-21 17:21         ` Nicklas Bondesson
2003-12-22  0:05         ` Nicklas Bondesson
2003-12-22  1:35           ` Walt H [this message]
2003-12-22 13:38             ` Nicklas Bondesson
2003-12-22 15:05               ` Walt H
2003-12-22 15:31                 ` Nicklas Bondesson
2003-12-22 23:22             ` Nicklas Bondesson
2003-12-23  0:59             ` Nicklas Bondesson
2003-12-23  2:07               ` Walt H
2003-12-23  3:18                 ` Nicklas Bondesson
2003-12-23  3:47                   ` Walt H
2003-12-23 13:41                     ` Nicklas Bondesson
2003-12-23 13:56                     ` Nicklas Bondesson
2003-12-23 15:05                       ` Walt H
2003-12-23 16:10                         ` Nicklas Bondesson
2003-12-24  0:54                           ` Walt H
2003-12-23 14:42                     ` Nicklas Bondesson
  -- strict thread matches above, loose matches on Subject: below --
2003-12-28 16:26 Nicklas Bondesson
2003-12-28 16:56 ` Marcelo Tosatti
2003-12-28 17:06   ` Nicklas Bondesson
2003-12-20 13:33 Nicklas Bondesson

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=3FE64A6E.2020506@comcast.net \
    --to=waltabbyh@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikomail@hotmail.com \
    /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