From owner-freebsd-current@FreeBSD.ORG Tue May 17 20:07:52 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65F6D16A4CE for ; Tue, 17 May 2005 20:07:52 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id E02CD43DD8 for ; Tue, 17 May 2005 20:07:51 +0000 (GMT) (envelope-from david.kleiner@gmail.com) Received: by zproxy.gmail.com with SMTP id 12so715223nzp for ; Tue, 17 May 2005 13:07:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YRdmvEae1tfEc1FdO6UIjUdlr1WDXxFfH8fhnuWu7K6x5lDEESlaPDqBtxoiLHWdgTQHMe52LmY4XoVaCuCexvk4149MoyzXE28bxyTY9qUn7Pqi9NZgyXPnnSMqp7LCNwcAzp/tjFcp0BsUk4EUVbxWXUCvcI8EqfFyK072BKg= Received: by 10.36.24.7 with SMTP id 7mr385823nzx; Tue, 17 May 2005 13:07:46 -0700 (PDT) Received: by 10.36.67.16 with HTTP; Tue, 17 May 2005 13:07:46 -0700 (PDT) Message-ID: Date: Tue, 17 May 2005 13:07:46 -0700 From: David Kleiner To: freebsd-current@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Subject: Re: -current: unable to boot (bt_strategy X not multiple of block size) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Kleiner List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2005 20:07:52 -0000 On 5/17/05, David Kleiner wrote: > CC: to -current. >=20 > Does anyone have insights into this? >=20 > --- >=20 > Hi, >=20 > As the subject says, -current as of evening of May 16 (US/Pacific), boot= ed > with an older i386 slice (October -current.) >=20 > Is there a way to recover? >=20 > Thank you, >=20 > David >=20 Replying to myself with more information: This is amd64 Asus A8N mobo, previous -current (May 1) worked fine, I cannot boot even into kernel.old any more, the only option is older i386 -current and maybe I can fix things from there. The boot loader said i386/FreeBSD but I don't remember what it said before for amd64 - it was happening too fast. /David