From owner-freebsd-questions Wed Oct 25 15:40: 5 2000 Delivered-To: freebsd-questions@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id 957B537B479 for ; Wed, 25 Oct 2000 15:39:58 -0700 (PDT) Received: from morgaine.udel.edu (morgaine.wondermutt.net [192.168.1.2]) by wondermutt.net (8.11.1/8.11.1) with ESMTP id e9PMe6202121; Wed, 25 Oct 2000 18:40:07 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.2.7.2.20001025183208.00ae86c0@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 25 Oct 2000 18:38:30 -0400 To: Salvo Bartolotta From: John Subject: Re: FSCK & "No write access" Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <20001025.22394400@bartequi.ottodomain.org> References: <4.3.2.7.2.20001025171553.00ae5880@mail.udel.edu> <4.3.2.7.2.20001025171553.00ae5880@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:39 PM 10/25/2000 +0000, Salvo Bartolotta wrote: > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< > >On 10/25/00, 10:19:59 PM, John wrote regarding FSCK & >"No write access": > > > > Hi all, > > > Out of curiosity and for sake of just checking my system to see how it >was > > doing, I was attempting to run fsck, but I am getting errors as shown >here: > > > merlin# fsck -fp /usr > > /dev/da0g: NO WRITE ACCESS > > /dev/da0g: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > > Some may ask why I was trying to use the -f, and the answer is that I >was > > only trying that after I had the same results with just a -p. So, in > > tooling around I thought to look at the /etc/fstab, which looks ok: > > > merlin# cat /etc/fstab > > # Device Mountpoint FStype Options Dump > Pass# > > /dev/da0b none swap sw 0 > 0 > > /dev/da0a / ufs rw 1 > 1 > > /dev/da0e /cvs ufs rw 2 > 2 > > /dev/da0g /usr ufs rw 2 > 2 > > /dev/da0f /var ufs rw,nosuid 2 > 2 > > proc /proc procfs rw 0 > 0 > > /dev/cd0c /cdrom cd9660 ro,noauto 0 > 0 > > /dev/da1c /home ufs rw,nosuid 0 > 0 > > > If I try to run fsck without any switches, I still get a read-only >message: > > > merlin# fsck /usr > > ** /dev/da0g (NO WRITE) > > (etc). > > > > >Surely you have done this upon your **unmounted** filesystems (eg >right after booting in single user mode)? > > No suck luck. I'm up-and-running in 'multi-user mode'. In each of the existing FS's (/, /usr, /home, /cvs, and /var) I am fully able to 'cp', 'mv', and 'touch' files. I can also use vi in any of those directories as well to create new files. Thanks again, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message