From owner-freebsd-stable@FreeBSD.ORG Fri Jun 15 17:10:25 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F06C01065670 for ; Fri, 15 Jun 2012 17:10:25 +0000 (UTC) (envelope-from fbsd-stable@bzerk.org) Received: from ei.bzerk.org (ei.bzerk.org [82.95.223.12]) by mx1.freebsd.org (Postfix) with ESMTP id 881E08FC0C for ; Fri, 15 Jun 2012 17:10:25 +0000 (UTC) Received: from ei.bzerk.org (BOFH@localhost [127.0.0.1]) by ei.bzerk.org (8.14.4/8.14.4) with ESMTP id q5FH43EG081716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 15 Jun 2012 19:04:04 +0200 (CEST) (envelope-from fbsd-stable@bzerk.org) Received: (from bulk@localhost) by ei.bzerk.org (8.14.4/8.14.4/Submit) id q5FH43jR081715 for stable@freebsd.org; Fri, 15 Jun 2012 19:04:03 +0200 (CEST) (envelope-from fbsd-stable@bzerk.org) Date: Fri, 15 Jun 2012 19:04:02 +0200 From: Ruben de Groot To: stable@freebsd.org Message-ID: <20120615170402.GA81486@ei.bzerk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-12.9 required=5.0 tests=ALL_TRUSTED,AUTHD_RELAY, BAYES_00 autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ei.bzerk.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (ei.bzerk.org [127.0.0.1]); Fri, 15 Jun 2012 19:04:10 +0200 (CEST) Cc: Subject: kern.geom.part.check_integrity=0 not working. not able to boot 9-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, 15 Jun 2012 17:10:26 -0000 Hi, After over 3 years of uptime, I decided to upgrade one of my SUN boxes to 9-stable. However the new kernel didn't boot because of geom integrity check issues. This I understand as I remember I had to use some weird tricks in the past to get the entire disks used in the first place. Anyway, I felt lucky this was a known and documented problem, with a workaround: http://www.freebsd.org/releases/9.0R/relnotes-detailed.html#AEN1277 However, the workaround doesn't seem to work :-( Type '?' for a list of commands, 'help' for more detailed help. OK set kern.geom.part.check_integrity="0" OK boot jumping to kernel entry at 0xc0070000. Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #5: Thu Jun 14 19:24:33 UTC 2012 root@morninglightmountain.hacktor.net:/usr/obj/usr/src/sys/MORNINGLIGHTMOUNTAIN sparc64 real memory = 536870912 (512 MB) avail memory = 503963648 (480 MB) cpu0: Sun Microsystems UltraSparc-IIe Processor (400.00 MHz CPU) ctl: CAM Target Layer loaded nexus0: pcib0: mem 0x1fe00000000-0x1fe0000ffff,0x1fe01000000-0x1fe010000ff irq 2032,2030,2031,2021 on nexus0 pcib0: Sabre, impl 0, version 0, IGN 0x1f, bus A, 66MHz pcib0: DVMA map: 0x60000000 to 0x63ffffff 8192 entries pcib0: [GIANT-LOCKED] pci0: on pcib0 pci0: at device 7.0 (no driver attached) pci0: at device 3.0 (no driver attached) dc0: port 0x10000-0x100ff mem 0-0xff at device 12.0 on pci0 miibus0: on dc0 amphy0: PHY 1 on miibus0 amphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:03:ba:05:fa:5c dc1: port 0x10100-0x101ff mem 0x2000-0x20ff at device 5.0 on pci0 miibus1: on dc1 amphy1: PHY 1 on miibus1 amphy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: Ethernet address: 00:03:ba:05:fa:5c pci0: at device 10.0 (no driver attached) atapci0: port 0x10200-0x10207,0x10218-0x1021b,0x10210-0x10217,0x10208-0x1020b,0x10220-0x1022f at device 13.0 on pci0 atapci0: using PIO transfers above 137GB as workaround for 48bit DMA access bug, expect reduced performance ata2: at channel 0 on atapci0 ata3: at channel 1 on atapci0 nexus0: type unknown (no driver attached) Timecounter "tick" frequency 400000000 Hz quality 1000 Event timer "tick" frequency 400000000 Hz quality 1000 Timecounters tick every 1.000 msec ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: ATA-7 device ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ata3 bus 0 scbus1 target 0 lun 0 ada1: ATA-7 device ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad1 GEOM: ada0: adding VTOC8 information. GEOM_PART: integrity check failed (ada0, VTOC8) this is where it hangs, just like without setting kern.geom.part.check_integrity. Is this a regression? -- cheers, Ruben de Groot