From nobody@FreeBSD.org  Sun Apr  2 15:29:49 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 B4C1237BB1B
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  2 Apr 2000 15:29:49 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id PAA31406;
	Sun, 2 Apr 2000 15:29:48 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Message-Id: <200004022229.PAA31406@freefall.freebsd.org>
Date: Sun, 2 Apr 2000 15:29:48 -0700 (PDT)
From: slansky@usa.net
Sender: nobody@FreeBSD.org
To: freebsd-gnats-submit@FreeBSD.org
Subject: Cannot install FreeBSD 4.0 on my IDE hard disk
X-Send-Pr-Version: www-1.0

>Number:         17759
>Category:       kern
>Synopsis:       Cannot install FreeBSD 4.0 on my IDE hard disk
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr  2 15:30:01 PDT 2000
>Closed-Date:    Sun Apr 2 18:59:13 PDT 2000
>Last-Modified:  Sun Apr  2 19:00:49 PDT 2000
>Originator:     Petr
>Release:        FreeBSD 4.0 RELEASE
>Organization:
>Environment:
i386DX40; AMD-K6-350, common PC hardware, NE2000, 8/32MB of RAM, FD, ...
>Description:
I cannot install (not from CD nor from floppy) FreeBSD 4.0 on my IDE hardisk (QUANTUM LPS170A; 170MB, geometry:1011/15/22). Install cannot create filesystems, it ends with "bad magic number" or "tryed to mount R/W to /mnt that is RO,..."

Verison FreeBSD 2.2.8, linux and DOS, ... love my disk....

>How-To-Repeat:
I think problem is in "ata" driver

>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: billf 
State-Changed-When: Sun Apr 2 18:59:13 PDT 2000 
State-Changed-Why:  
Not a bug report, empty PR. 

Please send mail to questions@FreeBSD.org 

(and in the future choosing "critical" severity and "high" priority 
and deeming this a kernel problem is probably not wise, when the 
problem is most likely hardware or PEBKAC) 
>Unformatted:
