From owner-freebsd-questions Tue Jan 15 0:29:31 2002 Delivered-To: freebsd-questions@freebsd.org Received: from fedde.littleton.co.us (cfedde.dsl.frii.net [216.17.139.141]) by hub.freebsd.org (Postfix) with ESMTP id 8DE0937B404 for ; Tue, 15 Jan 2002 00:29:29 -0800 (PST) Received: from fedde.littleton.co.us (localhost [127.0.0.1]) by fedde.littleton.co.us (8.11.6/8.11.4) with ESMTP id g0F8TO874541; Tue, 15 Jan 2002 01:29:24 -0700 (MST) Message-Id: <200201150829.g0F8TO874541@fedde.littleton.co.us> To: charon@seektruth.org Cc: freebsd-questions@FreeBSD.ORG Subject: Re: can't mount / properly, fstab woes In-Reply-To: <200201132254.g0DMsGt02191@midway.uchicago.edu> From: Chris Fedde Date: Tue, 15 Jan 2002 01:29:24 -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 13 Jan 2002 16:54:20 -0600 David Syphers wrote: +------------------ | What did I do that was wrong, then? All I changed was / to read-only. This , | and this alone, caused my web server to stop functioning. I could achieve | the same level of convenience and even better security by pulling out the | power plug. +------------------ I feel your pain. It appears that something on your / filesystem wanted to be written to. Before changing a file system to read only you will want to audit the drive and be sure that nothing is modifying it. One way to do that is to see if any files on the disk are newer than the kernel. find / -xdev -newer /kernel -print. An approach to fixing the problem is to boot from the "live file system" CD or from the fixit floppy. Then fsck the broken / device and mount it readwrite on /a or /mnt. Finally edit the broken file, sync, sync and reboot. Again I wish you the best of luck. -- Chris Fedde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message