From owner-freebsd-current@FreeBSD.ORG Mon Apr 30 12:49:29 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C2F561065672 for ; Mon, 30 Apr 2012 12:49:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 975958FC0A for ; Mon, 30 Apr 2012 12:49:29 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 01350B9C2; Mon, 30 Apr 2012 08:49:29 -0400 (EDT) From: John Baldwin To: Anton Shterenlikht Date: Mon, 30 Apr 2012 08:43:14 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p13; KDE/4.5.5; amd64; ; ) References: <20120426224215.GA79891@mech-cluster241.men.bris.ac.uk> <201204270751.11885.jhb@freebsd.org> <20120428172021.GA92264@mech-cluster241.men.bris.ac.uk> In-Reply-To: <20120428172021.GA92264@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201204300843.14636.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 30 Apr 2012 08:49:29 -0400 (EDT) Cc: freebsd-current@freebsd.org Subject: Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 12:49:29 -0000 On Saturday, April 28, 2012 1:20:22 pm Anton Shterenlikht wrote: > On Fri, Apr 27, 2012 at 07:51:11AM -0400, John Baldwin wrote: > > On Thursday, April 26, 2012 6:42:15 pm Anton Shterenlikht wrote: > > > I was updating from r231158 to 234465 > > > (amd64 laptop Compaq 6715s), > > > and I think I must've messed someting > > > up in the kernel config. Now I get > > > build error, panic of a loader error, > > > depending on which kernel I build. > > > > > > ********************************************************* > > > > > > If I build GENERIC, I get: > > > > > > (transcribed by hand) > > > > > > mountroot: waiting for device /dev/ad4s1a > > > Mounting from ufs:/dev/ad4s1a failed with error 19. > > > > > > mountroot> ? > > > > > > List of GEOM managed disk devices: > > > > > > cd0 > > > > > > mountroot> > > > > Hmm, so GENERIC is not finding ad4. Can you look in the dmesg > > (using scroll-lock) to see if GENERIC finds your ATA controller > > ok? > > I see only one line: > > ata0: at channel 0 on atapci0 > > ata does not appear anywhere else. > > > > > > The device is certainly correct in r231158: > > > > > > BUZI> df > > > Filesystem 512-blocks Used Avail Capacity Mounted on > > > /dev/ad4s1a 101554068 46474368 46955376 50% / > > > devfs 2 2 0 100% /dev > > > BUZI> > > > > > > ********************************************************* > > > > > > If I add > > > > > > device atadisk > > > > > > to GENERIC, then I get this linking error: > > > > Yes, you aren't supposed to use 'atadisk' with ATA_CAM. See the UPDATING > > entry 20110424 for more details on that. > > > > However, can you obtain a verbose dmesg from your old kernel? > > Amazingly (for me) I can't! > > Twice I got a panic. The third time, > and thereafter, I get the same error as with GENERIC: > > Mounting from ufs:/dev/ad4s1a failed with error 19. > > I also see: > > ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0exb > ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 > ata0: reset tp2 stat0=00 stat1=00 devices=0x10000 Hmmm, I don't know how to grok these lines, but does your disk work at all now with any kernel? It may be that your disk has died (or a cable, etc.) and it just happened to coincide with your upgrade? -- John Baldwin