From owner-freebsd-stable@FreeBSD.ORG Thu Jan 29 17:04:23 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 8BCF5106579C for ; Thu, 29 Jan 2009 17:04:23 +0000 (UTC) (envelope-from mike.barnardq@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224]) by mx1.freebsd.org (Postfix) with ESMTP id 5D34A8FC2D for ; Thu, 29 Jan 2009 17:04:23 +0000 (UTC) (envelope-from mike.barnardq@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so5632rvf.43 for ; Thu, 29 Jan 2009 09:04:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=SqvESiRBE7teS/C4Qy1Hd/pFQV5Vmc3ck7J4RVbuqLY=; b=qTNzlF+GuhZZMcH3YOiZswq4zs4xr20OlkloOWdTaMsLjVMawbBDH1Vlc7+JFNOkRs xdpTQli66UZNrtOnUcYZSRh3fsySj/h6GL1zvR2w0FwieOEifozAmK+xkiFLb7IwE3LU msxwzmfLF3HjMWC/SfuNZ5NkZoEhAhaX5wYlE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Uh0umQocmJ3szdfJ8lYSAs5ALqepm+j/dJTulK06HRax5LhWd1OvyDwom7GbRQ1LrO KN3xDz7z3Qy29yiPsxZywnW6BpgyefmWayAoTJqmbhGtmpngBvXC+Oe0mNcCftyzm0Kn qWlZg9r9xBcx3hUmYVsj/1U3xUT86KEG7oPeY= MIME-Version: 1.0 Received: by 10.141.142.15 with SMTP id u15mr125630rvn.112.1233248662939; Thu, 29 Jan 2009 09:04:22 -0800 (PST) In-Reply-To: References: <7dc029620901290634q7ca5361ct496fc2c4a6bfe53f@mail.gmail.com> Date: Thu, 29 Jan 2009 20:04:22 +0300 Message-ID: <7dc029620901290904m241a101ya5c4e044eac7000b@mail.gmail.com> From: Mike Barnard To: jjr@larush.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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: Thu, 29 Jan 2009 17:04:24 -0000 Thanks John On Thu, Jan 29, 2009 at 7:43 PM, wrote: > I entered ufs:ad7s1a and booted the kernel when I > recognized that the drive had been re-named from ad9 to ad7. After > booting, I changed /etc/fstab appropiately and have had no further > problems. I've never run into this with previous upgrades, very odd. > Unfortunately, this does not work for me. I tried this from the onset of the problem and ended up with nothing. I got as far as ad15s1a (yeah... pushing it as far as I could) with no results. I cannot seem to get any further than mountroot> how did you notice that the drive numbering had moved from ad9 to ad7? I have booted into single user mode with verbose logging and i see no reference to any adx devices. I do see ata entries which recognise the disk as a Intel ICH7 SATA300 and ata0 being reference at atapci0, but other than that, I see no references to any adx. When i boot the RELEASE kernel, i get this ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ad0: 152627MB at ata0-master SATA150 ad0: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth queue When i boot the 7.1 STABLE kernel, with verbose logging, i get this ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ata1: reiniting channel ... ... and then the famous mountroot> Thanks -- Mike Of course, you might discount this possibility, but remember that one in a million chances happen 99% of the time. ------------------------------------------------------------