From nobody@FreeBSD.ORG  Sun Nov 19 19:38:19 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 8F8B437B479; Sun, 19 Nov 2000 19:38:19 -0800 (PST)
Message-Id: <20001120033819.8F8B437B479@hub.freebsd.org>
Date: Sun, 19 Nov 2000 19:38:19 -0800 (PST)
From: mx@pisem.net
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: fsck -p on 4.0 stop with msg NO WRITE ACCESS
X-Send-Pr-Version: www-1.0

>Number:         22968
>Category:       bin
>Synopsis:       fsck -p on 4.0 stop with msg NO WRITE ACCESS
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 19 19:40:01 PST 2000
>Closed-Date:    Sun Nov 19 20:14:37 PST 2000
>Last-Modified:  Sun Nov 19 20:17:55 PST 2000
>Originator:     Max
>Release:        4.1.1
>Organization:
>Environment:
FreeBSD www.domn.com 4.1.1-RELEASE FreeBSD 4.1.1-RELEASE #0: Thu Oct 26 09:46:31 GMT 2000     max@www.domn.com:/usr/src/sys/compile/domn  i386
>Description:
#fsck -p
/dev/ad0s1a: NO WRITE ACCESS
/dev/ad0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

I am try install new fresh system and imediatly after install and first boot run fsck -p. Result - the same.
Also i am try install on another computer with different vendor of hdd, motherboard, procc and mem. Result - the same.


#fsck -y
** /dev/ad0s1a (NO WRITE)
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
946 files, 28316 used, 49043 free (211 frags, 6104 blocks, 0.3% fragmentation)
** /dev/ad0s1e (NO WRITE)
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=269855 (2 should be 0)
CORRECT? no
...
...


#df
Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/ad0s1a     77359    28316    42855    40%    /
/dev/ad0s1e   9082014   422823  7932630     5%    /usr
/dev/ad0s1f    286615     6092   257594     2%    /var
procfs              4        4        0   100%    /proc


>How-To-Repeat:
Every time runing fsck -p.
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: dougb 
State-Changed-When: Sun Nov 19 20:14:37 PST 2000 
State-Changed-Why:  

I realize that it's easy to be confused, but send-pr is 
really for different kinds of problems. Please resend 
your details to freebsd-questions@freebsd.org. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=22968 
>Unformatted:
