From owner-freebsd-questions@FreeBSD.ORG Fri Aug 7 17:04:31 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 849EB1065678 for ; Fri, 7 Aug 2009 17:04:31 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 12B148FC1E for ; Fri, 7 Aug 2009 17:04:31 +0000 (UTC) Received: from c83-255-48-78.bredband.comhem.se ([83.255.48.78]:61759 helo=falcon.midgard.homeip.net) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1MZSr9-0006pE-5k for freebsd-questions@freebsd.org; Fri, 07 Aug 2009 19:03:53 +0200 Received: (qmail 39991 invoked from network); 7 Aug 2009 18:57:08 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 7 Aug 2009 18:57:08 +0200 Received: (qmail 51812 invoked by uid 1001); 7 Aug 2009 18:57:08 +0200 Date: Fri, 7 Aug 2009 18:57:08 +0200 From: Erik Trulsson To: Identry Message-ID: <20090807165707.GA51779@owl.midgard.homeip.net> References: <4d4e09680908061012q6ea8aeacm875c556eaea7a54f@mail.gmail.com> <4A7B1B41.7090507@unsane.co.uk> <4d4e09680908061733v21602321x252a7111a7648ad6@mail.gmail.com> <4A7C074C.9060303@unsane.co.uk> <4d4e09680908070825h6f42e692t8cf0baa4f10f9cc@mail.gmail.com> <20090807154009.GB39621@slackbox.xs4all.nl> <4d4e09680908070926y40c6463au2666fd0b085ab3af@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4d4e09680908070926y40c6463au2666fd0b085ab3af@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-Originating-IP: 83.255.48.78 X-Scan-Result: No virus found in message 1MZSr9-0006pE-5k. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1MZSr9-0006pE-5k 9d3bf1b1c11c1df0146939c902527bc8 Cc: Roland Smith , freebsd-questions@freebsd.org Subject: Re: Boot failure X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2009 17:04:32 -0000 On Fri, Aug 07, 2009 at 12:26:10PM -0400, Identry wrote: > >> Should I use any flags? Should I mount the filesystems read write or read only? > > > > You should never fsck a filesystem when its mounted! > > Ah... glad I asked. Actually it is only when a filesystem is mounted read-write that you must not run fsck on it. Running it on a filesystem which is mounted read-only should be OK. (Otherwise we would all be in a lot of trouble since when fsck is run normally during the startup sequence the root filesystem (/) is mounted read-only, and is in fact where the fsck binary is loaded from.) > > > I think you should start by reading the manual pages for fsck and > > fsck_ffs. I would start with 'fsck_ffs -fp /dev/yourdevicenode'. > > Okay, that makes sense, and is simpler than what I was planning. I > have a long train ride, so I'm going to print out and read those man > pages, and whatever I can find in the Handbook, and maybe there's some > info in my Absolute FreeBSD book... > > > If this command quits with errors, you might try fsck_ffs without flags, > > or 'fsck_ffs -y' to have it try and repair all damage that it finds. > > Excellent. Thanks for all your advice Roland. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- Erik Trulsson ertr1013@student.uu.se