Date: Fri, 7 Aug 2009 16:41:57 -0400 From: Identry <identry@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Boot failure Message-ID: <4d4e09680908071341i2d503819h2d6a55b885db5b56@mail.gmail.com> In-Reply-To: <4d4e09680908071318p66a6e76bwedda5f88623e019d@mail.gmail.com> 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> <4d4e09680908071318p66a6e76bwedda5f88623e019d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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... Well, something got worse. After running fsck_ffs with no errors, I tried to boot the machine. It got to the point where it printed: <snip> Booting from BIOS Partition 0 PS2 keyboard detected PS2 mouse detected and it just hangs at that point. -- John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d4e09680908071341i2d503819h2d6a55b885db5b56>