From owner-freebsd-questions@FreeBSD.ORG Sun May 25 23:49:03 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5444E2B2 for ; Sun, 25 May 2014 23:49:03 +0000 (UTC) Received: from www5.pairlite.com (www5.pairlite.com [64.130.10.15]) by mx1.freebsd.org (Postfix) with ESMTP id 32DF82ED7 for ; Sun, 25 May 2014 23:49:02 +0000 (UTC) Received: from whisperer.chthonixia.net (cpe-69-204-244-241.nyc.res.rr.com [69.204.244.241]) by www5.pairlite.com (Postfix) with ESMTPSA id 470B22E2E4; Sun, 25 May 2014 19:48:51 -0400 (EDT) Date: Sun, 25 May 2014 19:49:24 -0400 From: Joe Altman To: freebsd-questions@freebsd.org Subject: Re: Post 'svn up .' to Revision: 266585 for 9.2; failure to mount root Message-ID: <20140525234924.GA33129@whisperer.chthonixia.net> References: <20140523144021.GA6839@whisperer.chthonixia.net> <53802BA9.4050608@cyberleo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53802BA9.4050608@cyberleo.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: CyberLeo Kitsana 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: Sun, 25 May 2014 23:49:03 -0000 On Sat, May 24, 2014 at 12:18:33AM -0500, CyberLeo Kitsana wrote: > > > 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. If they were disabled, I did not do so. Additionally, I don't have a clear idea what disabling means. So a question: is this something that is done for some reason? > > 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. I have tried to look at the issue, and find in dmesg for GENERIC: ada0: Previously was known as ad4 ada1: Previously was known as ad8 When I look at messages, this first occurs after the upgrade in the subject line. glabel list shows this: joe on whisperer /var/log $: glabel list -a Geom name: ada1s1 Providers: 1. Name: ufsid/4ded07edcfa105b8 Mediasize: 640134996480 (596G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 32256 Mode: r0w0e0 secoffset: 0 offset: 0 seclength: 1250263665 length: 640134996480 index: 0 Consumers: 1. Name: ada1s1 Mediasize: 640134996480 (596G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 32256 Mode: r0w0e0 Which shows the absence of ada0... > 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? Not sure what this means. > Another thing you might try is to switch the root mount in fstab or > loader.conf to using a glabel device, like /dev/ufs/