Date: Fri, 7 Aug 2009 12:26:10 -0400 From: Identry <jalmberg@identry.com> To: Roland Smith <rsmith@xs4all.nl> Cc: freebsd-questions@freebsd.org Subject: Re: Boot failure Message-ID: <4d4e09680908070926y40c6463au2666fd0b085ab3af@mail.gmail.com> In-Reply-To: <20090807154009.GB39621@slackbox.xs4all.nl> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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. > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d4e09680908070926y40c6463au2666fd0b085ab3af>