From owner-freebsd-questions@FreeBSD.ORG Sat May 24 05:25:29 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 03396AD1 for ; Sat, 24 May 2014 05:25:29 +0000 (UTC) Received: from mail.cyberleo.net (mtumishi.cyberleo.net [216.226.128.201]) by mx1.freebsd.org (Postfix) with ESMTP id D53302AB4 for ; Sat, 24 May 2014 05:25:27 +0000 (UTC) Received: from [172.16.44.4] (vitani.den.cyberleo.net [216.80.73.130]) by mail.cyberleo.net (Postfix) with ESMTPSA id C9624533; Sat, 24 May 2014 01:18:22 -0400 (EDT) Message-ID: <53802BA9.4050608@cyberleo.net> Date: Sat, 24 May 2014 00:18:33 -0500 From: CyberLeo Kitsana User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Joe Altman , freebsd-questions@freebsd.org Subject: Re: Post 'svn up .' to Revision: 266585 for 9.2; failure to mount root References: <20140523144021.GA6839@whisperer.chthonixia.net> In-Reply-To: <20140523144021.GA6839@whisperer.chthonixia.net> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2014 05:25:29 -0000 On 05/23/2014 09:40 AM, Joe Altman wrote: > Greetings, list... > > For 9.2 I recently updated to Revision: 266585 via svn east: > upon reboot, this error was written to my screen: > > Trying to mount root from ufs:dev/ad4s1a failed with error 19 Were your 'ad' aliases disabled in this new build? I just checked, and my 9.2 and 10.0 boxen have them by default; but they can be turned off. I would say to type ? at the mountroot prompt, but... > Then my keyboard fails, so I need to warm reset the machine. ...which means you can't really see what devices are available. > Booting > kernel.old (from April 9) succeeds; so following the instructions in the > handbook I mv kernel.old to kernel and reboot. The error above recurs. I > am currently using GENERIC. > The question should be obvious: what happened, and how can I fix it? Since you're using GENERIC, can you extract a fresh kernel from the distribution and see if that exhibits similar behaviour, just to narrow down a possible intermittent hardware issue? For example: I have an SSD in one of my machines that functions perfectly fine unless the machine is warm-rebooted, when it will disappear sometime between loader and mountroot. Only a power cycle can bring it back. Another thing you might try is to switch the root mount in fstab or loader.conf to using a glabel device, like /dev/ufs/