Date: Wed, 25 Oct 2000 17:19:59 -0400 From: John <papalia@udel.edu> To: freebsd-questions@freebsd.org Subject: FSCK & "No write access" Message-ID: <4.3.2.7.2.20001025171553.00ae5880@mail.udel.edu>
next in thread | raw e-mail | index | archive | help
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). I'm doing this all as root, and everything *seems* ok, and there are no flag set on the FS's or their files that I can see (with the exception of the occasional SCHG). I guess I should also note that FSCK was working just fine until I upgraded to 4.1.1-stable (from 4.1-stable). Any thoughts or direction would be great. Thanks in advance, 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.20001025171553.00ae5880>