archive mirror
 help / color / mirror / Atom feed
From: Paul <>
Subject: Promise fasttrack raid, changed disk, unable to boot.
Date: Fri, 11 Jul 2003 19:32:21 -0400	[thread overview]
Message-ID: <> (raw)

For the previos year i have been using the promise fasttrack 100 to controll 4 
disks. I mirrored 2 75gig drives and 2 80gig drives. Recently one of the 75 
gig drives died on me. This particular mirroring array was the system array. 
So i replaced the disk with an 80 gig one and duplicated it. Now i an unable 
to boot with the previos kernel 2.4.19. But i can boot with the 2.4.18 kernel 
which was provided to be by my distrabution. I have comiled 2.4.19 and 2.4.20 
on the machine itself and another machine to see if i could get one of them 
to work, but i can not. During boot up something like this is listed

ataraid/d0  then the partitions are listed. such as ataraid/d0p1
then the drives are listed
drive0 is 733XXX mb
raid0 consists of 1 drive.

That is how it looks with the new disk plugged in. But if i unplug it.
it will look like this:

drive0 is 733xxx mb
drive1 is 733xxx mb  <--- this tells me that there is something either in the 
kernel or in the system that is telling the kernel what the old disk used to 

I am completly lost and hope that someone else has an idea of what i should 
do. BTW I have compiled my kernel statically, while the distos 2.4.18 was 
modules, if that makes any difference.

Thank you,

             reply	other threads:[~2003-07-11 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11 23:32 Paul [this message]
2003-07-13  5:29 Promise fasttrack raid, changed disk, unable to boot Paul
2003-07-18 16:53 ` Paul
2003-07-19 16:13 Walt H

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).