From owner-freebsd-questions@FreeBSD.ORG Thu Jun 6 14:38:10 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 731C98E0 for ; Thu, 6 Jun 2013 14:38:10 +0000 (UTC) (envelope-from ahamiltonwright@mta.ca) Received: from smtpy.mta.ca (smtpy.mta.ca [138.73.1.143]) by mx1.freebsd.org (Postfix) with ESMTP id 4D4DC1758 for ; Thu, 6 Jun 2013 14:38:09 +0000 (UTC) Received: from host-29-237.mta.ca ([138.73.29.237]:61036) by smtpy.mta.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1UkbJF-00080T-VR; Thu, 06 Jun 2013 11:37:01 -0300 Subject: Re: Boot hangs in single-user mode Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Andrew Hamilton-Wright In-Reply-To: <20130606161824.4c45f579.freebsd@edvax.de> Date: Thu, 6 Jun 2013 11:38:08 -0300 Content-Transfer-Encoding: quoted-printable Message-Id: <17091F53-E841-4BDC-B0A8-3E2814CF68E9@mta.ca> References: <20130606161824.4c45f579.freebsd@edvax.de> To: Polytropon X-Mailer: Apple Mail (2.1085) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jun 2013 14:38:10 -0000 [ Condensation of earlier comments below ] On 2013-06-06, at 11:18 AM, Polytropon wrote: > On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote: >>=20 >> When I get to the point where the root filesystem is mounted, >> it hangs right after printing the message: >> Trying to mount root from ufs:/dev/ada0s1a >=20 > Have you tried hitting the RETURN key several times? ... > It's important to identify if the system is _really_ hanging, > or if the message "just isn't visible"... I did try that -- I have seen that behaviour before too. I tried = hitting return a half-dozen times, and have additionally tried waiting (up to 20 min) = to see if it would come back, to no avail. >> Interestingly, there seems to be a bit of a sequence issue, >> as I have also seen the mount message appear before the audio >> system comes up, so occasionally, the last item printed is: >> pcm0: on uaudio0 >=20 > This seems to indicate that the system is still responding, > i. e., the kernel is "up and running". Whenever "new" hardware > is detected, the kernel will issue a console message. That is a good point -- I will try plugging in an external USB device at this point, and see what happens then. It certainly appears that the system is generally running to me, as well. I should also mention that the system does respond nicely to [CTRL]-[ALT]-[DEL], which triggers the expected reboot process. >> I am rebooting the machine at the moment as I wish to ensure >> that I know which physical disk is ada2, so want to boot the >> machine without it plugged in. >=20 > A suggestion: I tend to keep a tendency to use labels instead > of device names to identify disks. This is handy in case you're This is an excellent idea. I do follow some variant of this (however work at a high enough level of paranoia that I want to be able to perform the "did the right drive disappear when I unplugged it" check just to ensure that I wasn't asleep when making up the labels. ;-) Thanks for the suggestions -- I will keep looking at it, and will try adding a USB device once this restore eventually completes. Thanks, Andrew.