Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Oct 2000 18:38:30 -0400
From:      John <papalia@udel.edu>
To:        Salvo Bartolotta <bartequi@inwind.it>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: FSCK & "No write access"
Message-ID:  <4.3.2.7.2.20001025183208.00ae86c0@mail.udel.edu>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
At 10:39 PM 10/25/2000 +0000, Salvo Bartolotta wrote:
> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
>
>On 10/25/00, 10:19:59 PM, John <papalia@udel.edu> 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).
>
>
><dumb question>
>
>Surely you have done this upon your **unmounted** filesystems (eg
>right after booting in single user mode)?
>
></dumb question>

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20001025183208.00ae86c0>