Bug 22968

Summary: fsck -p on 4.0 stop with msg NO WRITE ACCESS
Product: Base System Reporter: mx <mx>
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description mx 2000-11-20 03:40:01 UTC
#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.
Comment 1 Doug Barton freebsd_committer freebsd_triage 2000-11-20 04:14:37 UTC
State Changed
From-To: open->closed


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.