From owner-freebsd-stable@FreeBSD.ORG Fri Jan 30 05:52:31 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59E43106566B for ; Fri, 30 Jan 2009 05:52:31 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id EB3268FC16 for ; Fri, 30 Jan 2009 05:52:30 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (morganw-1-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:47e::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 7F4FCA1CAF76; Thu, 29 Jan 2009 23:52:26 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n0U5qMt7061680; Thu, 29 Jan 2009 23:52:22 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Thu, 29 Jan 2009 23:52:22 -0600 (CST) From: Wes Morgan To: Mike Barnard In-Reply-To: <7dc029620901290634q7ca5361ct496fc2c4a6bfe53f@mail.gmail.com> Message-ID: References: <7dc029620901290634q7ca5361ct496fc2c4a6bfe53f@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 05:52:31 -0000 On Thu, 29 Jan 2009, Mike Barnard wrote: > Hi All, > > I have run into a problem that seem rather puzzling. I have upgraded an > installation of FreeBSD from 7.0-RELEASE to 7.0-STABLE and 7.1-STABLE, but i > fail to boot with either one of the STABLE upgrades. I end up at this point: > > > Trying to mount root from ufs:/dev/ad0s1a > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:da0s1a > ? List valid disk boot devices > Abort manual input > > When i type ?, i get nothing. When i try to load all possible drives, from > ad0s1a to ad9s1a, i get nothing. When i boot kernel.old, i see this: > > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f mem 0xfdffe000-0xfdffe3ff > at device 31.2 on pci0 > ... > ad0: 152627MB at ata0-master SATA150 > > It seems that FreeBSD recognises this drive as a SATA300 but later on refers > to it as SATA150. Could this be the problem. Have you checked the jumper settings on the drive? There may be a jumper forcing SATA150 mode on the drive. I'd reset everything to factory defaults if possible. You might be able to use the ata driver from 7.0-R in -stable to boot your system. If that works, try searching for the commit that breaks your controller.