mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rupa Schomaker <rupa-list+linux-kernel@rupa.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Andries.Brouwer@cwi.nl, mlord@pobox.com, ole@linpro.no,
	linux-kernel@vger.kernel.org
Subject: Re: Problems with Promise IDE controller under 2.4.1
Date: 31 Jan 2001 22:05:08 -0800	[thread overview]
Message-ID: <m3hf2fdjl7.fsf@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.10.10101311201390.13711-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10101311201390.13711-100000@master.linux-ide.org> (Andre Hedrick's message of "Wed, 31 Jan 2001 12:03:04 -0800 (PST)")

Andre Hedrick <andre@linux-ide.org> writes:

> On 31 Jan 2001, Rupa Schomaker wrote:
> 
> > Andre Hedrick <andre@linux-ide.org> writes:
> > 
> > 
> > > > But there is no indication of what the problems could be,
> > > > or what he thinks the geometry should be (and why).
> > > > I see nothing very wrong in the posted data.
> > > 
> > > We agree Andries, but the enduser wants to see stuff the same.
> > 
> > In my case, I have two identical Maxtor drives, but they reported
> > different geometry.  How could that be?  Move the "virgin" drive to
> > the motherboard IDE controller and suddenly the geometry is the same.
> > Use fdisk and partition the disk, write it, and then move to the
> > promise controller and the "correct" geometry was used (that is, it is
> > now the same as when hooked up to the motherboard ide controller).
> > 
> > Why was it important to me?  I'm doing RAID1 and it is really nice to
> > have the same geometry so that the partition info is the same between
> > the two drives.   Makes life easier.
> 
> Please read the above and pass the geometry to the kernel.
> Mother boards have to do a translation to use the drive completely.

Andre,

But now it doesn't matter.  The drive was tainted (fdisk run while
attached to the mainboard controller) and now that geometry is
"stuck".  <shrug>  I was mostly explaining why it is nice to get the
same geometry on two identical drives (RAID1 is easier for the human
to deal with).

-- 
-rupa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-01  6:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-31 16:43 Andries.Brouwer
2001-01-31 17:46 ` Andre Hedrick
2001-01-31 19:33   ` Rupa Schomaker
2001-01-31 20:03     ` Andre Hedrick
2001-02-01  6:05       ` Rupa Schomaker [this message]
2001-02-01  8:23         ` Andre Hedrick
2001-01-31 20:04     ` Mark Lord
2001-01-31 20:08       ` Andre Hedrick
2001-01-31 20:55         ` Dan Hollis
2001-01-31 21:10           ` Andre Hedrick
2001-02-01  9:44     ` Peter Samuelson
  -- strict thread matches above, loose matches on Subject: below --
2001-01-31 23:15 Andries.Brouwer
2001-01-31 23:08 Andries.Brouwer
2001-01-31 16:02 Ole Aamot
2001-01-31 16:35 ` Andre Hedrick
2001-01-31 16:57   ` Paul Flinders
2001-01-31 17:47     ` Andre Hedrick
2001-02-01 14:15       ` Matthias Andree
2001-02-01 15:03         ` Paul Flinders
2001-02-01 17:45         ` Andre Hedrick

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=m3hf2fdjl7.fsf@localhost.localdomain \
    --to=rupa-list+linux-kernel@rupa.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlord@pobox.com \
    --cc=ole@linpro.no \
    /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®