From owner-freebsd-stable@FreeBSD.ORG Thu Jan 29 14:34:55 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 AF990106566C for ; Thu, 29 Jan 2009 14:34:55 +0000 (UTC) (envelope-from mike.barnardq@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id 033A28FC08 for ; Thu, 29 Jan 2009 14:34:54 +0000 (UTC) (envelope-from mike.barnardq@gmail.com) Received: by fg-out-1718.google.com with SMTP id e12so1281419fga.35 for ; Thu, 29 Jan 2009 06:34:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=bRk7RBF69sTN2AS6fnkKOQ400DDz23raYzM6wn0/hvE=; b=VcdFYATWlisXoHA6brYkaai6h44uK2WmzR5FZXrgAQdQsn9trKaXcmDozihkwQwQ+G Nw+k8bRzd5PcRO+tdhjkAXDYVsE1M++WB0gmoGSnR1jZtA54LuKIZfZxUGJ4druthO7O nGNEeGmDar26P84DKU+B3oBCFsOxXWHpSFZs0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=TWygz6iHyRmnEkZGeXNdWshnZnXkDErQW4jgE8Y8OfqpEeIdkgIVUNIFCHjnfTayhC 7tWc5CcGciAbOgS6rxlwtSgtDtuGpjBD8bZxv910XAxSdhzJrKGgZEvdc/B+HHUQH0o/ rEWBi6a28uzMYy/iguydFD3PTxJRqY/cVN8K4= MIME-Version: 1.0 Received: by 10.223.113.136 with SMTP id a8mr124127faq.76.1233239693932; Thu, 29 Jan 2009 06:34:53 -0800 (PST) Date: Thu, 29 Jan 2009 17:34:53 +0300 Message-ID: <7dc029620901290634q7ca5361ct496fc2c4a6bfe53f@mail.gmail.com> From: Mike Barnard To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 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 14:34:55 -0000 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. This is what i have about this disk when i boot the RELEASE version of FreeBSD: #pciconf -lv atapci0@pci0:0:31:2: class=0x01018a card=0x73361462 chip=0x27c08086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller' class = mass storage subclass = ATA #atacontrol cap ad0 Protocol Serial ATA II device model WDC WD1600AAJS-60PSA0 serial number WD-WMAP96717073 firmware revision 21.12M21 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 312581808 sectors dma supported overlap not supported Feature Support Enable Value Vendor write cache yes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 # atacontrol mode ad0 current mode = SATA150 When i boot in verbose mode, i get this: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f mem 0xfdffe000-0xfdffe3ff at device 31.2 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfa00 pci0: child atapci0 requested type 4 for rid 0x24, but the BAR says it is an memio ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 54 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0xc ioapic0: routing intpin 15 (ISA IRQ 15) to vector 55 ata1: [MPSAFE] ata1: [ITHREAD] ... ... 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 GEOM: new disk ad0 ad0: Intel check1 failed ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0xc ata1: reinit done .. ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0xc ata1: reinit done .. ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire Any one with any ideas? -- Mike Of course, you might discount this possibility, but remember that one in a million chances happen 99% of the time. ------------------------------------------------------------