From owner-freebsd-stable@FreeBSD.ORG Wed Jun 20 15:14:57 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 86C7C1065672 for ; Wed, 20 Jun 2012 15:14:57 +0000 (UTC) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (ei.bzerk.org [82.95.223.12]) by mx1.freebsd.org (Postfix) with ESMTP id E86CB8FC0A for ; Wed, 20 Jun 2012 15:14:56 +0000 (UTC) Received: from lt012.flucon.local (ip503d40cf.speed.planet.nl [80.61.64.207]) (authenticated bits=0) by ei.bzerk.org (8.14.4/8.14.4) with ESMTP id q5KFEjKJ044913 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 20 Jun 2012 17:14:46 +0200 (CEST) (envelope-from bulk@bzerk.org) From: Ruben de Groot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 20 Jun 2012 17:14:45 +0200 Message-Id: <730E36C6-E2A7-4C62-B988-25D66CDFE292@bzerk.org> To: stable@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-Spam-Status: No, score=4.5 required=5.0 tests=RCVD_IN_PBL,SPF_FAIL autolearn=no version=3.3.2 X-Spam-Level: **** X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ei.bzerk.org X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (ei.bzerk.org [192.168.179.40]); Wed, 20 Jun 2012 17:14:49 +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: Wed, 20 Jun 2012 15:14:57 -0000 I'm resending this email as I got no response the first time. 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.=20 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=3D"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 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 _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org"