linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jean-Rene Cormier" <jean-rene.cormier@cipanb.ca>
To: Alvin Oga <aoga@Maggie.Linux-Consulting.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Software RAID1 problems
Date: Sun, 2 Mar 2003 10:41:08 -0400	[thread overview]
Message-ID: <003301c2e0c9$c5eee010$8400a8c0@jrc> (raw)
In-Reply-To: Pine.LNX.3.96.1030301170531.29069A-100000@Maggie.Linux-Consulting.com


----- Original Message -----
From: "Alvin Oga" <aoga@Maggie.Linux-Consulting.com>
To: "Jean-Rene Cormier" <jean-rene.cormier@cipanb.ca>
Cc: <linux-raid@vger.kernel.org>
Sent: Saturday, March 01, 2003 9:08 PM
Subject: Re: Software RAID1 problems


>
> On Sat, 1 Mar 2003, Jean-Rene Cormier wrote:
>
> > Yes that was a typo sorry. I did reformat /dev/md0 and a when it started
> > formating it gave me those errors again. I did a little searching and
the
> > problem is not in the raid array, but I'm still not sure what is causing
the
> > problem. The error was:
> >
> > hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> > hde: drive not ready for command
> > hde: status timeout: status=0xf0 { Busy }
> > hde: drive not ready for command
> > ide2: reset: success
>
> make sure you have the same speed disks on the same ide cable
> - best to use only one ide drive per cable
> - do NOT mix ata-33 w/ ata-66 w/ ata-100 w/ ata-133 on the same
> cable

Both drives are new 60Gb Maxtor DiamondMax Plus 9 on separate IDE channels
on a Promise Ultra TX2 IDE card

> use better and SHORTER ide cables ??   ( should be 80 conductor )

I did switch the cable on the drives to see if it would make a difference
and it's still the same drive who gave me those errors so I guess it's not
the cables.

> make sure you do NOT have kinks in the ide cable ( keep it straight )
>
> make sure your kernel has the ide chipset support enabled for your
> motherboard

I noticed yesterday that my kernel didn't have IDE support for the Promise
Ultra compiled in so I recompiled the kernel with it. I'll put the drive
back in the computer and try it again to see if it works better

> -- otherwise... you have a failing or dead disk drive...
> -- if its an ibm deskstar... get rid of it...

I'll try this drive in another computer to see what it'll say.

Thanks

Jean-Rene Cormier


  reply	other threads:[~2003-03-02 14:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 13:20 Software RAID1 problems Jean-Rene Cormier
2003-02-21  0:11 ` Neil Brown
2003-02-21  3:12   ` Jean-Rene Cormier
2003-02-23 22:40     ` Neil Brown
2003-03-01 17:28       ` Jean-Rene Cormier
2003-03-02  1:08         ` Alvin Oga
2003-03-02 14:41           ` Jean-Rene Cormier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-12  7:42 ANNOUNCE: mdadm 2.1 - A tool for managing Soft RAID under Linux Neil Brown
2005-09-12 14:30 ` Software RAID1 problems Andy Dawson
2005-09-12 22:23   ` Neil Brown
2005-09-23 15:45     ` Andy Dawson
2005-09-23 15:52       ` Neil Brown

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='003301c2e0c9$c5eee010$8400a8c0@jrc' \
    --to=jean-rene.cormier@cipanb.ca \
    --cc=aoga@Maggie.Linux-Consulting.com \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).