From nobody@FreeBSD.org  Sun Apr  9 19:40:30 2000
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 285CA37B5C3
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  9 Apr 2000 19:40:30 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id TAA94317;
	Sun, 9 Apr 2000 19:40:30 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Message-Id: <200004100240.TAA94317@freefall.freebsd.org>
Date: Sun, 9 Apr 2000 19:40:30 -0700 (PDT)
From: asherrod@sharemedia.com
Sender: nobody@FreeBSD.org
To: freebsd-gnats-submit@FreeBSD.org
Subject: Still having trouble identifying disk geometry (in ata-disk.c now)
X-Send-Pr-Version: www-1.0

>Number:         17885
>Category:       i386
>Synopsis:       Still having trouble identifying disk geometry (in ata-disk.c now)
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    grog
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr  9 19:50:01 PDT 2000
>Closed-Date:    Sun Apr 9 21:42:20 PDT 2000
>Last-Modified:  Sun Apr  9 21:43:56 PDT 2000
>Originator:     Andrew Sherrod
>Release:        4.0
>Organization:
Sharemedia
>Environment:
>Description:
This problem existed in wd.c and was carried over to ata-disk.c.

I have been told over and over it is not a "real" problem. Asking 
various users, I have discovered that I am not alone in experiencing 
this. Of course, others just followed the "Well, add a DOS partition,
and let Microsoft fix your problem" advice. But it IS a problem.

Whenever I install I have to go back and re-write the disk driver then
re-run newfs, etc... It is a problem. It can be fixed (easily).

My drives are not antiques or that unusual. One Western Digital, one
Maxtor. Okay, cheap disks, but not uncommon.

The problem: Not all disks return 16383 cylinders to indicate LBA mode
must be used. Mine return 4192, which rsults in rather small disk sizes.


>How-To-Repeat:
Boot the system with one of the disks in question. Try running 
/stand/sysinstall. Look at how small the disks just became.
>Fix:
129c129,130
<

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: grog 
State-Changed-When: Sun Apr 9 21:37:38 PDT 2000 
State-Changed-Why:  
Require feedback from submitter. 


Responsible-Changed-From-To: freebsd-bugs->grog 
Responsible-Changed-By: grog 
Responsible-Changed-When: Sun Apr 9 21:37:38 PDT 2000 
Responsible-Changed-Why:  
grog is handling this PR. 
State-Changed-From-To: feedback->closed 
State-Changed-By: grog 
State-Changed-When: Sun Apr 9 21:42:20 PDT 2000 
State-Changed-Why:  
Duplicate, incorrectly entered PR. 
>Unformatted:
Greg Lehey, 10 April 2000

Please supply more details.  What are the disks exactly?  What
hardware?  What version of FreeBSD?  Have you found any workarounds?
What do you mean by "re-write the disk driver"?

Looking at the synopsis, it's possible that you're referring to an
earlier PR.  Don't make us search: refer to it by number.

Greg Lehey, 10 April 2000

It appears that this PR was the first in a series of attempts to enter
a PR with a proposed fix.  This was finally successful with PR 17890.
I have assigned that PR to sos, and am closing this one (17885).
