Help with rc.conf error, read-only file system

2004-11-30 Thread Michael G.
I've been away from FreeBSD for a while and I just loaded 5.3 and 
inavertently made an error in rc.conf.  Now when I boot up the file 
system is read-only and I haven't been able to edit rc.conf to correct 
the simple mistake.  Any help would be appreciated.

Michael G.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help with rc.conf error, read-only file system

2004-11-30 Thread David Kelly
 I've been away from FreeBSD for a while and I just loaded 5.3 and
 inavertently made an error in rc.conf.  Now when I boot up the file
 system is read-only and I haven't been able to edit rc.conf to correct
 the simple mistake.  Any help would be appreciated.

mount -a to attempt mounting all filesystems. Use fsck -y on the ones
mount refuses to do. These days background fsck usually applies
automatically meanwhile one gets to use the filesystems instantly.

Just for fun you can type mount by itself at any time to list mounted
filesystems and some interesting properties such as R/W and softupdates.

Manually you could remount root with mount / to make it R/W. Then mount
/usr so as to have vi, which will complain (but still function) about
/var not being mounted and therefore no backup copy for crash recovery.

Use exit to resume multiuser boot out of single user.



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help with rc.conf error, read-only file system

2004-11-30 Thread Christian Hiris
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday 30 November 2004 23:22, Michael G. wrote:
 I've been away from FreeBSD for a while and I just loaded 5.3 and
 inavertently made an error in rc.conf.  Now when I boot up the file
 system is read-only and I haven't been able to edit rc.conf to correct
 the simple mistake.  Any help would be appreciated.

# mount -a -t ufs

- -- 
Christian Hiris [EMAIL PROTECTED] | OpenPGP KeyID 0x3BCA53BE 
OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBrPy809WjGjvKU74RAqxLAJ9ptl4tkDcKZIk4qyQ2D4QMM4ZJmwCfS/Bq
AdDF8C3sPx/dOk+YMYyS/Tg=
=7GI1
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help with rc.conf error, read-only file system

2004-11-30 Thread Conrad J. Sabatier
On Tue, 30 Nov 2004 17:04:03 -0600 (CST), David Kelly
[EMAIL PROTECTED] wrote:

  I've been away from FreeBSD for a while and I just loaded 5.3 and
  inavertently made an error in rc.conf.  Now when I boot up the file
  system is read-only and I haven't been able to edit rc.conf to
  correct the simple mistake.  Any help would be appreciated.

Once you reach the single-user shell prompt, do this:

mount -u / (changes root filesystem from read-only to read/write)
mount -a (attempts to mount any other filesystems in /etc/fstab)

If any filesystem fails to mount, run fsck -y on it, then try mounting
it again.

 mount -a to attempt mounting all filesystems. Use fsck -y on the
 ones mount refuses to do. These days background fsck usually applies
 automatically meanwhile one gets to use the filesystems instantly.

Not in single-user mode it doesn't.

 Just for fun you can type mount by itself at any time to list
 mounted filesystems and some interesting properties such as R/W and
 softupdates.
 
 Manually you could remount root with mount / to make it R/W. Then
 mount/usr so as to have vi, which will complain (but still function)
 about/var not being mounted and therefore no backup copy for crash
 recovery.
 
 Use exit to resume multiuser boot out of single user.
 
 
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]
 


-- 
Conrad J. Sabatier [EMAIL PROTECTED] -- In Unix veritas
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Read-Only file system

2004-10-14 Thread steveb99
I appear to have hosed myself and having trouble finding out what I do 
and how to fix it.  It appears that many of my file-systems are now 
saying they are read-only and I can't do anything with them, even when I 
login as root. 
I'm still learning so not a production mess. Can someone point to me how 
a file system can become Read-Only, the file permissions are fine.
Also can this be repaired if so what should I be reading to learn to do 
that.

TIA,
Steve B.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Read-Only file system

2004-10-14 Thread Micheal Patterson

- Original Message - 
From: steveb99 [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, October 14, 2004 4:28 PM
Subject: Read-Only file system


 I appear to have hosed myself and having trouble finding out what I do
 and how to fix it.  It appears that many of my file-systems are now
 saying they are read-only and I can't do anything with them, even when I
 login as root.
 I'm still learning so not a production mess. Can someone point to me how
 a file system can become Read-Only, the file permissions are fine.
 Also can this be repaired if so what should I be reading to learn to do
 that.

 TIA,
 Steve B.

First thing I would look at would be to make sure that the settings in
/etc/fstab are configured to be mount your slices as read write (rw) instead
of read only (r).

Your /etc/fstab should have entries similar to the one below. This would be
a normal one.

/dev/da0s1a /   ufs rw  1   1

Where you see rw, if that is an r only, then the file system will be mounted
as read only and cause your problem.

--

Micheal Patterson
Senior Communications Systems Engineer
405-917-0600

Confidentiality Notice:  This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]