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: Sat, 20 Dec 2003 17:01:07 -0800 [thread overview]
Message-ID: <3FE4F0D3.2020904@comcast.net> (raw)
In-Reply-To: <BAY8-DAV26Mb5CIs4vP0000f52f@hotmail.com>
Nicklas Bondesson wrote:
> Hi,
>
> Oh I forgot to say that i'm running RAID1 and it detects both drives
> perfectly (I'm passing the IDE addresses to the kernel at boot time from the
> lilo conf, see previous post). The system was reinstalled yesterday with two
> brand new 80GB Western Digital disks (WD800JB-00DUA3). The thing is, I have
> succesfully installed the TX2000 card with the native ATARAID drivers before
> using two 30GB Maxtor (something) disks and kernel 2.4-20 - 2.4.23. I wonder
> why I can't get it up and running now. It will only work with the pre
> compiled kernel shipped with Debian 3.0 (2.4.18-bf2.4). I have tried all
> sorts of kernel settings. Since I have got it to work before I think should
> be able to do it again.
>
> Please advise.
>
> /Nicke
Hmmm. I'm pretty sure that the partitions are enumerated the same way in 2.4.23
vs. 2.4.18. There was a change in the way IDE geometry was returned from the
kernel that caused a hiccup in the pdcraid driver around 2.4.22 I think? My
patch just tells the pdcraid to use an alternate method of finding the RAID
superblock on each drive. Not sure what else might be the problem. Do you see
the ataraid driver fire up (looking something like this):
ataraid/d0: ataraid/d0p1
Drive 0 is 239372 Mb (33 / 0)
Drive 1 is 239372 Mb (34 / 0)
Raid1 array consists of 2 drives.
Promise Fasttrak(tm) Softwareraid driver for linux version 0.03beta
The only problem I've recently come upon with pdcraid, is when it detects just
one of the drives and fails. I didn't think that should happen with raid1 though.
next prev parent reply other threads:[~2003-12-21 1:01 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 [this message]
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
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=3FE4F0D3.2020904@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