Date: Fri, 7 Aug 2009 16:18:31 -0400 From: Identry <jalmberg@identry.com> To: Erik Trulsson <ertr1013@student.uu.se> Cc: Roland Smith <rsmith@xs4all.nl>, freebsd-questions@freebsd.org Subject: Re: Boot failure Message-ID: <4d4e09680908071318p66a6e76bwedda5f88623e019d@mail.gmail.com> In-Reply-To: <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> <20090807165707.GA51779@owl.midgard.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>> > 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, back in the data center. I ran fsck_ffs -fp on my root file system and it returned with no errors. It just printed some information about number of files, used, free space, etc., ending with the interesting fact of .3% fragmentation. Then I reran it without the -fp and it printed Phase 1 - Phase 5, no errors, and again some info on the files. So, it looks like there is nothing wrong with the root partition. Which again raises the question, why won't it mount during the boot process? I'm going to try booting with verbose logging and see what that last line printed is... -- John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d4e09680908071318p66a6e76bwedda5f88623e019d>